2 ms·

Thank you for this very thorough review :) I agree with many of your points and I will do my best to incorporate them into my book. The reason I have compared

by dom96 11y ago

Thank you for this very thorough review :) I agree with many of your points and I will do my best to incorporate them into my book. The reason I have compared Nim to Python so heavily is for two reasons: 1) I used to be a Python programmer and chose Nim as a replacement. 2) I see a lot of Python programmer's trying out Go and saying describing it as a "better, faster Python". Perhaps that is just a HN illusion. I in turn believe that Nim is far closer to Python than Go will ever be. I am trying to show people that. Perhaps I should be comparing Nim to Go more as well. Your list of hooks is brilliant. It's hard for someone like me to remember features which make Nim unique since I use it almost every day, so these are really useful. I will see about mentioning some more of those things, in order to hopefully grab more people's attention! I have heard of Pony but have not had a chance to try it out. Looks promising. > Another nitpick, in the section on functional programming, why use var instead of let? The immutability story is just as important as first class functions... And you're missing the item (->) in the list of things the modules were imported for... Will fix, thank you! I have started out using 'var' then changed everything to 'let' (where appropriate), must have missed that one. Thanks again!

Jach 11y ago
I don't think I'll ever fully understand the Python --> Go transition, I sometimes have to shrug and attribute it to the power of big company backing. I think the drain has mostly been from Python web and networking programmers, probably a bunch of devops scripters too, but with web pretty much everything else that offers easy to use and high performance web servers out of the box is a cause for drain too, so I think the transition to Go directly is probably less severe than what one might think from HN submissions. Python is much more anyway and will remain a strong choice for many areas for years to come. For your point 2 I agree completely, for the few reasons that I can kind of understand why one would do Python --> Go, Python --> Nim (among several other viable options) ought to weigh in as a better choice based on the same reasoning, and Nim offers other extra reasoning criteria to sweeten the deal. I'm not sure how to target Go users other than to consistently show their favorite domains are done better with another language.

by dom96 11y ago

Jach 11y ago

I don't think I'll ever fully understand the Python --> Go transition, I sometimes have to shrug and attribute it to the power of big company backing. I think the drain has mostly been from Python web and networking programmers, probably a bunch of devops scripters too, but with web pretty much everything else that offers easy to use and high performance web servers out of the box is a cause for drain too, so I think the transition to Go directly is probably less severe than what one might think from HN submissions. Python is much more anyway and will remain a strong choice for many areas for years to come. For your point 2 I agree completely, for the few reasons that I can kind of understand why one would do Python --> Go, Python --> Nim (among several other viable options) ought to weigh in as a better choice based on the same reasoning, and Nim offers other extra reasoning criteria to sweeten the deal. I'm not sure how to target Go users other than to consistently show their favorite domains are done better with another language.