Coder Social home page Coder Social logo

fira's Introduction

Mozilla's Fira Type Family

http://mozilla.github.io/Fira/

Download Fira

Latest Release
All Releases

Fira Roadmap

See the Fira Road Map for further information on upcoming releases. Please add your comments or questions within the document.

How to Contribute to Fira

If you're interested in contributing, see our Fira Contribution Documentation. Please add your comments or questions within the document.

Usage

Use this font on your website!

<link rel="stylesheet" href="https://code.cdn.mozilla.net/fonts/fira.css">

External Resources

Further information on the design and specifications of the Fira typeface can be found at Carrois Studio.
Fira can also be found in these foundries:
1001 Fonts
Adobe Typekit
Google Fonts
Font Squirrel

fira's People

Contributors

davelab6 avatar earaujoassis avatar haroenv avatar hayderimran7 avatar horia avatar jfkthame avatar k88hudson avatar kdashg avatar kkirsche avatar kremalicious avatar potch avatar schweinepriester avatar sedrubal avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

fira's Issues

Cyrillic slanted Д looks like Latin slanted D

This could be fine for a fancy font but clearly draws extra attention when used daily (I've set Firefox on a 166dpi notebook to use Fira Sans/Mono as default fonts, so far so good).

Please do consider changing it to proper Cyrillic one; regular version is correct.

Danke sehr!

gnome-terminal doesn't see Fira Mono. gedit and firefox are ok.

I'm using Ubuntu 14.04.

fc-match "Fira  Mono"
FiraMono-Regular.otf: "Fira Mono" "Regular"

gedit and firefox are fine. I can select Fira Mono. But in gnome-terminal's profile preference dialog, I cannot see Fira mono.

Any hints will be greatly appreciated. Thanks.

Fira Mono italics

Please make proper italics for Fira Mono!
It is already one of the best fonts for programming (IMO), but seriously lacking without italics.

Add documentation about contributing

I'd like to add a fix for #17 but couldn't find what the correct procedure for contributing is. What is the original source format I'd have to use? Is it OTF? Is editing with fontforge ok?

Ligatures seem too small.

This could be an issue with my font rendering setup, instead of with the font itself. I know too little about font rendering to say one way or the other.

Ligatures appear too small on my screen. I'm using up-to-date Arch Linux with freetype2 2.5.0.1, fontconfig 2.10.95, and cairo 1.12.16. I've attached an image showing the issue in Firefox 24.0:

ligatures

Notice the cross on the ligature f is lower than the median, the ligature f's ascender is shorter than the first f's, and the bottom of the ligature appears to render slightly underneath the baseline. (Using terms from http://en.wikipedia.org/wiki/File:Typography_Line_Terms.svg ).

Let me know if I can give any more information to help diagnose this.

Specify the Copyright holder.

Neither the License nor README file specify the copyright holder. I assume it is the Mozilla Foundation?

I need to provide the copyright holder for the Debian package I'm working on: ruediger/fonts-fira#1

Master site for downloading latest version

Hello,

I am maintainer of Fira port on FreeBSD:
http://svnweb.freebsd.org/ports/head/x11-fonts/fira/
http://svnweb.freebsd.org/ports/head/www/fira-webfont/

I looked for MASTER_SITES when making this and one is for moztt (deprecated):
https://github.com/mozilla-b2g/moztt

The other is unusable box.com with random URL, no file name, no version and no checksum:
https://www.mozilla.org/en-US/styleguide/products/firefox-os/typeface/

So I'm using https://github.com/mozilla/Fira right now.

I checked file size from port and box.com .zip and are not identical:

# du -k  /usr/local/lib/X11/fonts/fira-box.com/FiraMono-Regular.ttf 
124  /usr/local/lib/X11/fonts/fira-box.com/FiraMono-Regular.ttf

# du -k /usr/local/lib/X11/fonts/fira/FiraMono-Regular.ttf 
140  /usr/local/lib/X11/fonts/fira/FiraMono-Regular.ttf
  1. Is it possible to update https://github.com/mozilla/Fira to use the latest version of the font? Maybe using Tags to differentiate these versions too.
  2. I'd like to include the OT PDF in the FreeBSD port DOCS. Please add the PDF demos from box.com .zip in https://github.com/mozilla/Fira too.

Some tests when I'm looking at "f" in Fira:

https://i.imgur.com/QYxqA1l.png
The font sizes in PDF and LibreOffice are different.
I couldn't find a quick way to extract the font size for "f" from PDF (I think it's image, not font).

https://i.imgur.com/Y2Aj2Da.png
The font sizes here are 32px and the "f" appears almost identical when I select to difference the layers in the Gimp:
Matching the "f" in "Firefox": http://i.imgur.com/riOaNAz.png
Matching the "f" in "abcdefgh...": http://i.imgur.com/7L6Rx3R.png

Using the Gimp I get these results:
http://i.imgur.com/sRqeULR.png
http://i.imgur.com/G7gk0CL.png

http://i.imgur.com/aLYrND7.png
The font sizes here are 32px and the "f" appears almost identical when I select to difference the layers in the Gimp:
Matching the "f" in "Firefox": http://i.imgur.com/SkckZFJ.png
Matching the "f" in "abcdefgh...": http://i.imgur.com/0wGEz2e.png

Using the Gimp I get these results:
http://i.imgur.com/zhNodV7.png
Matching the "f" in "Firefox": http://i.imgur.com/Kt0ll7P.png
Matching the "f" in "abcdefgh...": http://i.imgur.com/4jFSdJI.png

Thank you

Feature request: a light weight for Fira Mono?

The font rendering on OS X is bolder than other platforms, and the medium weight of the monospaced version looks almost bold.

See here Fira Mono Regular 11 pt vs Source Code Pro light 12 pt, which have roughly the same size:

Fira Mono Regular 11 pt

Source Code Pro light 12 pt

I know it is a big undertaking, but a light weight would be a very nice addition.

Difference in leading in Mono version of the typeface

This is a screenshot of my terminal (iTerm2) with the typeface version downloaded from this link.

screenshot 2014-05-27 14 41 19

And here is a screenshot with the typeface (otf version) from this repo. Checked out the latest version.
screenshot 2014-05-27 14 45 29

My question is, is the change in leading intentional? Or is there some setting I'm missing? I haven't changed the spacing manually.

Fraction Slash (U+2044) in Fira Mono has negative width

In v3.106, the fraction-slash glyph has been given a negative(!) advance width. I think this is incorrect in principle — in a monospaced font, it should have the same width as all the rest of the (spacing) glyphs — and it seems likely to cause problems for software that assumes glyph widths are non-negative.

Fira Hair

I can't seem to get fira hair to render properly in chrome (Version 35.0.1916.153 m). For example, here's the github repo website in chrome vs internet explorer (11.0.9600.17126):

screenshot 2014-06-18 08 04 39

Google Web Fonts

Is there any chance this font will become available from Google Fonts?

FiraSans 3.108 - glyphs with negative advance widths

In the 3.108 fonts, there are seven glyphs in each face that have negative advance widths in the 'hmtx' table:

FiraSans-BoldItalic.ttx: [mtx name="null" width="-10" lsb="0"/]
FiraSans-BoldItalic.ttx: [mtx name="uni200C" width="-10" lsb="-72"/]
FiraSans-BoldItalic.ttx: [mtx name="uni200D" width="-10" lsb="-72"/]
FiraSans-BoldItalic.ttx: [mtx name="uni200E" width="-10" lsb="-71"/]
FiraSans-BoldItalic.ttx: [mtx name="uni200F" width="-10" lsb="-73"/]
FiraSans-BoldItalic.ttx: [mtx name="uniFEFF" width="-10" lsb="0"/]
FiraSans-BoldItalic.ttx: [mtx name="zerowidthspace" width="-10" lsb="0"/]
FiraSans-BookItalic.ttx: [mtx name="null" width="-5" lsb="0"/]
FiraSans-BookItalic.ttx: [mtx name="uni200C" width="-5" lsb="-69"/]
FiraSans-BookItalic.ttx: [mtx name="uni200D" width="-5" lsb="-69"/]
FiraSans-BookItalic.ttx: [mtx name="uni200E" width="-5" lsb="-68"/]
FiraSans-BookItalic.ttx: [mtx name="uni200F" width="-5" lsb="-70"/]
FiraSans-BookItalic.ttx: [mtx name="uniFEFF" width="-5" lsb="0"/]
FiraSans-BookItalic.ttx: [mtx name="zerowidthspace" width="-5" lsb="0"/]
FiraSans-ExtraBoldItalic.ttx: [mtx name="null" width="-11" lsb="0"/]
FiraSans-ExtraBoldItalic.ttx: [mtx name="uni200C" width="-11" lsb="-73"/]
FiraSans-ExtraBoldItalic.ttx: [mtx name="uni200D" width="-11" lsb="-73"/]
FiraSans-ExtraBoldItalic.ttx: [mtx name="uni200E" width="-11" lsb="-72"/]
FiraSans-ExtraBoldItalic.ttx: [mtx name="uni200F" width="-11" lsb="-74"/]
FiraSans-ExtraBoldItalic.ttx: [mtx name="uniFEFF" width="-11" lsb="0"/]
FiraSans-ExtraBoldItalic.ttx: [mtx name="zerowidthspace" width="-11" lsb="0"/]
FiraSans-ExtraLightItalic.ttx: [mtx name="null" width="-2" lsb="0"/]
FiraSans-ExtraLightItalic.ttx: [mtx name="uni200C" width="-2" lsb="-67"/]
FiraSans-ExtraLightItalic.ttx: [mtx name="uni200D" width="-2" lsb="-67"/]
FiraSans-ExtraLightItalic.ttx: [mtx name="uni200E" width="-2" lsb="-67"/]
FiraSans-ExtraLightItalic.ttx: [mtx name="uni200F" width="-2" lsb="-68"/]
FiraSans-ExtraLightItalic.ttx: [mtx name="uniFEFF" width="-2" lsb="0"/]
FiraSans-ExtraLightItalic.ttx: [mtx name="zerowidthspace" width="-2" lsb="0"/]
FiraSans-HeavyItalic.ttx: [mtx name="null" width="-12" lsb="0"/]
FiraSans-HeavyItalic.ttx: [mtx name="uni200C" width="-12" lsb="-73"/]
FiraSans-HeavyItalic.ttx: [mtx name="uni200D" width="-12" lsb="-73"/]
FiraSans-HeavyItalic.ttx: [mtx name="uni200E" width="-12" lsb="-72"/]
FiraSans-HeavyItalic.ttx: [mtx name="uni200F" width="-12" lsb="-74"/]
FiraSans-HeavyItalic.ttx: [mtx name="uniFEFF" width="-12" lsb="0"/]
FiraSans-HeavyItalic.ttx: [mtx name="zerowidthspace" width="-12" lsb="0"/]
FiraSans-Italic.ttx: [mtx name="null" width="-6" lsb="0"/]
FiraSans-Italic.ttx: [mtx name="uni200C" width="-6" lsb="-69"/]
FiraSans-Italic.ttx: [mtx name="uni200D" width="-6" lsb="-69"/]
FiraSans-Italic.ttx: [mtx name="uni200E" width="-6" lsb="-68"/]
FiraSans-Italic.ttx: [mtx name="uni200F" width="-6" lsb="-70"/]
FiraSans-Italic.ttx: [mtx name="uniFEFF" width="-6" lsb="0"/]
FiraSans-Italic.ttx: [mtx name="zerowidthspace" width="-6" lsb="0"/]
FiraSans-LightItalic.ttx: [mtx name="null" width="-3" lsb="0"/]
FiraSans-LightItalic.ttx: [mtx name="uni200C" width="-3" lsb="-68"/]
FiraSans-LightItalic.ttx: [mtx name="uni200D" width="-3" lsb="-68"/]
FiraSans-LightItalic.ttx: [mtx name="uni200E" width="-3" lsb="-67"/]
FiraSans-LightItalic.ttx: [mtx name="uni200F" width="-3" lsb="-68"/]
FiraSans-LightItalic.ttx: [mtx name="uniFEFF" width="-3" lsb="0"/]
FiraSans-LightItalic.ttx: [mtx name="zerowidthspace" width="-3" lsb="0"/]
FiraSans-MediumItalic.ttx: [mtx name="null" width="-8" lsb="0"/]
FiraSans-MediumItalic.ttx: [mtx name="uni200C" width="-8" lsb="-71"/]
FiraSans-MediumItalic.ttx: [mtx name="uni200D" width="-8" lsb="-71"/]
FiraSans-MediumItalic.ttx: [mtx name="uni200E" width="-8" lsb="-70"/]
FiraSans-MediumItalic.ttx: [mtx name="uni200F" width="-8" lsb="-72"/]
FiraSans-MediumItalic.ttx: [mtx name="uniFEFF" width="-8" lsb="0"/]
FiraSans-MediumItalic.ttx: [mtx name="zerowidthspace" width="-8" lsb="0"/]
FiraSans-SemiBoldItalic.ttx: [mtx name="null" width="-9" lsb="0"/]
FiraSans-SemiBoldItalic.ttx: [mtx name="uni200C" width="-9" lsb="-71"/]
FiraSans-SemiBoldItalic.ttx: [mtx name="uni200D" width="-9" lsb="-71"/]
FiraSans-SemiBoldItalic.ttx: [mtx name="uni200E" width="-9" lsb="-70"/]
FiraSans-SemiBoldItalic.ttx: [mtx name="uni200F" width="-9" lsb="-72"/]
FiraSans-SemiBoldItalic.ttx: [mtx name="uniFEFF" width="-9" lsb="0"/]
FiraSans-SemiBoldItalic.ttx: [mtx name="zerowidthspace" width="-9" lsb="0"/]
FiraSans-UltraItalic.ttx: [mtx name="null" width="-13" lsb="0"/]
FiraSans-UltraItalic.ttx: [mtx name="uni200C" width="-13" lsb="-74"/]
FiraSans-UltraItalic.ttx: [mtx name="uni200D" width="-13" lsb="-74"/]
FiraSans-UltraItalic.ttx: [mtx name="uni200E" width="-13" lsb="-73"/]
FiraSans-UltraItalic.ttx: [mtx name="uni200F" width="-13" lsb="-75"/]
FiraSans-UltraItalic.ttx: [mtx name="uniFEFF" width="-13" lsb="0"/]
FiraSans-UltraItalic.ttx: [mtx name="zerowidthspace" width="-13" lsb="0"/]

These should all be zero-width, I presume.

Fractional coordinates in Hair

Hello,

I am looking at Fira Sans Hair right now and have the following concern. It is the thinnest weight in the family, but it does not look like a master. It feels like it was produced by extrapolation from some thicker weight, and that extrapolation did not do a good job.

Most of the nodes have fractional coordinates. I understand that, at this weight, it is challenging to work with integers, but there are some really questionable cases. In particular, there is no capital letter aligned to the cap height. Have a look at the top nodes of such letters as E, H, I, and T: they are shorter than 681 but taller than 680.

May I ask if it was intentional and, if so, how it affects text rendering.

Thank you.

Regards,
Ivan

FiraMono: xAvgCharWidth should match the standard glyph advance

In FiraMono-Regular.otf, the OS/2 table includes

<xAvgCharWidth value="585"/>

although the standard width of the (monospaced) glyphs is 600. This should be changed so that it matches the actual glyphs.

It looks like Glyphs is calculating an average that includes the small number of zero-width glyphs in the font. This results in an average that is slightly less than the font's fixed glyph advance, but it's not helpful for client software - e.g. when using this value to determine the size of a text area that's supposed to be "80 characters wide".

The OpenType spec[1] actually specifies this: "The value for xAvgCharWidth is calculated by obtaining the arithmetic average of the width of all non-zero width glyphs in the font." (My emphasis.)

[1] http://www.microsoft.com/typography/otspec/os2.htm#acw

in Mono...

in Mono the J to u kerning needs to narrow.
See Jump in sample.

Vertical metrics should be equal for consistent spacing across platforms

In version 3.108 of Fira, the sTypo metrics (sTypoAscender, sTypoDescender, sTypoLineGap) have been set to 785, 215, and 200, respectively, for a total line height of 1200 (i.e., 1.2 ems). This is good-- this does indeed match what was present in version 2 of the fonts.

However, at least two major OSes' font renderers do not use the sTypo metrics at all-- in particular, Windows GDI uses the usWin metrics consistently, while Mac OS X uses the hhea metrics consistently, regardless of the value of the USE_TYPO_METRICS flag. (See http://typophile.com/node/13081 for further discussion of this.) DirectWrite on Windows does obey the sTypo metrics--but unfortunately, there are still some Windows machines (such as my work laptop) where DirectWrite's rendering is very buggy, forcing the use of GDI.

The total line height as measured by both of these sets of metrics should be equal to the total line height from the sTypo metrics. Unfortunately, in the case of Fira, they're not. With an ascender of 1050 and a descender of 500, the total line height as measured by these metrics is 1550 (1.55 ems). As a result, line spacing is not identical across OSes.

Greek lowercase kappa (κ) is wrong.

Thank you for this very nice open font. I noticed an issue with a greek glyph.

In the greek lowercase kappa ( κ, equivalent to latin k ) the vertical line shouldn't extend above the rest of the letter. The small kappa's height should be the same as the height of a,s,o,m instead of the current height which matches h,b,d.

It may seem small but for anyone used to the greek language it seems unnatural and strikes as wrong.

More ligatures?

It's not really an issue, but I could not find any information on this. Are more ligatures planned? I think ligatures for ft, fj and ff (maybe even ffi, ffl and fft (in extrema for st, but might be too much)) would make this font more beautiful, especially for print.

Cheers, Cris

License mismatch in TTF metadata

The license data in the TTF metadata differs from the LICENSE file in the repo:

$ ttname ~/Downloads/FiraSans-Regular.ttf 
[...]
license description (#13): Licensed under the Apache License, Version 2.0
license info URL (#14): http://www.apache.org/licenses/LICENSE-2.0

😢

OTF zip file contains Mac OS X specific files

$ unzip -l FiraOpenType.zip 
Archive:  FiraOpenType.zip
  Length      Date    Time    Name
---------  ---------- -----   ----
        0  09-13-2013 16:12   130913 Fira Mono OT/
     6148  08-28-2013 23:13   130913 Fira Mono OT/.DS_Store
        0  09-13-2013 16:13   __MACOSX/
        0  09-13-2013 16:13   __MACOSX/130913 Fira Mono OT/
       82  08-28-2013 23:13   __MACOSX/130913 Fira Mono OT/._.DS_Store
    71748  09-10-2013 14:53   130913 Fira Mono OT/FiraMonoOT-Bold.otf
    68848  09-10-2013 14:53   130913 Fira Mono OT/FiraMonoOT-Regular.otf
        0  09-13-2013 16:13   130913 Fira Sans OT/
     6148  08-28-2013 23:13   130913 Fira Sans OT/.DS_Store
        0  09-13-2013 16:13   __MACOSX/130913 Fira Sans OT/
       82  08-28-2013 23:13   __MACOSX/130913 Fira Sans OT/._.DS_Store
   113432  09-10-2013 14:17   130913 Fira Sans OT/FiraSansOT-Bold.otf
   116844  09-10-2013 14:17   130913 Fira Sans OT/FiraSansOT-BoldItalic.otf
   109364  09-10-2013 14:17   130913 Fira Sans OT/FiraSansOT-Light.otf
   112544  09-10-2013 14:17   130913 Fira Sans OT/FiraSansOT-LightItalic.otf
   112860  09-10-2013 14:17   130913 Fira Sans OT/FiraSansOT-Medium.otf
   115896  09-10-2013 14:17   130913 Fira Sans OT/FiraSansOT-MediumItalic.otf
   110244  09-10-2013 14:17   130913 Fira Sans OT/FiraSansOT-Regular.otf
   112660  09-10-2013 14:17   130913 Fira Sans OT/FiraSansOT-RegularItalic.otf
---------                     -------
  1056900                     19 files

incorrect style flags in most of the Italic faces in Fira Sans 3.1

(Copied from https://bugzilla.mozilla.org/show_bug.cgi?id=987872#c18)

In a number of the files, the fsSelection field in the 'OS/2' table is not set correctly. Bit 0 of that field is supposed to be set for italic faces, but in most cases it's missing. (Only FiraSans-Italic.otf and FiraSans-BoldItalic.otf have it set.)

At the weights where this is missing, it's basically a crapshoot whether you'll get the "regular" or the "italic" version, as they have identical attributes for our font-selection process.

(The italic style should also be reflected in the macStyle field of the 'head' table, though I think it's the OS/2 bit that is more important for our purposes here.)

Supported codepages info incomplete in some fonts

Fira Sans Bold and Medium are the only ones that have all supported codepages marked (CP-125...0,1,2,3,4,7,8)

Whereas:
Light, Light-Italic,
Regular, Regular-Italic,
Medium-Italic,
and Bold-Italic
all have only CP-125...0,2,4,7 marked in font metadata.

The issue is present in both OTF and TTF versions.

Cannot select Fira Mono as monospaced font under KDE

I am running KDE on OpenSuSE 13.1.
Within almost any font chooser dialog, I cannot select Fira Mono (TTF Version 3.111) as a monospaced font, although the font is installed and selectable in LibreOffice, for instance.

I've played around with fontforge a bit. It doesn't complain about having different advances or something. It does however complain about erroneous minima/maxima.

Is there any workaround that enables me to select that font?

(Demo) Fonts still get downloaded if locally installed

Even though I've installed the TTF and OTF copies of the Fira Sans fonts, the fonts specified in the CSS @font-face at-rules are getting loaded.

This is because the local rules should be something like

src: local('Fira Sans'), ...

instead of

src: local('Fira Sans Light'), ...

Although the spec says otherwise:

Just as a @font-face rule specifies the characteristics of a single font within a family, the unique name used with local() specifies a single font, not an entire font family.

We could change the WOFFs, but I'd recommend just fixing the locals:

src: local('Fira Sans Light'),
     local('Fira Sans'), ...

Differentiate curly braces from parens in Fira Mono

Right now curly braces and parens are not that far from each other, so when I'm looking through code I need to pay more attention to distinguish them.

Fira Mono

I love Monaco for this, as all the different braces, parens and brackets are really different:

Monaco

If would be nice if those symbols were more different in Fira Mono too :)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.