Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Negotiations Failed: How Oracle Killed Java EE

headcrashing.wordpress.com

Post reply on HN
Print view View original

11–20 of 526 posts

Re: Negotiations Failed: How Oracle Killed Java EE

#11

Post by smadge »

Illniyar wrote: post #2

Well, mmm, good riddance? I suppose this will cause a lot of hardships to a lot of people who need to maintain JavaEE, but the fact that Java EE is no more is nothing but good. It is a nightmare case of overengineering.

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.

Re: Negotiations Failed: How Oracle Killed Java EE

#13

Post by chpmrc »

pjmlp wrote: post #7
hajderr wrote: post #5

heads over to Python :)

Good luck with the performance over there.

Before the language becomes a performance bottleneck there is so much stuff to consider that it quickly becomes clear how the choice of language doesn't really make a difference, except in special cases such as embedded systems.

Re: Negotiations Failed: How Oracle Killed Java EE

#16

Post by rbanffy »

pjmlp wrote: post #6
sheepdestroyer wrote: post #3

Oracle never fails to show off how evil they are.

While there is some truth to it,they did more research for Java than Sun ever did, and no one else cared to buy Sun.

That's, sadly, true. At the time of acquisition, Sun was only a shadow of its former glory...

Re: Negotiations Failed: How Oracle Killed Java EE

#17

Post by rbanffy »

pjmlp wrote: post #15
rbanffy wrote: post #14

Earlier quoted context omitted.

The hot parts we can implement in C. There's not much overhead in crossing over to native code.

That is not Python.

It's real-world Python. Why do you think stuff like SciPy are so popular?

Re: Negotiations Failed: How Oracle Killed Java EE

#18

Post by pjmlp »

chpmrc wrote: post #13
pjmlp wrote: post #7

Earlier quoted context omitted.

Good luck with the performance over there.

Before the language becomes a performance bottleneck there is so much stuff to consider that it quickly becomes clear how the choice of language doesn't really make a difference, except in special cases such as embedded systems.

A language that requires C for anything regarding performance is only useful for scripting and learning to program.

Re: Negotiations Failed: How Oracle Killed Java EE

#19

Post by masklinn »

DonHopkins wrote: post #4

>But once Eclipse products would be not vendor-neutral anymore, the EF’s tax exemption might become void, which would mean a financial fiasco, or possibly mean the end of the organization as a hole. I think the problem is Oracle's a-hole, in this situation.

Do not anthropomorphise the lawnmower.

Re: Negotiations Failed: How Oracle Killed Java EE

#20

Post by agumonkey »

DonHopkins wrote: post #8
Illniyar wrote: post #2

Well, mmm, good riddance? I suppose this will cause a lot of hardships to a lot of people who need to maintain JavaEE, but the fact that Java EE is no more is nothing but good. It is a nightmare case of overengineering.

Time to switch to C#. Funny how it took Oracle to do what C# originally intended to do: kill Java.

Nice joke (apparently bad taste for the HN crowd). That said is C# really great ? come on .. they have F#, and F > C. QED
Post reply on HN