Negotiations Failed: How Oracle Killed Java EE • Hacker News Board

Re: Negotiations Failed: How Oracle Killed Java EE

#521

Post by cutler » Wed, May 08, 2019, 11:08 PM UTC

philliphaydon wrote: post #379

cutler wrote: post #364

Earlier quoted context omitted.

If you're looking to get into C# 8.0 you're out of luck if using OS X. Visual Studio 2019 for Mac offers .Net Core 3.0 as an option if you have it installed but Mono hasn't caught up with C# 8.0 so isn't available. So much for cross-platform development - it seems OS X is still an afterthought.

What would you need mono for? If you’re using .net core...

Download Visual Studio for Mac 2019 and you won't find C# 8.0 listed under the project's language options. I'm referring to the Mac here where I understood Mono is still the way .Net Core is implemented.

Re: Negotiations Failed: How Oracle Killed Java EE

#522

Post by AlexCoventry » Fri, May 10, 2019, 3:41 AM UTC

threeseed wrote: post #51

bborud wrote: post #41

Oracle makes Java a risk factor in all projects. I stopped approving new Java projects in my team 2 years ago after we switched to Go. This wasn’t a decision we took lightly and it took almost a decade for me to be comfortable with leaving Java behind. But it is the right thing to do. Oracle is not trustworthy.

Strange attitude to take when you can just target OpenJDK and then it is completely irrelevant what Oracle does or does not do. The fact is that every single one of the largest companies has some Java or Scala code within their core platform. And none of them have ever raised Oracle as a risk.

It's sane to be leery about entering into any kind of contract with a counterparty as grasping and merciless as Oracle has proven to be. If they find an exploit in the GPL, Java projects are in for a bad time.

Re: Negotiations Failed: How Oracle Killed Java EE

#523

Post by ptx » Sat, May 11, 2019, 12:24 PM UTC

repolfx wrote: post #160

bharatm wrote: post #106

Earlier quoted context omitted.

They did research not because they want to support Java community, but because they want to make gains from making it proprietary.

Then why is their research open source? GraalVM is on github.

To entice people to license the full version of GraalVM, which isn't open source.

Re: Negotiations Failed: How Oracle Killed Java EE

#524

Post by cutler » Sat, May 11, 2019, 9:51 PM UTC

jongalloway2 wrote: post #403

cutler wrote: post #364

Earlier quoted context omitted.

If you're looking to get into C# 8.0 you're out of luck if using OS X. Visual Studio 2019 for Mac offers .Net Core 3.0 as an option if you have it installed but Mono hasn't caught up with C# 8.0 so isn't available. So much for cross-platform development - it seems OS X is still an afterthought.

Why? On OSX, just use Visual Studio Code and .NET Core: https://weblogs.asp.net/dixin/c-8-0-in-depth-setup-c-8-0-and...

That's a Windows guide.

Re: Negotiations Failed: How Oracle Killed Java EE

#525

Post by floriol » Sun, May 12, 2019, 12:59 PM UTC

nullwasamistake wrote: post #344

vfc1 wrote: post #23

The Java ecosystem has been slowly dying for years, it's already the new Cobol at this stage. I have the impression that a lot of the mindshare has switched to the Node and Javascript ecosystem, especially the frontend devs, via the Typescript / Angular path, which is a natural path to Java developers due to the comfort given by familiar concepts like static types, classes, etc. When I used to do Java, I always found…

Java is much closer to C++ than COBOL. COBOL has been massively obsolete for decades. Java has a lot of historical cruft but the basic syntax is still somewhat modern, mostly based off of C++ and agruable better. Like C++, it's modern features are being slowly added. There's a huge difference between Java 8 and 11, in performance and features. Innovation is hardly dead. Java EE and Spring are both terrible. I recomme…

Why do you think Java EE is terrible?

Re: Negotiations Failed: How Oracle Killed Java EE

#526

Post by floriol » Sun, May 12, 2019, 1:07 PM UTC

mbell wrote: post #330

smadge wrote: post #11

Earlier quoted context omitted.

I never used a flow blown Java EE web application server, but the various APIs I used like JDBC, JAX-RS, and JPA were generally well thought out and pleasant enough to work with. It would be a shame if these interfaces/specifications became proprietary.

Without knowing it you have cherry picked possibly the only good parts of Java EE. The rest that constitute a 'full blown' Java EE stack are horrific disasters (JSF, EJB, etc).

Would you mind showing any platform's solution to the problems that java EE solves? I have yet to see any competitor technology solve transaction management as elegantly as EJB's does.