3 ms·
The Java time package has been a disaster for 20 years until Java 8, before that everyone was using Joda. As for generics have a look at what C# does for "prope
by Thaxll 7y ago
The Java time package has been a disaster for 20 years until Java 8, before that everyone was using Joda. As for generics have a look at what C# does for "proper" generics.
- apta 7y agoI'm aware of what C# does, that's why I said it was a tradeoff. Compare the number of languages on the JVM to those on the CLR to see why they made this tradeoff. The JVM folks are working on improving generics even further in upcoming releases. I know about Joda time, that even another point in how mature the Java ecosystem is. There's no similar offering in golang.
- Const-me 7y ago> Compare the number of languages on the JVM to those on the CLR to see why they made this tradeoff IMO the main reason why people aren't creating more CLR language is unrelated to generics. You can compile many languages to CLR bytecode and never emit these ldelem/stelem/unbox.any instructions. The main reason is C# is good language, and it evolves fast enough. I don't believe Java developers deliberately crippled Java to incentivize third parties to develop more JVM languages.
- repolfx 7y agoJava Time is a renamed Joda Time with some improvements, from the same guy who did Joda Time. It's a pretty great example of Java being defined by its community actually.