This is the font that intended for using in non-antialised environments especially for programmers.
You may Download 7z-archive and use it freely (see "license" in archive).
1. It is TTF with embedded bitmap font into it. 2. It has no glyphs. More exactly all glyphs are the same - filled rectangles.
This has some consequences. Bad news is font is not scalable, you can use only embedded sizes, now only one size 16 pixels height. Good news is if you see letters not black rectangles you may be absolutelly sure that you see non-antialiased text.
3. It has ASCII symbols and Russian letters. 4. English and Russian and digits are in three slightly different styles.
Bad news is font is good for pure english or english+russian only. Good news is for russian programmers - you can distinguish between latin and russian letters and this makes life easier, trust me.
5. It's not fact it was my intension to make font nice for long reading of the sources. 6. It has bold variant but not italic variants. It's hard to do good italic on low resolutions.
When I started my work on mbb-font at the beginning of 2009 I was 44 and I thought that things are changing rapidly. I thought that after 2-3 years monitor resolutions will be about 200-300 dpi and it will be possible to use scalable fonts in my real programming process.
Now at the mid of 2013 I am 49 and I see that things are not changing so rapidly, I use the 96-dpi monitor at work and 102-dpi monitor at home. Of course there are many devices around me with 200-300 dpi and I have my own SurfacePro but my everyday programming environment is almost the same as 5 years ago.
Progress is slower than expected or it has not the same speed in all directions. The highest speed is in consumers' interests - at the moment this is mobile devices. But we, programmers, are not users. We have slightly different priorities. One of these - we need to work with texts on the screen hours and hours every day of weeks. And if users' priority is usually a reading speed we add reading accuracy.
On the other hand we don't really need scalability to read program sources. So we don't really need antialiasing.
And we don't need antialiasing because it pains our eyes. Yes, even Microsoft indirectly agreed with this fact. They told on one of MSDN forums that about 15% people feel uncomfortable with antialiased fonts. These are people mostly with good sight and they see every pixel at low dpi (up to 200).
Take care of your eyes.
Low percentage (15%) of us give some problems. First, it is very hard to explain others our problems with antialiased fonts. "But all use it, don't warry" - they say.
Second, vendors of software tools don't put this usability problem into first priority list. For example, VisualStudio 2012 uses WPF for rendering. And in editor window we always saw antialiased text apart from system's settings. In Update 1 things did not change. Only in Update 2 editor window takes into account system's settings. Now I see sharp perfect non-antialiased text. Thanks Microsoft.
So things are not much better than 5 years ago. That's why I created mbb-font that time and use it today for everyday programming. That's why I decided to explain.