Earlier quoted context omitted.
Time to switch to C#. Funny how it took Oracle to do what C# originally intended to do: kill Java.
hand up uh not as experienced as most people on HN, what's the hate for c#? I went from vb6 to VB.net then c# and while I fully admit I'm a casual coder, i haven't had an issue (with what I do, which is voice to string primarily) so far. Is there something better for this I perhaps should look into?
Negotiations Failed: How Oracle Killed Java EE
31–40 of 526 posts
Re: Negotiations Failed: How Oracle Killed Java EE
#32« Oracle already started a blocking politics at the Eclipse Foundation’s board, where Oracle has a seat, and where unanimous decisions are needed. Oracle now has the power, and apparently will use that power, to block the foundation’s future. It demonstrated that power already in a board meeting, where they had the sole vote against an otherwise unaimous move. » I hope other organisations with a director from Oracle…
In the EU the same is happening. Poland and Hungary have found a loophole allowing them to ignore EU rules and sanctions while still profiting from subsidies and market access.
All sanctions against a member state require unanimous-1 (all states except the sanctioned member) votes and Poland is vetoing all sanctions against Hungary, and Hungary all sanctions against Poland.
Re: Negotiations Failed: How Oracle Killed Java EE
#33The 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…
Where I am (geographically, company wise and ecosystem) Java and the Java ecosystem are very much thriving.
Re: Negotiations Failed: How Oracle Killed Java EE
#34The 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…
Re: Negotiations Failed: How Oracle Killed Java EE
#35The 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…
Working in the JVM world I'm always surprised to hear that its dying, the JVM and Java moves faster forward than ever, Graal is about to go 1.0, a bunch of very interesting (very) low latency GCs are in the pipe (for example ZGC and Shenandoah) and lots of other interesting projects like Valhalla promise to keep the JVM relevant for the next 20 years. Oracle have made some moves to monetize on parts of its investment…
So how is this "JVM world" escaping the grip of Oracle? E.g. graalvm is directly Oracle's, or am I missing something? Specifically, what is preventing any of the Java-related things people use now (including those that you mention) to end like the OP is describing?
Asking as somebody outside of that world, but interested "how much it's worth considering" under the given circumstances (Oracle being Oracle, demanding a lot of money for everything Oracle's that some company could use, and owning a lot of that "world"). Where are the boundaries? What is safe and outside of reach of Oracle? E.g. what is safe for a small company to use?
Re: Negotiations Failed: How Oracle Killed Java EE
#36Re: Negotiations Failed: How Oracle Killed Java EE
#37« Oracle already started a blocking politics at the Eclipse Foundation’s board, where Oracle has a seat, and where unanimous decisions are needed. Oracle now has the power, and apparently will use that power, to block the foundation’s future. It demonstrated that power already in a board meeting, where they had the sole vote against an otherwise unaimous move. » I hope other organisations with a director from Oracle…
For me it's more a lesson about how unanimous votes, or unanimous - N can become problematic. In the EU the same is happening. Poland and Hungary have found a loophole allowing them to ignore EU rules and sanctions while still profiting from subsidies and market access. All sanctions against a member state require unanimous-1 (all states except the sanctioned member) votes and Poland is vetoing all sanctions against…
Re: Negotiations Failed: How Oracle Killed Java EE
#38Earlier quoted context omitted.
Time to switch to C#. Funny how it took Oracle to do what C# originally intended to do: kill Java.
hand up uh not as experienced as most people on HN, what's the hate for c#? I went from vb6 to VB.net then c# and while I fully admit I'm a casual coder, i haven't had an issue (with what I do, which is voice to string primarily) so far. Is there something better for this I perhaps should look into?
¹ The story is Steve Balmer was very anti-open source and forbade most interop or support for Linux, so this only could start changing when he left in 2014.
² You always had Mono with is why Unity and GNOME could also use C#, but is was very niche outside of Unity.
Re: Negotiations Failed: How Oracle Killed Java EE
#39Earlier quoted context omitted.
Time to switch to C#. Funny how it took Oracle to do what C# originally intended to do: kill Java.
hand up uh not as experienced as most people on HN, what's the hate for c#? I went from vb6 to VB.net then c# and while I fully admit I'm a casual coder, i haven't had an issue (with what I do, which is voice to string primarily) so far. Is there something better for this I perhaps should look into?
Re: Negotiations Failed: How Oracle Killed Java EE
#40Well, 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.
JVM is still the best platform for any type of back-end application. It has the widest array of libraries, is proven to run on any type of hardware and comes standard on every OS and every cloud instance.
.Net is a great platform and all but it still hasn't done enough to really merit switching teams. Especially when you have Scala, Kotlin, Clojure etc to pick from.