@bitprophet eh i've moved from python to golang and it's not so bad now go doesn't have GOPATH and has modules, generics

but the hashes are random order and i want to scream every time

@tef yea I think GOPATH/modules is partly what I meant by hearing packaging got less shite.

Also yes, lack of generics was a very easy dunk BITD but I did hear they got them. Was less of an issue for me as I'm only really grokking generics in the last yearish myself (doing more typed Python) 🤪

@bitprophet

the thing about go, it that its best contemporary is java, that's the sort of mindshare it competes with

rust wants to compete with c++, but it seems the largest adoption comes from people from ruby, python, etc, who want something more mechanical, rather than existing c/c++ users

there is rarely a case where it is "go or rust" because usually the other constraints "ffi/embedded" force your choice

@bitprophet

but yeah go has an option type, it's a pointer :v

@tef yea, that's a fair analysis, I've definitely noticed the “folks coming to Rust from interpreted languages and quietly avoiding most of the features added to Rust to entice C/C++ folks” thing.

Also, I'm thinking about situations where there is a reasonable language choice in play, vs anytime where a best-in-class tool requires a specific binding or w/e, I would always just…use that for that need.

@bitprophet it's just, yeah

rust's key feature, the borrow checker, is a lot more expensive to use and develop with than plain old garbage collection

so for embedding inside c++ or writing embedded systems, it's a no-brainer choice, and well, on you go, but for the rest of us weenie application developers

things like library availability (stdlib r otherwise) dominate choices, and for all it's faults, go is still way way easier to use