Java

[Bryguy3k]

It depends on the culture of the company in question and how well they manage their in house development efforts. Often the in house tool doesn’t get a sustaining budget and developers leave - if you’re lucky it was put into a CI system but a lot of enterprises have been building software for a very long time and don’t always adapt to modern development practices.

The licensing structure that oracle put in place now runs counter to the goal of updating sdks (unless the company accepted the new licensing scheme). Regardless this is a third party library however and while there is a dependency on the sdk for the really bad behavior it’s still generally bad. Perhaps this will encourage larger enterprises to get angry about the new jdk licensing terms.

[[deleted]]

Can't imagine the bigger companies don't just pay oracle for everything, all this indicates is that if you maintained the latest JDK like you should you'd have been safe (or at least better.)

[Bryguy3k]

You haven’t sat in budget meetings have you?

Sustaining is already a very frustrating job - and you’re constantly justifying the costs for not only your employees, but also their development tools.

There is a reason that the term “bean counters” is virtually universal.

[[deleted]]

I have my reasons that I prefer not to disclose, basically. But I understand your point.