There are a lot of good points in @moerm's post. I too feel like there is too 
much effort spent on compiler gizmos, pragmas to avoid a variable copy in some 
bizarre instance, rather than making what already exists "best in class", or at 
least have that as an ideal.

Recently [Araq posted](https://forum.nim-lang.org/t/6733):

> These should be provided as external libraries (and iirc we have some Nimble 
> packages offering these) or added to "nim fusion". Our focus is on language 
> development, not on libraries.

I understand that the core Nim team is focused on the compiler; it's complex 
and newcomers are not going to be able to jump in and start helping with that. 
But at the same time, when help is offered for improving the libraries, it 
often turns into a humongous discussion, even for obviously broken code.

I think the core Nim team should focus only on the compiler. But they need 
another "czar" for a better word, to reign over the standard library, and one 
with good diplomatic skills so that newcomers offering help are not immediately 
put off with brusk negative comments that, in my experience, are made before 
even taking time to fully understand the issues.

Nim's core team will remain small if new developers feel like the hassle of 
helping to improve Nim is just too much. Instead of feeling good about 
contributing to improve Nim, it can turn into "run the GitHub pull gauntlet". A 
good technical community leader with good diplomatic skills and authority to 
merge PR's, with the core compiler team staying focused on the compiler, would 
go a long way toward improving the standard library, Nimble, Fusion, etc., 
thereby improving the Nim language ecosystem, and also helping build the 
contributor community.

Developers do not want a compiler with a lot of experimental knobs to fiddle 
with. They need a complete language ecosystem, with organized, well-documented, 
in-depth, optimized libraries being a large part of that ecosystem. In my mind, 
this is more important than adding a new kind of garbage collector that is 
twice (or whatever) as efficient.

Reply via email to