News for hackers. Stuff that matters.
Re:Oracle to charge for Java from Jan 2019 by kamaal on Thursday August 09, 2018 @09:14AM (#17723887)
Signaling is everything here. Once you've announced that you are going to charge for something like this, you've also in a way announced you could charge for other things as well.

At that point, you are just better off using something else to insulate you from things like these.

>>Just don’t expect any future updates from Oracle, security or otherwise.

That's a very big problem for most shops.

>>With its huge ecosystem and modern toolsets such as Spring Boot Java is a highly viable option for developing new applications.

Spring Boot isn't a configuration less framework. Its basically a only one configuration works framework, change something small and nothing works. Also code comes out so unmaintainable no one apart from the original authors generally understands anything about it.

Re:Oracle to charge for Java from Jan 2019 by BjoernKW on Thursday August 09, 2018 @10:07AM (#17724286)
Your last statement simply isn’t true. I’ve been using Spring Boot for years in a variety of configurations and it works absolutely fine.
Re:Oracle to charge for Java from Jan 2019 by not_kurt_godel on Thursday August 09, 2018 @09:54PM (#17730135)
As long as we're going with anecdata, I'll add that in my experience Spring is a goddamn nightmare. I've spent X too many times in dependency hell with it and have vowed to never voluntarily use it again.
Re:Oracle to charge for Java from Jan 2019 by BjoernKW on Friday August 10, 2018 @03:27AM (#17731345)
That’s exactly the point of Spring Boot. It makes an opinionated choice of libraries that work well together so you don’t have to.