Eclipse has always been a needed and valuable IDE for Java development. If I wanted to spin up a Java app with Maven, I could do okay with Eclipse. Refactorin

Eclipse has always been a needed and valuable IDE for Java development. If I wanted to spin up a Java app with Maven, I could do okay with Eclipse. Refactoring tools work fine, debugging is great. Support for languages OTHER than Java, however, vary wildly in terms of value. One language support that seems to have crossed over into complete obsolescence is JavaScript. I hate to break it to you Eclipse Foundation, but developing JavaScript on a WebIDE is completely out of the question for many of us, so your fancy Orion system is a non-starter. It's mean of me to say, but I'm rooting for Orion to fail so you can move those developers back to enhancing the desktop IDE's JavaScript support. Eclipse JSDT is my only option, and it seems broken and unmaintained. Around the 2008 timeframe, I was really impressed with JSDT's ability to build out a type library as it parsed my prototypes, it really understood the type system when I added JSDocs. It all works ok for rink-a-dink projects that are targeting the browser and coexisting with HTML. But, for any modern development like server-side Node.JS or CommonJS browserify/webpack projects in the browser, ES6 or anything modern, Eclipse JSDT is really up a creek without a paddle. I can't use you, and that makes me so sad to say because I WAS a staunch Eclipse user who turned his nose up at JetBrains! To make matters worse, Eclipse has gotten slower and buggy since the last major upgrade (Luna?) and WebStorm is cheap and great and amazing at parsing JSDoc's to the point it practically turns JavaScript into a statically typed language, and it groks CommonJS and my node_modules folder (with the help of a little plugin I downloaded.) I admit I haven't tried running Eclipse in a year, so perhaps the bugginess has been addressed.