3 ms·
Having only played a little with both (Kotlin and Nim), I enjoy Kotlin syntax but overall it feels as heavy as Java (need to setup an IDE for even getting start
by felipeccastro 7y ago
Having only played a little with both (Kotlin and Nim), I enjoy Kotlin syntax but overall it feels as heavy as Java (need to setup an IDE for even getting started, choose and understand some package manager, slow compile times, etc.)
Nim feels as lightweight as Go, but with great syntax.
The main thing holding me back now is the lack of libraries, but it's definitely on my radar.
- vips7L 7y agoIsn't an ide just a choice? You don't have to use intellij. There are vscode plugins. Don't you also need to understand the go package manager or Nim's? I don't see how this is different than learning Gradle.
- kitotik 7y agoBetter than having to choose an IDE, is to not have to choose an IDE. It’s pretty liberating to put some text in a single file, pass that file to a compiler, and have a single executable binary. A devolved workflow I know.
- 7thaccount 7y agoDevolved, but still superior in some ways.
- kungtotte 7y ago> nimble install docopt > echo "import docopt" > test.nim > nim c test.nim Nim's package management isn't exactly rocket surgery. Even if you use nimble as a build tool it's still extremely straight forward: > nimble init > echo 'require "docopt"' >> projectname.nimble > echo "import docopt" > src/projectname.nim > nimble build Notice the lack of explicitly installing docopt, nimble build takes care of unmet dependencies. That's it! Now you know everything there is to know about Nim package management. (Not quite, but close enough)