| Re: [ide-dev] Why we dropped Eclipse in favour of IntelliJ | Java Code Geeks |
|
There are some good arguments I fully agree with. Things such as having most of JDT warnings disabled by default is a only way to hide the value of Eclipse. Most products show everything they can do by default, and users are free to disable the useless parts. On this topic, some Eclipse projects chose the other way round, which seems to lower the value of the IDE. I'm aware of the argument "people don't like to see hundreds of warnings", but it's the role of an IDE to show them and teach to any developer a better way to write code. Opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=417630 I don't know much of JSDT and VJET, but I heard mainly bad things on the topic of JS development with Eclipse. I guess in current world where everything is _javascript_ for tablet and smartphone, a bad _javascript_ tooling can be a cause of total failure of an IDE. Let's hope some contributors will put efforts on this. It would be interesting to know how much contributors plan to invest in this (to be honest I don't even know for Red Hat...) and see whether some improvement will happen. And it could be interesting to highlight _javascript_ as a "hot topic" and a corner-stone of the future of IDEs and make call for participations, via newsletter, twitter or other. Could it be something the Foundation could do? More generally, the most web-centric package is Eclipse JEE. It could make sense to rename it "Eclipse for Web and Mobile Development" to advertise the support of more trendy/modern web technologies such as JS and get further than just JEE. Opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=417632 The "Several minor things" are actually pragmatic feature requests that should be entered in the tracker. I let other people do it ;) |