Earlier quoted context omitted.
Wonder what database they are using.
period correct? mysql 5.1
Oh no it was Oracle before Oracle bought MySQL, so it's gotta be Oracle db.
Java 16
71–80 of 327 posts
Re: Java 16
#72Java 16 for what? Does anybody really use > 8 in production?
Re: Java 16
#73Still on Java 8 at work :-/
Every thread about new Java version has the same comment all the time. Why share it? What kind of response do you seek?
Re: Java 16
#74Still on Java 8 at work :-/
Eight's JVM still ships with Minecraft, so that's not necessarily a bad thing. It's battle-proven.
Re: Java 16
#75Earlier quoted context omitted.
We see similar developments with C# borrowing features from F#, with records in v9, pattern matching, etc. While it's good for C#/Java, it does make it harder to push for adoption for a language such as Scala and F#. Why bother investing in the languages with a much smaller market share when the big boys adopt good bits and pieces from them constantly?
> Why bother investing in the languages with a much smaller market share when the big boys adopt good bits and pieces from them constantly? This won't always apply, but sometimes (many times?) there's a software endeavor that permanently feels on the margins of a programming language's capabilities, whatever that means. You may forego market share in order to be 5 or 10 years ahead of current practice. In other words…
Another thing to note that cutting edge languages do not always deliver great features , they also deliver with great frequency half baked features to be discarded or deprecated in few years. Also since most effort spent on language , tooling remain primitive and slow for long time.
So I do not see them a sure win for projects I work on.
Re: Java 16
#76Why they decided to change the keyword rules to use "non-sealed" is beyond me. Surely, there might be other choices? Closed/unclosed? Unsealed?
It's the same story in C++, co_await, co_yield. The sole purpose is not to break other people's code.
I think non_sealed would be better than non-sealed though, because AFAIK there used to be no identifiers with hifen before.
Re: Java 16
#77Earlier quoted context omitted.
There is an nginx in front of it. What was wrong with Apache?
Apache feels like a forgotten gem in the ops world. Everyone moved onto Nginx and at some point will run into some use-case that needs a feature that's only in Nginx+. And since Nginx+ is so expensive people end up just patching the OSS Nginx with the modules they need. But that whole time Apache was there with every conceivable battery and feature already included.
[deleted]
Re: Java 16
#78Very cool to see that Scala continues to have a huge impact on Java’s roadmap. Records and Sealed Classes are borrowed from Scala. Could be not the best news for new Scala adoption, but good news for developers having better abstractions in Java Edit: Kotlin, and other languages should also mentioned since they also include similar features. I still think Scala has had the most influence over the years.
> Records (...) are borrowed from Scala.
I think records already existed in FORTRAN and other languages like ALGOL-60. C has structs, too.
Re: Java 16
#79Man, I hope the migration to Java 11 that my infrastructure team started 18 months ago is going okay.
Re: Java 16
#80Earlier quoted context omitted.
> Why bother investing in the languages with a much smaller market share when the big boys adopt good bits and pieces from them constantly? This won't always apply, but sometimes (many times?) there's a software endeavor that permanently feels on the margins of a programming language's capabilities, whatever that means. You may forego market share in order to be 5 or 10 years ahead of current practice. In other words…
Another thing to note that cutting edge languages do not always deliver great features , they also deliver with great frequency half baked features to be discarded or deprecated in few years. Also since most effort spent on language , tooling remain primitive and slow for long time. So I do not see them a sure win for projects I work on.
Great point about half-baked features. The investment boils down to risk-reward. Can we say that the features that are introduced into Java at this point are features that have stood the test of time in other languages?