21–30 of 526 posts
Earlier quoted context omitted.
That is not Python.
It's real-world Python. Why do you think stuff like SciPy are so popular?
Rather real world Fortran, C and C++ with Python glue code.
Just like Tcl, Ruby or whatever scripting language with the same glue code would get out of it.
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.
And a proper story for something similar to Swing, not even considering JavaFX here. There is Xamarin, but again, the platforms with Java compilers available.
And I am stating this as someone that works daily within .NET eco-system.
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 that Spring was a much better framework than Java EE, and have used it in most projects I've worked.
Oracle did not take a note from the Microsoft book and is really behaving that an evil corporate overlord.
It's clear at this stage that they bought Sun in order to slowly turn Java proprietary, and charge billions to the companies that are now fully Java-based for the next few decades.
I'm glad I saw the writing on the wall and switched, but the problem is that Java is still being taught a lot at schools, and school programs especially universities are hard to adapt and only change every 4-5 years or so.
(Not an expert on all the Java nomenclature / standards / politics) What does Eclipse foundation have to do with Java EE? Does this news sabotage their use of OpenJ9 somehow?
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.
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.
Earlier quoted context omitted.
Good luck with the performance over there.
The hot parts we can implement in C. There's not much overhead in crossing over to native code.
1) write everything in python because its easy and quick to do so.
2) its slow as.
3) abandon software and write it in something else, or, live on with slow ass software and blame python for being slow and rubbish forever more.
re-writing python in c is a hideously painful process, and its proven to be very unsuccessful practically.
Writing new code in c/c++/whatever and exposing a python api is where successful projects like numpy and tensorflow live.
python is very good at what it is, but no one is ever going to go and rewrite your python code in c to make it faster; its just going to be slow forever.
WORA was never perfect, I would be surprised if there was even a single JRE release that didn't note a breaking change in its release notes. So vendors should have a process to update their releases just for that already in place.
> The future is unclear because Oracle already started a blocking politics at the Eclipse Foundation’s board, where Oracle has a seat, and where unanimous decisions are needed.
They have no rules to out board members acting in bad faith?
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…
Ref:
- https://openjdk.java.net/projects/valhalla/
I think Eclipse Foundation is f*cked, not by Oracle but its bureaucracy, and inability to reinvent itself.