3 ms·
When i first started Golang professionally, over 3 years ago, my first gripe was the GOPATH. WHY SHOULD ALL MY CODE SIT IN ONE FOLDER? I say gripe, it was a hu
by alias_neo 8y ago
When i first started Golang professionally, over 3 years ago, my first gripe was the GOPATH.
WHY SHOULD ALL MY CODE SIT IN ONE FOLDER? I say gripe, it was a huge annoyance. Why on earth, also, should i need to use the repo path in my structure and imports? It's obscene.
My next annoyance was the utter inability to easily parse dynamic JSON. But you know what the JSON looks like? Great, you'll only have to wrap it in a few structs and check your capitalisation if you want it to parse at all, no problem you think before half a day has gone just parsing one response.
The vendoring makes my month painful as I'm retooling the build system for the flavour of the month vendoring toy.
Structuring large projects still causes me great pain.
All of that said, Golang is now my favourite language to program in, and is my default for any new project.
- dom96 8y agoI've had a similar reaction when trying Go. While I'm biased, I strongly believe Nim offers a much better alternative which solves all of the problems you mention in a much better way. In particular, parsing JSON is a breeze, just like in Python. And there is no GOPATH weirdness. Give Nim a try if you haven't already, it may just become your new favourite language :)
- alias_neo 8y agoI'll look into it, thanks. I was planning on Rust being my next language but I'll see what Nim offers. I take it your bias is because your the/a creator?
- dom96 8y agoI'm one of the core developers
- alias_neo 8y agoOk! What's its standard library like compared to Go? I like that I can write powerful projects with few external dependencies. I don't like that C binding is slow and C++ binding is missing. How does it compare to Rust, which is currently top of my list to learn next? Can you suggest a reason, or a few why Nim should knock Rust from that spot?