7 ms·

As pron always says.. that's a risk of staying on an LTS release. You're choosing to not receive updates.

by vips7L 3y ago

geodel 3y ago
It seems to me by design or by indifference Java is now tired of JVM ecosystem languages at large who claim innovation by surface level changes while relying heavily on JVM bedrock. Now Java is moving fast and they are taking JVM compiler, runtime, class metadata etc along where Java, the language is headed.
- pjmlp 3y ago
  Not only Java, that is the fate of all guest languages, as they don't evolve alongside the platform, always require additional tooling and most language cultures than start making their own little islands of idiomatic libraries instead of directly using platform libraries. Since most platforms are leaky, one ends up needing to master two ecosystem in parallel, eventually it gets tiring and always cost extra in development. C++, Objective-C and Typescript get around this problem in UNIX and Web, as they are extensions of the platform languages, not something completely different.
  - geodel 3y ago
    Yep agree with all you said. Nowadays new job every year people at work are scaring me with their enthusiasm to replace decades old solid Java applications which are performant and working fine with Kotlin and what not.
    - Alupis 3y ago
      I wouldn't advocate for replacing/re-writing old stuff - but you should try out Kotlin for backend work. It's amazing. Java programmers will have only a small learning curve before feeling productive, and can gradually get more comfortable with idomatic Kotlin as they progress through their journey. Kotlin, as a language, was very well through out, letting you use as much or as little of it as you are comfortable with.
      - pjmlp 3y ago
        It is still another syntax, with idioms moving away from JVM, their own little islands of Kontlin only libraries, and only works on InteliJ/Android Studio. I don't see any value in Kotlin outside Android shops.
        jcadam 3y ago
        > I don't see any value in Kotlin outside Android shops. Developer experience is important to some people - not just devs, but those who seek to recruit and retain good ones. Of course, if you're looking to hire massive numbers of butts-in-seats (gov work, large enterprise shops, etc) I suppose Java is probably the ideal choice.
        Alupis 3y ago
        While true it has it's own syntax, the syntax is better than Java and more ergonomic. With that said, you can write Java in Kotlin - and by that I mean Kotlin code that looks almost exactly like Java. Heck, you can have .java and .kt source within the same project all mixed together if you want. Kotlin libraries are interoperable with Java and vice versa. In some specific cases, a Kotlin library needs a little syntactic sugar to make it work with Java like a Java developer would expect, but it's easy to do. Going the other direction though - Java library used in Kotlin, zero issues, it just works. Some Java developers don't even realize they're already using Kotlin - take a look at OKHttp and friends... Lastly, there's Kotlin support is all major IDE's, including IntelliJ of course, but also Eclipse and likely whatever editor/ide you prefer. Kotlin is basically just a bunch of libs. I would argue Kotlin is better outside of Android than in Android. For backend work, particularly when coupled with Spring/Boot, it's freaking amazing. The Spring team has put in an impressive amount of work to make Kotlin a first-class language within the ecosystem, and it really shows.
        pjmlp 3y ago
        Try to call Kotlin co-routines from Java. Telling me there is Kotlin support in Eclipse only tells me you never actually tried it, specially after JetBrains ramped down the team that was doing the now stale plugin.
  - never_inline 3y ago
    That's an interesting hypothesis. Is that applicable to platforms other than programming languages?
  - imtringued 3y ago
    That would only be a bad thing if the Java ecosystem was good to begin with. From my perspective it is terrible enough that the language specific wrapper library has 10x to 100x the usability of the Java option if you use it directly from Java. For example, GORM for Groovy is significantly better than Hibernate even though it is built on top of Hibernate. It is so good that I chose to use groovy once, not because it made sense but simply because Hibernate is so terrible, the cost of a different language was outweighed by it. I don't give a damn about most JVM features. They don't change the crap ecosystem at all. I personally despise the JVM for being incredibly memory inefficient as well. None of this is going to change.
- Tainnor 3y ago
  And many developers are tired of Java making minuscule improvements to developer ergonomics while pretending to be progressing, when even now, it doesn't have features that other languages have had for 30 years.
  - kaba0 3y ago
    Based on pure statists about the number of important, business critical java-applications that run most of the internet, it seems like it just straight doesn’t matter in any significant way.
    - Tainnor 3y ago
      Maybe it doesn't matter to you, but it does matter to me. All the power to people who enjoy working in Java, but that doesn't have to make me like it.
- vips7L 3y ago
  The JVM and Java the language have always been intertwined. The same people that develop the language, develop the VM. Lots of optimizations in the VM know specifically about Java the language idioms and implementation details. Check out this function which helps determine if instance fields are trusted: https://github.com/openjdk/jdk/blob/edd454b502b9bacde55492820e52655bbac63b89/src/hotspot/share/ci/ciField.cpp#L219 https://github.com/openjdk/jdk/blob/edd454b502b9bacde5549282...

As pron always says.. that's a risk of staying on an LTS release. You're choosing to not receive updates.

by vips7L 3y ago

As pron always says.. that's a risk of staying on an LTS release. You're choosing to not receive updates.

It seems to me by design or by indifference Java is now tired of JVM ecosystem languages at large who claim innovation by surface level changes while relying heavily on JVM bedrock. Now Java is moving fast and they are taking JVM compiler, runtime, class metadata etc along where Java, the language is headed.

pjmlp 3y ago
Not only Java, that is the fate of all guest languages, as they don't evolve alongside the platform, always require additional tooling and most language cultures than start making their own little islands of idiomatic libraries instead of directly using platform libraries. Since most platforms are leaky, one ends up needing to master two ecosystem in parallel, eventually it gets tiring and always cost extra in development. C++, Objective-C and Typescript get around this problem in UNIX and Web, as they are extensions of the platform languages, not something completely different.
- geodel 3y ago
  Yep agree with all you said. Nowadays new job every year people at work are scaring me with their enthusiasm to replace decades old solid Java applications which are performant and working fine with Kotlin and what not.
  - Alupis 3y ago
    I wouldn't advocate for replacing/re-writing old stuff - but you should try out Kotlin for backend work. It's amazing. Java programmers will have only a small learning curve before feeling productive, and can gradually get more comfortable with idomatic Kotlin as they progress through their journey. Kotlin, as a language, was very well through out, letting you use as much or as little of it as you are comfortable with.
    - pjmlp 3y ago
      It is still another syntax, with idioms moving away from JVM, their own little islands of Kontlin only libraries, and only works on InteliJ/Android Studio. I don't see any value in Kotlin outside Android shops.
      - jcadam 3y ago
        > I don't see any value in Kotlin outside Android shops. Developer experience is important to some people - not just devs, but those who seek to recruit and retain good ones. Of course, if you're looking to hire massive numbers of butts-in-seats (gov work, large enterprise shops, etc) I suppose Java is probably the ideal choice.
      - Alupis 3y ago
        While true it has it's own syntax, the syntax is better than Java and more ergonomic. With that said, you can write Java in Kotlin - and by that I mean Kotlin code that looks almost exactly like Java. Heck, you can have .java and .kt source within the same project all mixed together if you want. Kotlin libraries are interoperable with Java and vice versa. In some specific cases, a Kotlin library needs a little syntactic sugar to make it work with Java like a Java developer would expect, but it's easy to do. Going the other direction though - Java library used in Kotlin, zero issues, it just works. Some Java developers don't even realize they're already using Kotlin - take a look at OKHttp and friends... Lastly, there's Kotlin support is all major IDE's, including IntelliJ of course, but also Eclipse and likely whatever editor/ide you prefer. Kotlin is basically just a bunch of libs. I would argue Kotlin is better outside of Android than in Android. For backend work, particularly when coupled with Spring/Boot, it's freaking amazing. The Spring team has put in an impressive amount of work to make Kotlin a first-class language within the ecosystem, and it really shows.
        pjmlp 3y ago
        Try to call Kotlin co-routines from Java. Telling me there is Kotlin support in Eclipse only tells me you never actually tried it, specially after JetBrains ramped down the team that was doing the now stale plugin.
- never_inline 3y ago
  That's an interesting hypothesis. Is that applicable to platforms other than programming languages?
- imtringued 3y ago
  That would only be a bad thing if the Java ecosystem was good to begin with. From my perspective it is terrible enough that the language specific wrapper library has 10x to 100x the usability of the Java option if you use it directly from Java. For example, GORM for Groovy is significantly better than Hibernate even though it is built on top of Hibernate. It is so good that I chose to use groovy once, not because it made sense but simply because Hibernate is so terrible, the cost of a different language was outweighed by it. I don't give a damn about most JVM features. They don't change the crap ecosystem at all. I personally despise the JVM for being incredibly memory inefficient as well. None of this is going to change.
Tainnor 3y ago
And many developers are tired of Java making minuscule improvements to developer ergonomics while pretending to be progressing, when even now, it doesn't have features that other languages have had for 30 years.
- kaba0 3y ago
  Based on pure statists about the number of important, business critical java-applications that run most of the internet, it seems like it just straight doesn’t matter in any significant way.
  - Tainnor 3y ago
    Maybe it doesn't matter to you, but it does matter to me. All the power to people who enjoy working in Java, but that doesn't have to make me like it.
vips7L 3y ago
The JVM and Java the language have always been intertwined. The same people that develop the language, develop the VM. Lots of optimizations in the VM know specifically about Java the language idioms and implementation details. Check out this function which helps determine if instance fields are trusted: https://github.com/openjdk/jdk/blob/edd454b502b9bacde55492820e52655bbac63b89/src/hotspot/share/ci/ciField.cpp#L219 https://github.com/openjdk/jdk/blob/edd454b502b9bacde5549282...