Earlier quoted context omitted.
And they created a whole language and ecosystem (C# / .Net), even before Oracle bought Sun, so they wouldn't be dependent on a 3rd party for that.
Ironically, .NET was created because MS tried and failed to take over the Java ecosystem using an Embrace, Extend, Extinguish approach that ran afoul of SUN's licencing deal with them.
Negotiations Failed: How Oracle Killed Java EE
501–510 of 526 posts
Re: Negotiations Failed: How Oracle Killed Java EE
#502Earlier quoted context omitted.
You seem really traumatized with whatever happened there regarding jobs. No job is secure.
That’s kind of the point. No job is secure that’s why it’s not a great idea for someone not to keep their skills current with the market and keep their heads down. It’s not hard to project that Windows only development is a dead end when even Microsoft is outright saying that all of its energy is going toward .Net Core and they have been moving toward cross platform development for the last half decade.
The days of pure coding jobs are over.
Re: Negotiations Failed: How Oracle Killed Java EE
#503Earlier quoted context omitted.
Excelsior JET is only one among many. As for your problem, it looks very strange to me, only similar to compiling C and C++ on underpowered hardware.
Which are the other ones? I know of GCJ, which is dead, and Graal, which from what I hear takes hours to compile small programs.
For example, PTC, Aicas, Aonix (now also owned by PTC), IBM RealTime WebSphere, some variants of J9, Android since version 5 (although it isn't technically a JVM), RobotVM, Codename ONE, GluonVM, IBM i JVM (uses OS/400 TIMI), JRockit.
Re: Negotiations Failed: How Oracle Killed Java EE
#504Earlier quoted context omitted.
To write the same functionality I need 10x the packages (from 9x vendors) in JavaScript compared to a Java/.NET ecosystems. The infamous left-pad packages is a sample for something found in the base class libraries of the other languages. And this does not only stand true for vulnerability analysis but also for other analyze jobs like for licenses or gdpr compliance. The amount of work is just higher with the amount…
I think the net amount of code ends up being pretty much the same, it's just spread over several repositories/sources/owners. That does mean it's more difficult without tooling to trawl through, but it's not like it's an order of magnitude or anything.
Java/.NET/Python ecosystems tend to be more professional with this regards. JavaScript catches up but is not completely there yet (you can see this with the amount of repositories who add licenses in 2016/2017 timeframe, years after creation).
Hence, same amount of code, much more work (it is a magnitude).
Re: Negotiations Failed: How Oracle Killed Java EE
#505Earlier quoted context omitted.
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.
> when you can just target OpenJDK and then it is completely irrelevant what Oracle does or does not do Yeah, Google thought the same
Re: Negotiations Failed: How Oracle Killed Java EE
#506Earlier quoted context omitted.
You mean it’s hard to keep track, even though you’ve responded to the posts? But if the post is concerning Java wouldn’t it be kinda of silly to bring up C++, C, Python, and JavaScript/TypeScript? What I did say that it was foolish from a long term career perspective not to see where the market is going and stick with a platform that even the vendor said is maintenance mode as far as .Net Framework and Windows Forms…
Just because I responded to all posts doesn't mean I am able to remember everything. It is also foolish to have senior devs focus on selling themselves as Language X dev, without any other skill to offer. I would rather have a VB 6 guy on the team that can do proper software architecture design, speaks fluently two European languages across our customer sites and is able weight what really matters across the delivery…
Re: Negotiations Failed: How Oracle Killed Java EE
#507Earlier quoted context omitted.
WebForms is a super legacy technology, to be fair. How many web API are supported today that originated 17 years ago? There are better uses of resources than to give that new life.
Might be, but some customers do pay to keep it alive.
The chances are that either (the hypothetical) you would either want to leave the company that is still focused on those technologies or the company would leave you long before your career is over. The last thing a person should want is to have on their resume in two years that their experience is any of those technologies.
There are still companies today using Visual Studio 2008 to support legacy ruggedized Windows CE devices. I have five years of experience with them and still get calls to develop for them today. I don’t go near those types of jobs.
Re: Negotiations Failed: How Oracle Killed Java EE
#508Earlier quoted context omitted.
That’s kind of the point. No job is secure that’s why it’s not a great idea for someone not to keep their skills current with the market and keep their heads down. It’s not hard to project that Windows only development is a dead end when even Microsoft is outright saying that all of its energy is going toward .Net Core and they have been moving toward cross platform development for the last half decade.
Developers that focus in only being good in tech, without any additional skill won't go far. The days of pure coding jobs are over.
Re: Negotiations Failed: How Oracle Killed Java EE
#509Earlier quoted context omitted.
In 1995-2005, JVM was a serious competitor for the web, it's why JavaScript was named Java Script.
javascript is named javascript for marketing purposes. your example is an almost stereotypical misunderstanding by people unfamiliar with java.
Re: Negotiations Failed: How Oracle Killed Java EE
#510The 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…
You can't compare these frameworks. They're in entirely different spaces, with different requirements and constraints.