> Compile, Build and Run from within the editor
I solve that by using the integrated terminal in VSCode. And simply do the
standard: nim c xxx.nim
Or you can use the setting from the nim plugin:
"nim.buildOnSave": true,
"nim.buildCommand": "c",
"nim.lintOnSave": true,
"nim.project": ["test.nim", "project2.nim"],
Put those in your user settings. It auto builds if you save ( and displays
errors when fails ).
There is also the Aporia nim editor but frankly it just feels not finished.
While it works, it can never keep up with editors like VSCode...
**@idobai:**
Atom is just less newbie friendly. I tried it last week ago and it was
disappointing at how many hurdled i needed to run over, to get it "ready".
Figuring out how to get the plugins, getting some of the basics going etc...
VSCode is technically behind Atom but it felt so much more easy going. And it
seems from the blogs that they have a faster development.
Atom was slower then VSCode. A large part in my opinion is the less user
friendliness. This slows people down and makes the editor feel ( unjustified )
slower. VSCode feels more integrated / professional. Atom feels like a
collection of plugins.
> With such "progress" they'll never beat neither sublime nor vim.
That is a hard statement. Vim can never be beaten in speed simply because of
its nature as a "simple" terminal editor. But at the same time its a complex
piece, what required people a long time to learn it. Let alone trying to get
the plugins going for Vim. Its simply not user friendly. And that was never its
goal. It simply grew to become this big multi able monster over time. And its
not that efficient also because else there was no reason for Neovim.
Wrote over 3 years Perl code with Vim, with plugins and when switching to full
ide editor like PHPStorm, never looked back. Even after 3 years i was still
looking up VIM commands because you simply forget the one's you do not use
every day. VIM for me is at best for small tasks but never any descent jobs. It
just feels less productive. And its file locking is horrible in multi team
development.
VMCode while less complete then for instance Intelli/PHPStorm, but it just
feels nice & productive. And that is what matters. Its frankly the first editor
that made me WANT to code in Nim. All the rest ended up frustrating me because
of lacking features, time wasting configuring things, time wasting with
plugins, bugs or other problems.
I tried almost every editor on the list
[https://github.com/nim-lang/Nim/wiki/editor-support](https://github.com/nim-lang/Nim/wiki/editor-support),
except VMCode because it was not on it _lol_. OderWat his mention peaked my
interest and here i am :)
The fact that i needed to download, compile & configure nimsuggest/nim plugins
for VIM just made me instantly say No! Just tired of doing things like that.
Maybe i am lazy in my old age but i just prefer things to work out of the box
with no hassle installing & configuring half a dozen of thing _lol_
VMCode does just that. Install Nim. Install VMCode, select nim plugin. Good to
go ( literally because its installed as a portable version on my USB/SSD ).
Atom was slower on that USB/SSD in loading etc.
