Of course hinted glyphs would look better on Windows. Windows screens are why font hinting was invented. But they would not on eInk. Directly from Wikipedia; font hinting is the use of mathematical instructions to adjust the display of an outline font so that it lines up with a rasterized grid.
The key word here is
rasterized grid. This means geometrically aligned pixels of a computer (or smartphone) screen. All pixels are on the same lines on those screens, like boxes perfectly distributed. But electronic paper isn't created so. While it has geometrically aligned pixels, they are not used to show us the glyphs on the screen. The image is rendered between them haphazardly. This image show it:
The text on screen is created by the black and white dots you see here. This macro of a Kindle explains it better than words:
So, in effect, there are no rasterized grid in epaper that font hinting could understand. Hinting depends on rasterized grids, epaper doesn't have it. Moreover, hinting is a massive job to do properly. I greatly doubt that JSWolf spend months hand-hinting this type. And if he did, it was an exercise in futility. Sorry about that.
Hinting is also not that usable in high-ppi screens (
http://blog.typekit.com/2013/05/01/hi-dpi-typography/). The reason hinting exists is to make type look good at low resolutions screens. eInk isn't low resolution anymore, and more importantly, it isn't geometrically aligned when you look at it from outside. There is no way hinting could be useful, and there absolutely no way autohinting (which works on an assumption of an usual computer screen) can work at all. It might not make things worse, but it definitely can't make things better. It is impossible.
JSWolf, if you are going to keep claiming that I am wrong, I expect something more than just you saying it works better. Explain why it works, please.