"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…
The Fall of Eclipse (2016)
41–50 of 149 posts
Re: The Fall of Eclipse (2016)
#42Re: The Fall of Eclipse (2016)
#43Article Header needs (2016) next to it.
Re: The Fall of Eclipse (2016)
#44Still 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?
Eclipse is a direct descendant of IBM Visual Age for Java, which branched from VA for Smalltalk. VA was an excellent tool for Smalltalk insofar as it allowed you to work with a big soup of classes, abstracting away source files to the point of near invisibility. Fitting Java required a bit of shoehorning, and I must admit VAJava was an acquired taste for me. I had to sink or swim as VAJ was the official tool of my jo…
Re: The Fall of Eclipse (2016)
#45I 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…
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)
#46I 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…
I do think that the price as a cons being like 15$/month is kind of a negligible cost if you're using it every day for multiple hours.
Re: The Fall of Eclipse (2016)
#47Being 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…
Re: The Fall of Eclipse (2016)
#48I 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…
I do think that the price as a cons being like 15$/month is kind of a negligible cost if you're using it every day for multiple hours.
Re: The Fall of Eclipse (2016)
#49Earlier quoted context omitted.
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…
Was that a feature of the IDE or the compiler? Or does the IDE have its own integrated compiler that can't be used standalone?