3 ms·

Oracle needs to refocus on Eclipse and leave Visual Code crap alone, focus on Eclipse and kick the enterprise Red Hat yahoos out of the Java space. Red Hat gave

Oracle needs to refocus on Eclipse and leave Visual Code crap alone, focus on Eclipse and kick the enterprise Red Hat yahoos out of the Java space. Red Hat gave up on developers when they split Red Hat into the enterprise version and Fedora garbage.

29athrowaway 3y ago
Eclipse must have started as a joke about covering the "Sun".
- rzzzt 3y ago
  "It turned out Sun wasnt the target of the Eclipse moniker, though. In his keynote at the EclipseCon 2005 conference in March, Lee Nackman, chief technology officer and vice president of Design, Construction, and Test Tools at IBMs Rational Software division, said Microsoft Corp. was actually the company IBM wanted to 'eclipse' and was the true object of IBMs attention." - https://www.eweek.com/development/eclipse-behind-the-name/ https://www.eweek.com/development/eclipse-behind-the-name/ - https://en.wikipedia.org/wiki/Eclipse_(software)#Name https://en.wikipedia.org/wiki/Eclipse_(software)#Name
mikece 3y ago
By making their own implementation of a Java LSP they could integrate this in any number of editors and IDEs, including JetBrains products: https://blog.jetbrains.com/platform/2023/07/lsp-for-plugin-developers/ https://blog.jetbrains.com/platform/2023/07/lsp-for-plugin-d...
- ianlevesque 3y ago
  I think you'd have to be crazy to use a different Java LSP for JetBrains, but it's a useful feature for other languages to be sure.
arrowleaf 3y ago
Serious question, is Red Hat a risk to the Quarkus project? I haven't started any new applications on anything but Quarkus for a couple of years. I would love to use Helidon, but the features and production stability just aren't there yet.
- exabrial 3y ago
  Any single vendor product that does not conform to a specification is, ergo Quarkus (was). Now, Quarkus _finally_ got pulled into JakartaEE certification kicking and screaming, however, it has a million out-of-spec features that I see as risky and likely to break in the future... Spring Framework is now big fat and ugly for this reason! Quarkus's initial philosophy of "Kubernetes first" really isn't such a good rally cry anymore. They've toned down on that, but it does influence the framework to this day. I think if you program and stick to "just the" Jakarta Spec you are in good hands (which Quarkus now implements, along with other APIs). CDI absolutely rocks and is probably the easiest to write fast code for, but also make it composable so it's very testable. I'm hoping someday the Apache Foundation (maybe the TomEE crew?) comes out with a leaner competitor to Quarkus, basically something thats "just the cdi container" and you can pull in stuff as needed.
- _ea1k 3y ago
  Red Hat owns Quarkus, so they are a risk or a benefit depending upon your perspective.
pjmlp 3y ago
Netbeans you mean. Eclipse has always been mostly about Red-Hat and IBM, which is what Red-Hat alongside Microsoft use for their VS Code extension.
darklycan51 3y ago
"Leave Visual Code crap alone". Except that the vast majority of new and even old developers moving to VSCode prefer it over janky 20+ year old IDEs. I like working on multiple ecosystems and not having to re-learn the wheel for each.
leosanchez 3y ago
> Fedora garbage Care to explain ?
LaSombra 3y ago
What are you talking about? What is the relation between Fedora’s decision and the JBoss acquisition?
znpy 3y ago
I used to love netbeans back in the day for java development

29athrowaway 3y ago

Eclipse must have started as a joke about covering the "Sun".

rzzzt 3y ago
"It turned out Sun wasnt the target of the Eclipse moniker, though. In his keynote at the EclipseCon 2005 conference in March, Lee Nackman, chief technology officer and vice president of Design, Construction, and Test Tools at IBMs Rational Software division, said Microsoft Corp. was actually the company IBM wanted to 'eclipse' and was the true object of IBMs attention." - https://www.eweek.com/development/eclipse-behind-the-name/ https://www.eweek.com/development/eclipse-behind-the-name/ - https://en.wikipedia.org/wiki/Eclipse_(software)#Name https://en.wikipedia.org/wiki/Eclipse_(software)#Name

mikece 3y ago

By making their own implementation of a Java LSP they could integrate this in any number of editors and IDEs, including JetBrains products: https://blog.jetbrains.com/platform/2023/07/lsp-for-plugin-developers/ https://blog.jetbrains.com/platform/2023/07/lsp-for-plugin-d...

ianlevesque 3y ago
I think you'd have to be crazy to use a different Java LSP for JetBrains, but it's a useful feature for other languages to be sure.

arrowleaf 3y ago

Serious question, is Red Hat a risk to the Quarkus project? I haven't started any new applications on anything but Quarkus for a couple of years. I would love to use Helidon, but the features and production stability just aren't there yet.

exabrial 3y ago
Any single vendor product that does not conform to a specification is, ergo Quarkus (was). Now, Quarkus _finally_ got pulled into JakartaEE certification kicking and screaming, however, it has a million out-of-spec features that I see as risky and likely to break in the future... Spring Framework is now big fat and ugly for this reason! Quarkus's initial philosophy of "Kubernetes first" really isn't such a good rally cry anymore. They've toned down on that, but it does influence the framework to this day. I think if you program and stick to "just the" Jakarta Spec you are in good hands (which Quarkus now implements, along with other APIs). CDI absolutely rocks and is probably the easiest to write fast code for, but also make it composable so it's very testable. I'm hoping someday the Apache Foundation (maybe the TomEE crew?) comes out with a leaner competitor to Quarkus, basically something thats "just the cdi container" and you can pull in stuff as needed.
_ea1k 3y ago
Red Hat owns Quarkus, so they are a risk or a benefit depending upon your perspective.

pjmlp 3y ago

Netbeans you mean. Eclipse has always been mostly about Red-Hat and IBM, which is what Red-Hat alongside Microsoft use for their VS Code extension.

darklycan51 3y ago

"Leave Visual Code crap alone". Except that the vast majority of new and even old developers moving to VSCode prefer it over janky 20+ year old IDEs. I like working on multiple ecosystems and not having to re-learn the wheel for each.

leosanchez 3y ago

> Fedora garbage Care to explain ?

LaSombra 3y ago

What are you talking about? What is the relation between Fedora’s decision and the JBoss acquisition?

znpy 3y ago

I used to love netbeans back in the day for java development