The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Tim Holloway wrote:Eclipse has plug-ins for almost everything - including Java.
Joke.
Eclipse is really just an OSGi framework and the "Java IDE" that most of us think of as "Eclipse" is actually just a spin that has Java plugins pre-installed. Or JEE, if that's the spin you choose. There are plugins for C/C++ (including a full spin), JavaScript, Python, Unix Shell Scripts and even COBOL and LISP. Often the hard choice is determining which one of several similar plugins to install and use. I think that I'm using "Eclipse Java Web Development Tools", myself. While JavaScript is certainly not Java, there's enough syntactical overlap that it's for one set of plugins to support both.
While the IntelliJ world has lots of plugins, last time I checked, Eclipse had more. IntelliJ is like traditional Apple. It does the important things very well, but doesn't try to do everything. Eclipse is more like Unix, in that it's not as well-focused on specific common tasks, but it makes up for it by being more open-ended. Which one is preferable depends on your needs. I like to run debugging sessions that dig intol multiple apps and servers in a single session, and IntelliJ couldn't handle that last time I looked, but it's second-nature for Eclipse. Conversely, I've never seen a good WYSIWYG Swing editor for Eclipse, but it's built into IntelliJ. And JetBrains has done considerable pioneering work in their own right. Consider Kotlin, for example. There's a Kotlin plugin for Eclipse. Provided by JetBrains.
Bear Bibeault wrote:There may be JS plugins for those IDEs, but I've never used either of them (even when I am writing Java).
The most common IDEs used for JS development today seem to be WebStorm or IntelliJ from JetBrains, or VS Code from MS. All have top-notch JS integration.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Tim Holloway wrote:.
In fact, you can turn a Maven project into an Eclipse (+Maven) project by rubnning "mvc eclipse:eclipse" as a goal. And guess what? You can do "intellij:intellij" as well. I don't know about NetBeans.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.