3 ms·
The JVM has amazing, mature tooling, and a bunch of existing compile-to languages. If the goal is to do a productive exploration with some toys, that’s a good p
by sethaurus 3y ago
The JVM has amazing, mature tooling, and a bunch of existing compile-to languages. If the goal is to do a productive exploration with some toys, that’s a good place to start.
- awestroke 3y agoReally? What JVM tooling amazes you, specifically?
- baq 3y agoEverything that isn’t Java is top notch. JIT, GCs, debugging. It’s sad that Java the language sucked so bad for this long.
- pjmlp 3y agoThat is a matter of opinion, plenty of people like Java, the language.
- baq 3y agoJava today is a likable language. It was not expressive enough a few years ago which lead to major boilerplate copypasta and making do with abhorrent ’design patterns’ instead of well designed language features. Plenty of people liked it then I agree, can’t really understand why, because the simplicity argument just moved the complexity into libraries.
- pjmlp 3y agoJava was the Go of its time, specially when compared with the chaos of commercial C and C++ compilers. Java predates ISO C++, and the UNIX world was a mess of K&R C, and half backed ISO C89. Design patterns were invented for Smalltalk and C++, as much as people like to blame Java for them.
- schemescape 3y agoDoes anyone know if you could target the JVM without having to use UTF-16 for string encoding? Probably not justified, but that’s a hassle I’d want to avoid if I had any plans to support Unicode.