Back 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?
People, Intellij's performance is fine, just like Eclipses was. 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.
The Fall of Eclipse (2016)
111–120 of 149 posts
Re: The Fall of Eclipse (2016)
#112Back 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?
There are multiple ways to vastly increase Intellij performance. They also have 'Auto-share Settings' feature so you can keep a whole team in-sync with them through a repo. tweaks like: - they added their own custom property that speaks for itself: 'editor.zero.latency.typing=true' - it runs on a JVM, so update the JVM settings. (Like most apps, they ship with defaults that assume you're running your IDE on something…
Re: The Fall of Eclipse (2016)
#113OTOH, Eclipse, while different releases have been better or worse than others, and despite a rough period starting with the whole "Eclipse 4" thing, the Oxygen version has been very nice. I started with a RC of Oxygen and it's worked so well I never even bothered upgrading to the actual release version.
The only thing that really annoys me about Eclipse is that they killed off the TPTP sub-project, and I really liked their profiler back in the day.
Re: The Fall of Eclipse (2016)
#114I 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…
" Its worth it to save the time figuring out eclipse." We talking about people making 100k+ but are worried about spending a few hundred for a better tool. It just shows that the same amount of money is valued different in a different context. Spending 500 more for a better laptop is being questioned and two days later you got to dinner with some VPs and they blow more than $200 per person for wine and food.
ad rem - I could never make myself using Eclipse - it always felt like getting in the way instead of helping.
Re: The Fall of Eclipse (2016)
#115I 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…
On the other hand I've never been a big fan either. Developing plugins wasn't fun - getting various plugins to work together wasn't fun either. It was an OK IDE for Java and some other languages...
Re: The Fall of Eclipse (2016)
#116I started using IDEA because I wanted dark theme and Eclipse didn't have it. Probably even now you can't get nice looking dark theme in Eclipse, not sure, correct if I'm wrong.
Re: The Fall of Eclipse (2016)
#117That said, there were few things that I liked in Eclipse. Errors were easier to work with. Also I could run uncompileable Java code and I liked it (Eclipse skipped bad code and throwed exception there).
Re: The Fall of Eclipse (2016)
#118Earlier 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.
Honestly it reminds me of GIMP taking years to finally implement an MDI interface. If only eclipse let me keep the same bindings, UI, etc across different workspaces I probably wouldn't have switched.
Re: The Fall of Eclipse (2016)
#119Netbeans was better/easier to use than Eclipse for a long time in my opinion (100% accept that isn't worth a whole lot). I vaguely remember that in about 2010/2011 trying to use the maven and git plugins for eclipse together and hitting a lot of errors. Netbeans wasn't perfect but it worked AND used the system installations of git/mvn. Also, Ive never understood why Eclipse insists (at least last time I used it) on i…
Re: The Fall of Eclipse (2016)
#120Recently i changed to Netbeans having been using Eclipse at work for years and was pleasantly surprised. Much faster than eclipse, no constant lags and freezes. At home i use IntelliJ. Never looking back to Eclipse.