November 11, 2015

My favorite IDE

This is an old post, nowadays I use a web IDE.

We all start with something like notepad++ until we start for something more useful.

Various editors exist, Xcode with block scope highlighting (which is CPU intensive) to something like vim, which is ideal for quick editing of config files over SSH.

My first real IDE

My first language was Java, which was taught in BlueJ at my university (if your uni still does this, burn the books! programming is never learned from books, since half of the content is deprecated from the moment they are printed).

My first IDE were Netbeans and Eclipse, since I was programming Java. I switched to the one who supported the best dark theme (that was before I found system wide color inversion, which is available on Windows, OSx and Linux).

Visual Studio

My uni was really into proprietary software and Windows, which made me use Visual Studio.

My experience with and Visual Studio is horrible. I used Ubuntu, and needed to run them in VM, since there was no proper alternative to run VS.

Javascript IDE

When doing js for a class at uni, the recommended Aptana Studio as a Eclipse plugin. This worked, but was just and overkill, why use such a heavy IDE?

My main focus the last year has been Bash, LaTeX and js. For which I searched for a good IDE and tried various. Some people recommended Sublime, but it just wasn’t my thing. I used LightTable for some time, but it had too many flaws which made me search again.


Currently I use Atom, which I really love! Of course there are some things that I would like to see updated. But with the following packages:

  • markdown-preview-plus
  • language-docker
  • language-latex
  • language-lua
  • language-nginx
  • linter
  • linter-js-standard
  • red-wavy-underline
  • standard-formatter
  • tabs-to-spaces

it is an amazing IDE.

I also disabled some default packages;

  • welcome
  • whitespace (only important in this list)
  • language-csharp
  • language-perl
  • language-clojure
  • language-ruby-on-rails

If you want spell-check to work, you need to do some modifications. See the type of block/scope you want to be checked, place the blinking cursor on it, and press CTRL + SHIFT + ALT + P. Now copy the scope and paste it in the grammar array in config.cson. Which is accessible through: Menu bar (visible by pressing ALT) > Edit > Open Your Config, or by

$ f=$USER/.atom/config.cson && vim $f || xdg-open $f

and the most easy is to just paste it in: Menu bar > Preferences > Packages > type ‘spell-check’, ENTER > Settings (of that package) > Grammars.

My current entry in this box:


Blog by