Earlier quoted context omitted.
You're right, I remember it now. I used the wrong terminology in that case. Honestly, the end result is the same. I'm sure there were reasons to use multiple workspaces for different pieces of code and the same user of the same program would still want it to look and feel the same rather than getting thrown the defaults back in your face when starting a new workspace...
You can easily import your preferences into your new workspace. I mean, it's not even difficult to find, File>Export and File>Import.
The Fall of Eclipse (2016)
101–110 of 149 posts
Re: The Fall of Eclipse (2016)
#102That does resonate strongly with me. I learned to program when Eclipse was (surely according to the graph) the most popular java IDE. It was at that point a good IDE for Java as well and I was quite happy with it.
But after having used IntelliJ for three years now, I really would not want to go back to Eclipse. I had to use it some months ago when I was helping a student with a project, and it does look quite bad compared to IntelliJ.
Re: The Fall of Eclipse (2016)
#103I still remember when Eclipse jumped the shark. It was always a complex and somewhat bloated IDE, but once you learned how to use it, it was fast and had plenty of useful features, refactoring was a breeze, etc. Then they did that major UI redesign TFA mentions. I remember thinking "I can't believe nobody cares that this is slow, nothing works and the UI is unusable. It used to work!". Then I read the Eclipse forums…
They missed the boat on JS. That was a big issue for me as a full stack dev. When it became clear they were going to drag their feet forever on updates to JSDT and not support the plethora of languages that suddenly seemed to come from nowhere, I had to bite the bullet and go to Intellij.
Eclipse is like a nice house in a neighborhood that needs some serious renovations. Intellij is move in ready with gleaming countertops, fresh floors, new appliances etc. Can you tell I'm house hunting?
Re: The Fall of Eclipse (2016)
#104Still have no idea how to use Eclipse after 10 years. Vim, Emacs, VS Studio, VS Code, a few proprietary ones - very easy to figure out. Eclipse seems to be a magical combination of hard to use, slow, and hated. Was there a golden period? Was it great for awhile, and now is past it's prime, like MS Word?
hard to use, slow, and hated A classic example of Conway’s Law in action
Re: The Fall of Eclipse (2016)
#105I actually question whether the real story is the fall of Eclipse or the rise of Intellij. My impression (as someone who used both) is that Intellij IDEA was significantly better than Eclipse (to the extent that I went out of my way to be the sole developer who used it on a team of Eclipse users) but that it was not widely used. Then they decided to release the community edition which enabled people to try it without…
Re: The Fall of Eclipse (2016)
#106Back then, Eclipse was this big, bloated and slow IDE. IntelliJ was slim, fast and much more intuitive and powerful in terms of refactoring, etc. Today, IntelliJ is big, bloated and turning slow. Which IDE will be the next big thing?
Stop buying cheap old macs or switch to PCs. Tired of the same crap arguments. If your company doesn't want to spring for 3k laptops, get a 1k win laptop with the same specs.
Re: The Fall of Eclipse (2016)
#107I stopped using eclipse because scrolling became super janky on mac after an update. Seven years on, the bug is still open: https://bugs.eclipse.org/bugs/show_bug.cgi?id=366471
Re: The Fall of Eclipse (2016)
#108"That era is now over." Not sure that is true (pedantically), as my son is building Minecraft modules in CodaKid, and they have him using Eclipse, I'm sure b/c it's free: https://codakid.com/ . (They have great classes, FWIW/IMO, not affiliated.) I also don't get all of the "Eclipse is super-hard to use" comments in the thread. Look, I love LPS and think that now that we have the luxury of local cross-process wire ca…
Re: The Fall of Eclipse (2016)
#109I still remember when Eclipse jumped the shark. It was always a complex and somewhat bloated IDE, but once you learned how to use it, it was fast and had plenty of useful features, refactoring was a breeze, etc. Then they did that major UI redesign TFA mentions. I remember thinking "I can't believe nobody cares that this is slow, nothing works and the UI is unusable. It used to work!". Then I read the Eclipse forums…
Everyone blames the Eclipse foundation, but really they set the bar high. The only IDE to rise above it has been Intellij imo. They missed the boat on JS. That was a big issue for me as a full stack dev. When it became clear they were going to drag their feet forever on updates to JSDT and not support the plethora of languages that suddenly seemed to come from nowhere, I had to bite the bullet and go to Intellij. Ecl…
Re: The Fall of Eclipse (2016)
#110I use both. Jetbrains is better, but it costs money. Its worth it to save the time figuring out eclipse. I use eclipse because I'm maintaining some tomcat code, and the code live in an eclipse project world. Eclipse works and once set up it does it job well. The truth is its just too complex. I still can't get it to work with Git. Eclipse is free (since I use it professionally I donated.) one example in Jetbrains I c…