When comparing Native vs Google Noto Sans Mono, the Slant community recommends Native for most people. In the question“What are the best programming fonts?” Native is ranked 79th while Google Noto Sans Mono is ranked 102nd.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Readable
Pro Consistent character widths between the italics and weights
Within Native's weights and styles, each character occupies 580 points of space. This ensures code does not become misaligned if a developer prefers certain callouts in a different style.
Pro The regular weight is free for Desktop, Web, and App Licensing
The regular weight can be picked up free of charge on MyFonts or Fort Foundry’s site.
Pro No alignment issues when switching between styles
Pro Italics are given a lot of differentiation
Pro Excellent support for Unicode characters
Unicode uses 16 bits per character, meaning that it can represent more than 65,000 unique characters.
Cons
Con Not FREE
Not free and hard to find.
Con Zero is difficult to identify
As it's not dotted or slashed, "0" is more difficult to distinguish.
Con Non-monospace ligature replacements for 'fl', 'fi', 'ffl', 'ffi'
By default, the substrings 'fl', 'fi', 'ffl', and 'ffi' are each crammed into one character width, making it not a truly monospace font. For example, the word 'flag' is rendered as three characters wide.
Con Letters capital 'i' and lowercase 'L' are too similar
The only difference is almost unnoticable.
Con Difficult to distinguish between a period and acomma as well as a colon and a semi-colon
Comma has very small tail, making it difficult to distinguish from a period (full stop). Same applies to colon and semi-colon.