Hi folks, in my opinion Nim is doing a lot of unnecessary stuffs. Like Python, TS/Javascript, etc. I might be wrong, but i really feel that Nim should just focus on one thing, to kill C (Rust, C++, etc). if Nim just focus on this, it will literally make development cycle much faster while focusing on performance & readibily aspect of the language. People would literally adopt it. Background - i have 9yrs+ of development experience in Python. i have never work with Nim lang on production.
My requirement? building drones for quick medical help supplies. C is so much to do... Nim is fun but i need hardware performance better than C without visual noise of C. i don't know if it's even possible 😅 but just a thought.
Hi folks, in my opinion Nim is doing a lot of unnecessary stuffs. Like Python, TS/Javascript, etc. I might be wrong, but i really feel that Nim should just focus on one thing, ...
Well you are wrong and compiling to JavaScript is just something that every language can do too anyway.
Nim doesn't do too much, often it is doing the bare minimum and people complain about it: (Maybe rightly so, maybe not.)
With great power comes great responsibility - Uncle Ben
You can build anything you want within a single unified codebase under a single language and run it anywhere- from a laptop to a playstation3 to a microcontroller.
Nim is arguably one of if not the most ergonomic, portable, performant, expressive, and extensive programming languages that exist.
Learn how to wrap C/C++ libraries and leverage AI to help port some Python libraries you need into Nim, and you'll never touch that language or any other again.
I came from a Python background too. I feel dirty when I think about it.
But my name is Niminem so I might be a little biased here.
Nim isn't small, but it's not that big either. But in my mind, either of these are beside the point. What matters to me is that Nim is of excellent quality. You get massively more value per unit of learning than other languages, and it compounds.
For example, I really went deep researching how thread communication works and what the efficiency tradeoffs are of different mechanisms. I was prepared to use some kind of really ugly solution as long as I got speed. What did I discover? That Nim standard library "locks" use fastest and best solution you can get on each operating system. But the lock interface is almost stupidly simple. So if I hadn't thought about it, I still would have got the fastest.
That casual excellence is not something I've experienced with any other language.
One thing I did notice that the more powerful features can be a distraction. It's still nice that they are there, in my mind, but you have to adjust- if you just want to get things done- use a few objects and procedures and basic types and writing the code will be as fast as running it.