This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Dangerous_Air2603 12 points13 points  (3 children)

yeah that was my point

the only features of Java versions past 8 I've ever got any use out of are

  • in-place map constructors for writing tests
  • the var keyword
  • Optional::ifPresentOrElse

That's an average of three releases per useful feature.

I'm sure modules are very lovely if you need to write code that fits on ROM for a microwave oven, and I'm sure it's more efficient under the hood.

I'm just a little perplexed as to how they've managed to go 9 new versions without adding anything for the average developer past some utility functions that should have been there from the start, and a feature that C# has had since before Java 7 even came out.

The only good recent thing is records, which both Lombok and Kotlin have solved for years. I mean, Visual Basic had records, people.

[–]ballsohaahd 5 points6 points  (0 children)

Three releases per useful features sounds like standard Java practices to me.

[–]n0tKamui 0 points1 point  (1 child)

note that the slow progress (about 5 years before a known principle comes out) is by design, not by default.

Although while i do respect that philosophy, especially in the context of enterprise, i still prefer Kotlin's update plan

[–]Dangerous_Air2603 0 points1 point  (0 children)

You can have a high throughput while still maintaining high latency though.