Code editor of choice?


#204

I don’t think there are probably that many people running a 50" (1.27m) display. For me the resolution would probably be too low if I was sat close to a screen of that size. A quad HD screen of that size might be different but it would probably still be too tall for me on my desk.


#205

Which plugins do you use to get intellisense for your custom code/classes? I tried a few, but never seem to go without any problems. (mostly it means it should autocomplete something, but it doesn’t). I am currently trying something called TernJS.


#206

WebStorm, by far the greatest JavaScript IDE. it’s a bit bloated and eats at memory, but it has so many insanely powerful and useful features


#207

If anyone is also a .net developer and has a ReSharper license, then you should look into the JetBrains ultimate upgrade at the moment - it’s crazy cheap if you already have a ReSharper license and it gets you almost everything JetBrains do, including Webstorm and the new database manager DataGrip (which unfortunately doesn’t do Mongo yet to save you checking, but does do SQL Server, Postgres etc). Plus you get two years for the price of one at the moment. I know other options are free, this is just a heads up for those who are already paying JetBrains for other stuff.


#208

please describe which modules/plugins you use with your ST, vim, emacs …


#209

I tried to convert from Sublime 3 to webstorm, but I just felt crippled without word selection -> multiple select word -> cursors everywhere -> edit all the things. It just doesn’t work nearly as well in webstorm as I have become used to. Not to mention the go-to-anything menus with fuzzy search that reads my mind.


#210

I used vim (MacVim) since college days. Managing vim plugins seems a pain to me so seldom bother unless strictly needed. Now works with Atom + vim-mode + ex-mode (not full vim features, but far more than enough for me). Awesome so far.


#211

I tried Atom yesterday and found that debugging is in the browser using node-inspector, just the same as using meteor debug. Since I also can’t get clear text with small fonts as described before, there’s no point for me to use Atom.

I am now trying WebStorm. Small fonts look blurry like in Atom. I made a screen capture that clearly shows the difference in clarity of the same font (Lucida Console) in WebStorm and Visual Studio 2015:

Note that this forum app doesn’t show the image at 100% zoom, so you’d need to first right click on the thumbnail image above and either open in a new browser tab or download, then view at 100% zoom.

There could be something in Visual Studio that makes small fonts appear clearly readable. Maybe it has something to do with Microsoft ClearType.

Maybe I’ll just use WebStorm as a debugger, until JetBrains works out how to render small fonts clearly. Visual Studio still remains the gold standard of IDEs.


#212

Wish Neteans had support for Meteor. Webstorm is good but not free.


#213

I use spacemacs (emacs + vim): http://spacemacs.org/doc/DOCUMENTATION.html


#214

my 2 cents.

Sublime Text 3: super smooth but not enough Meteor.
Atom: Super slow, some good Meteor plugins. Too many plugins make Atom unstable.
WebStorm: Bloated and clunky multi-cursor shortcuts, but pretty satisfied in the end. I’m gonna stick with this for a while. (links: JSX, multi-cursor, Meteor) Only problem is JSX component autocompletion doesn’t seem to work.

Really I think there so much more a Meteor IDE should do. Like knowing what server methods are available.

edit: oh my god method autocomplete actually works. Beat that atom/sublime.


Webstorm JSX integration
#215

Recently moved from ST3 to Atom, Atom’s packages tend to fit my purpose a lot better than ST’s equivalents. Webstorm is cool, though I don’t really need all the features it provides. Atom gives me easily sync’d dev environments, console support, ESLint, git integration and about 20 other helpful packages.

I’ve never really had issues with its speed, sometimes it takes a second for the syntax highlighting to popup, but the overall advantages from ST for me far outweigh waiting a second.


#216

Since originally posting this I’ve completely moved to only using Atom and all the Meteor plugins for Atom.
Love it.

I’ve tried Web Storm but have never really gotten into a groove working with it.


#217

The easiest way I found to work with multiple Meteor projects is using cloud based dev env: c9.io

For most experiments and general dev work the free plan is enough.


#218

Hi logician and Max,

I would be curious to know what is your setup to get WebStorm to stop at breakpoints in CoffeeScript code, something I have been struggling in vain for over two weeks now on the tiny Meteor leaderboard example. As a result, I discovered that there are today no less than 7 unfixed bugs related to this issue in WebStorm’s issue board:

  • WEB-23837
  • WEB-19573
  • WEB-19578
  • WEB-12672
  • WEB-9837
  • WEB-19762
  • WEB-13927
    some already two year old :scream:

It seems clear that those bugs surface back periodically, perhaps with each new version of Meteor, and are not voted enough for JetBrains to make a genuine effort to fix them.

So in case you have found a work around on your own, thanks in advance for sharing the trick. I have found this intriguing post on Stack Overflow, but I don’t understand it well enough to make it work.

Also, according to WebStorm’s support, for WebStorm to stop at breakpoints in client code ones needs to select the “with JavaScript debugger” and “after launch” checkbox on the browser/Live Edit tab of the run/debug configuration window. But when you do this, you have two debugging processes, one call “Run Meteor” and another called “Run Meteor JavaScript” and I don’t understand how to use both at the same time.

In the meantime, I am trying as a plan B to find or write a launch.json file for VSCode that could:

  • work with Meteor generated CoffeeScript source maps
  • allow attaching VSCode’s builtin node debugger to stop at breakpoints in the server side code
  • allow attaching VSCode’s chrome debugger extension to stop at breakpoints in the client side code
    but I only have found until now examples without source maps and for EITHER the node debugger alone XOR the chrome debugger alone, but not both.

#219

Vim with a bunch of stuff in my .vimrc file


#220

I’ve tried Atom, ST3, and WebStorm, nothing was able to beat WebStorm for me. It is rather resource heavy though.


#221

they look equally shitty when that small to me!


#222

can’t help; we dislike coffeeScript


#223

does the gold standard of IDEs have multiple cursors like WebStorm?