By far my favourite feature of this release, dark mode in docs: https://nim-lang.org/docs/lib.html
Nim 1.2
91–100 of 130 posts
Re: Nim 1.2
#92By far my favourite feature of this release, dark mode in docs: https://nim-lang.org/docs/lib.html
I feel like dark mode is a sign that people care. I think it's a user feature that is easy to do, but not done often. Mostly done by people who care. It brings so much polish to the experience.
Re: Nim 1.2
#93Earlier quoted context omitted.
I feel like dark mode is a sign that people care. I think it's a user feature that is easy to do, but not done often. Mostly done by people who care. It brings so much polish to the experience.
What if I care specficially not to add a dark mode?
Re: Nim 1.2
#94Re: Nim 1.2
#95Does Nim have an ORM or querybuilder as good as SQLAlchemy yet?
Re: Nim 1.2
#96Earlier quoted context omitted.
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.
Isn'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.
> 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)
Re: Nim 1.2
#97Re: Nim 1.2
#98hope they nim developers, port a lot of python data science tools e.g pandas, numpy etc so they can increase adoption in the language. Julia is supposed to fill that space, but feel strongly nim is better positioned
Re: Nim 1.2
#99One bit which I still hate is simply how imports work in Nim. My project pretty much has a header like file containing function and variable signatures which can be called from other files.
For someone used to modern languages, it just feels so archaic.
But overall it is still a fantastic language and I am excited to try the ARC gc
Re: Nim 1.2
#100I really with more people used NIM for web development. It really seems like the best of all worlds (e.g. perf, developer ergonomics, productivity, etc).
What advantage does it bring that Kotlin hasn't?
1. no JVM (Kotlin Native isn’t considered a stable thing, or is it?),
2. subjectively nicer language,
3. An optional non-GC runtime upcoming (already in there as beta), which is interesting for low-memory applications... which in the time of the Cloud is potentially any application. The more (AWS) lambda time you can get for free, the better, right?
4. Writing command line tools. Practically nobody is writing them on Kotlin. Everybody’s writing them on Rust, though, for some reason...
Disclaimer, full disclosure: I’ve only read about Kotlin, of course, not written a single line. It seems like an excellent language, and if I had to do JVM work, I’d have it as a top3 candidate for sure.