Emacs vs. WebStorm for Node.js Development • Hacker News Board

Re: Emacs vs. WebStorm for Node.js Development

#101

Post by tuananh » Wed, Jan 27, 2016, 1:44 AM UTC

vfc1 wrote: post #17

The new Webstorm version coming up is several times faster, its amazing. On a Mac its so fast its literally like using Sublime. This is due among other things due to their upgrade to Java 8. This is the link to the early access program https://confluence.jetbrains.com/display/WI/WebStorm+EAP

really? How long does it take on a cold startup?

Re: Emacs vs. WebStorm for Node.js Development

#102

Post by girzel » Wed, Jan 27, 2016, 2:12 AM UTC

ibabanov wrote: post #34

"Symbol and definition lookup is another great feature of WebStorm. While Emacs can find symbols and definitions in a single file via Tern, ..." Actually, tern has tern-find-definition which works not only in a single file. You can jump in to other modules in your project or to node_modules. And there is tern-pop-find-definition to return back. For methods of native js objects tern even opens browser with related MDN…

It's also worth noting that there's a lot of work going into Emacs right now to give it better IDE-like features -- finding definitions reliably, refactoring, all that stuff. They're working on a more generalized framework for supporting this stuff, and I'd expect Emacs to get significantly more competitive (with traditional IDEs) within the next year or two.

Re: Emacs vs. WebStorm for Node.js Development

#103

Post by feider » Wed, Jan 27, 2016, 8:24 AM UTC

thecatspaw wrote: post #51

feider wrote: post #46

Earlier quoted context omitted.

Using Atom is just pure pain, though the pain goes away fast once you stop using it.

What pain are you experiencing? Im using it often and dont have any problems.

Well, it is just slow: bigger the code base / longer it runs, the more clearer this becomes. I used Atom for ~6 months, until I had enough and switched to sublimetext about 4 months ago.

Re: Emacs vs. WebStorm for Node.js Development

#104

Post by wyqydsyq » Thu, Jan 28, 2016, 4:20 AM UTC

I find it strange that you tried Webstorm and not Atom - considering Atom and all of it's packages are written in JavaScript (or transpiled to it), you can give it any functionality using the language you're already using - JS. I find Atom to be great for working with Node.js, and there's already an existing package for pretty much any functionality you could need, such as a Node.js debugger: https://atom.io/packages/node-debugger

Re: Emacs vs. WebStorm for Node.js Development

#105

Post by barrkel » Fri, Jan 29, 2016, 6:51 PM UTC

davexunit wrote: post #93

barrkel wrote: post #91

Earlier quoted context omitted.

For me, coding in a debugger is a superior experience to coding with static type info - because I have data too, not just types. Ie completion isn't the big win - seeing live results of processing data is.

I can't tell if you are agreeing with me or if we are miscommunicating. Seeing live results of processing data is exactly the type of thing I do with Geiser in Emacs. No static analysis.

If the information includes local variables and parameters, then we are agreeing; if not, then we are disagreeing.