I abandoned Nim mainly because to make Nim usable in a lot of cases means to glue together bunch of libraries maintained by select few autistic developers. I mean it in the best way those of you who make those are extremely skilled probably in the 1 percentile of developers.
Thus Nim is an expert level programming language not suitable for an average folk.
We need Nimdummy a set of libraries and strict guidelines how to achieve the most common denominator for what people want. Performant parallel http servers.
Thus Nim is an expert level programming language not suitable for an average folk.
Never made a penny from programming. I do it just for fun and my code is utterly ugly and it works for me.
If you want to do high end stuff you'll encounter high end libraries.
So, I don't get (the purpose of) your post at all.
glue together bunch of libraries
Is that different in other langs?
for what people want.
What do people want? You might elaborate the gap you experience with additional examples...
Perhaps a Nim equivalent to blessed.rs, like awesome-nim would help get you started?
There are a few libraries that are default recommendations like Mummy, but a large part of Nim's user-base seems to be hobbyists interested in software "closer to the metal", so reinventing the wheel is part of the fun for them. Where it is used commercially on teams it produces idiolects like Status's std-lib libraries.
It would be nice if there was more cooperation and less reduplicated effort, package managers for instance. Fostering cooperation like this is basically a job though and you're "managing" volunteers, so frustrating. I'd love to see it happen though and would be happy to contribute to something in the web space.
to make Nim usable in a lot of cases means to glue together bunch of libraries maintained by select few autistic developers.
Do you want me to take you seriously? I'm not saying you did not have some issues with Nim, but you have to put a little bit more effort on your thread starter if you want a normal conversation with people. Anyway, I'm going to copy-paste my post from the Dlang forums here, because I hate the popularity meme:
If you want to see change, then be the change you want to see! Write code, write blogs, share with people what you like about the cool thing you like, ... The constant negativity loop of "why thing unpopular" isn't solving any problems.
Shout out to the autistic developers who maintain the libraries I depend on lololol
I recently tried this DeepWiki LLM thingy for generating documentation:
Performant parallel http servers: https://deepwiki.com/olliNiinivaara/GuildenStern
Peformant parallel SQL database: https://deepwiki.com/olliNiinivaara/SQLiteral
But I have mixed feelings about the results, and so far links to them are not published at GitHub.
Even if we accepted that these documents are useful for library users, I still understand the OP's concern that there are no beginner tutorials about how to glue these kinds of libraries together. Low-level libraries themselves should be general-purpose and not steer people to select one specific architecture. What we might need is a higher-level opinionated framework that makes it easy for the "average developer" to start churning out apps. Maybe that should be my next Nim side project...