But they truly killed Eclipse. Eclipse probably never had to go beyond being what it was at the beginning, a wonderful IDE.
The Fall of Eclipse (2016)
91–100 of 149 posts
Re: The Fall of Eclipse (2016)
#92I 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.
Re: The Fall of Eclipse (2016)
#93> One only has to look at the TypeScript support in WebStorm as an example of how bad things can get. I'm a bit surprised by this statement. I've been using TypeScript in WebStorm/PyCharm for quite a while and have been really happy with it. Are there some big flaws I'm not noticing or specific valuable features that they're not adding? Compared with JS and Python, TypeScript coding feels much nicer (as you'd expect…
Even compared to Java IDEs of a decade and a half ago, the refactoring, and other smart-assist facilities in Typescript editors/IDEs is rather weak.
Of course, Typescript isn't generally, totally statically typed, so that brings a whole set of challenges. And Typescript's type system is very complex these days.
But I agree Webstorm (and really the whole suite of Intellij IDEs) does a great job with Typescript. I think only recently in the past month or so, VS Code has gotten unused imports checking.
Re: The Fall of Eclipse (2016)
#94Intellij has always been way better than Eclipse, but for a long time you had to pay a small amount for it. People looking at dollars rather than bottom line foolishly chose Eclipse.
Re: The Fall of Eclipse (2016)
#95Being used to Visual Studio, every time I needed to use Eclipse I kept wondering how Java developers could tolerate such an environment. Now I know ofc some of it is due to less familiarity and exposure, but it realy felt like stepping back 15 years in time each time I launched it.
Re: The Fall of Eclipse (2016)
#96Being used to Visual Studio, every time I needed to use Eclipse I kept wondering how Java developers could tolerate such an environment. Now I know ofc some of it is due to less familiarity and exposure, but it realy felt like stepping back 15 years in time each time I launched it.
I'm not sure in what way your Eclipse experience was so atavistic, but I'd like to point out that at least for several years I was aware of, Eclipse had a significant competitive advantage: Incremental compilation. You could make a small change, do a Ctrl-S, and Eclipse would compile the change nearly instantly, where all competing products (that I was aware of, correct me if you know better) needed to fire up a Java…
Java Hotspot has always been a huge productivity booster.
Re: The Fall of Eclipse (2016)
#97that's due to decreasing demand in java.
A large number of Android developers would disagree with that statement.
And of course, you're not really targetting the JVM when you're programming Android, but Dalvik or whatever runtime powers Android these days.
Re: The Fall of Eclipse (2016)
#98There might be a real discussion here, though. E.g. as far as I know anybody who ever tried IntelliJ loved it so much that he never wanted to switch back to Eclipse. In the circle around me, 100% of people. Other people may see different outcomes. But still both Eclipse and IntelliJ where both kind of considered leaders in the Java IDE market for a long time. So it might be really interesting to discuss the strenghts and weaknesses of both.
Also a good discussion could be had how the path to Eclipse 4 developed and how things might've been done differently. That would require analysing other IDEs like the Microsoft's as well.
So, you know. Quite a wasted opportunity, right here. If someone reads this and felt like upvoting, could you put into a few sentences why?
Re: The Fall of Eclipse (2016)
#99EDIT: Although I would like to add that I liked Intellij VIM integration more. I have been using Vrapper for Eclipse and it is decent but not many people are contributing to the project for a while which raises doubts on it's sustainability: http://vrapper.sourceforge.net/home/
Re: The Fall of Eclipse (2016)
#100I'm okay with Eclipse. Here's why. As a consultant working at clients typically there's enough lockdown where I end up having to use Eclipse. Because of that I haven't had much opportunity to actually use Netbeans or IntelliJ at a client. So like someone mentioned below I just sucked it up and dealt with it. It's not perfect and I definitely get some cryptic errors but I'm actually pretty happy with it now. You shoul…