SolitudeSF

no build instructions, binary artifacts in repo. yuck.

this benchmark is afwul (which is expected)

this not even close to expert knowledge, thats entry level

its true that leadership does nothing and development is stuck, but even in this state nim is probably enough for most people.

> how much frustration you will encounter fighting the compiler and broken / under-specified language features and semantics might be a turn-off.

unless you limittest generics, most people wont even encounter this.

> My advice would be to look elsewhere.

that would imply that there is a better alternative

Nim

thats not a different way of doing same thing, its doing different thing. this not even an argument, if language can provide multiple memory management strategies, in what world is that a bad thing?

and if you somehow confused about choice (of gc), you should stick to default.

also, there is no such thing as "There is Only One Way to Do It" languages. your entire argument is just a circlejerk point.

> Nim implements just about every paradigm it can think of, and if there are multiple ways to implement a paradigm, it implements them all.

any examples?

he is not trying to sell/convince you to learn gtk. he is warning if you already want to learn it. not everything posted on hn should be a promotion material.

glad subjects like you are getting filtered by themselves

it still compares algorithm implementation, not the language speed.

thats not how it works

you can compile with `--stylecheck:error/hint` for enforcing consistent naming.

#? replace(sub = "\t", by = " ")

but please, dont

> Hate speech against functional concepts in the community

are you trolling?

> Some arrogant community members were tolerated just because they wrote popular blog posts on Nim implementing a fashionable pet project.

for example?