4 ms·

For me at least the main annoyance of using Java-based tools are issues like these: http://youtrack.jetbrains.com/issue/IDEA-57233 http://youtrack.jetbrains.com

For me at least the main annoyance of using Java-based tools are issues like these: http://youtrack.jetbrains.com/issue/IDEA-57233 http://youtrack.jetbrains.com/issue/IDEA-57233 . Had to install a non-official patched JVM to get the fonts to look decent, when all the other applications on the system render fonts just fine.

67726e 12y ago
To pick on Java is my point of contention. Every runtime has warts, If I did some digging I could find issues with any other environment. It just seems like folks pick on Java disproportionately. That might just be the HN echo chamber, but I don't see too many folks bitching about any other non-native runtime.
- deleted 12y ago
  [deleted]
dnesteruk 12y ago
Regrettably, fact of the matter is that fonts look bad on Java, particularly on Windows where Java-enabled programs are unable (for whatever reason) to leverage ClearType and thus get the antialiasing done just right.
shock 12y ago
That's exactly the reason I don't use Jetbrains' products (font rendering looks like crap in them on Linux) and stick with Eclipse. I installed the non-official patched JVM to get the font rendering to look good but I'm not going to depend on a product that requires me to tweak the JVM just to make the product look good. My ability to tweak the JVM might go away at any point since I can only patch OpenJDK and Jetbrains recommends the Oracle JDK. Then what? Suck it up and look at the ugly fonts? No, thanks! I'd rather use apps that use SWT and render fonts natively. The couple of Swing apps I use are open source and if I'm sufficiently motivated to continue using them I can port them to SWT or find some other compromise. I wish more people would feel the same, then, maybe, Jetbrains would find a solution, but ,alas, it seems too few people care for Jetbrains to take notice.

4 ms·

For me at least the main annoyance of using Java-based tools are issues like these: http://youtrack.jetbrains.com/issue/IDEA-57233 http://youtrack.jetbrains.com

by epidemian 12y ago

67726e 12y ago
To pick on Java is my point of contention. Every runtime has warts, If I did some digging I could find issues with any other environment. It just seems like folks pick on Java disproportionately. That might just be the HN echo chamber, but I don't see too many folks bitching about any other non-native runtime.
- deleted 12y ago
  [deleted]
dnesteruk 12y ago
Regrettably, fact of the matter is that fonts look bad on Java, particularly on Windows where Java-enabled programs are unable (for whatever reason) to leverage ClearType and thus get the antialiasing done just right.
shock 12y ago
That's exactly the reason I don't use Jetbrains' products (font rendering looks like crap in them on Linux) and stick with Eclipse. I installed the non-official patched JVM to get the font rendering to look good but I'm not going to depend on a product that requires me to tweak the JVM just to make the product look good. My ability to tweak the JVM might go away at any point since I can only patch OpenJDK and Jetbrains recommends the Oracle JDK. Then what? Suck it up and look at the ugly fonts? No, thanks! I'd rather use apps that use SWT and render fonts natively. The couple of Swing apps I use are open source and if I'm sufficiently motivated to continue using them I can port them to SWT or find some other compromise. I wish more people would feel the same, then, maybe, Jetbrains would find a solution, but ,alas, it seems too few people care for Jetbrains to take notice.