Sure! It won’t comply, though.

Microsoft has a history of doing so, both with Minecraft customers and others. They just don’t care.

Some web applications force me to open their screens in separate tabs and windows, by making the screens remove any filtering on revisit by back button. And thus I have 20 tabs open that all start with the same meaningless word.

“Could”.

All the good things Records bring are stifled by JPA and DAO conventions and requirements. I really hate JPA for that reason, and have avoided Hibernate in favor of my own DAO implementations.

Records will slash thousands of lines of code from my implementation and will make it infinitely easier to maintain, and trust down-stream.

With some of my smaller clients, the CIO is the same as the CTO and the same as the IT Director. There, IT is developers, too.

Enterprise will cause a boom in hiring VBA devs to migrate legacy apps to other programming languages, then hear Microsoft will extend support for a few more years, then fire all those VBA devs again. If Microsoft had some wits, they’d create easy tools to migrate VBA to C#.

Wouldn’t it face the exact same security issues as VBA, with drive-by installs of obfuscated malware and executions of arbitrary code?

Sure! I wrote all about it over on Medium: https://medium.com/@aev_software/java-jakarta-soap-wsdl-client-fails-to-read-soap-message-for-logging-38087a63ea6d

To summarize: custom logging handlers failed after upgrading to version 3, because the underlying implementation that exports a message as a SOAP message is broken.

That indeed is annoying.

Cool. Just what I need: yet another version of a JDK/JRE to test. I feel like I spend more time testing these for regressions than I spend developing functionality for my clients. Anyway. Good for Adoptium and those who found and solved this bug.

I started using Jakarta half a year ago, as it was promised to be the de-facto way to build a SOAP client that speaks to a WSDL server. Oh boy: growing pains. Did not expect that 2 decades of developer experience in Java EE would amount to nothing, for the people who implemented Jakarta. As impressive as the effort may be, the inexplicable regressions we faced when we got forced to upgrade to version 3 proved quite cumbersome.

So they say. Remember they also promised not to track users, keep trackers away, and keep your browsing experience ad-free. They came back from that within a year.

One would switch to a free JVM when other JVMs change their licenses from free to paid. OpenJ9 was the first free JVM to which I got introduced. Knowing it was based on the work by IBM, known for high performance and low memory footprint, it was a simple choice.

Vivaldi has no choice. They have built their browser on Blink, which is made by Google. Google will force them to comply. Their way out would be to go back to the Opera web browser, which they gave up on over a decade ago.

The effect those people will have on profit margins probably are negligible, given the large amount of people using Google-created web browsers already.

Great article. Well written, with just the right amount of detail for me.

Looks like a problem with your theme. Try a completely fresh profile with no themes installed.

Right! I had used streams a couple of times but for most work had switched to Eclipse Collections. Some payloads just work better when streamed and I was left wondering why nothing happened!

Holy cow it’s fast!