3 ms·
> Not enough type safety Sure? Depends on use case. > too much verbosity Doesn't meaningfully affect anything. > Too much fucking "if err != nil". A surfac
by Mawr 1y ago
> Not enough type safety
Sure? Depends on use case.
> too much verbosity
Doesn't meaningfully affect anything.
> Too much fucking "if err != nil".
A surface level concern.
> The language sits in an awkward space between rust and python where one of them would almost always be a better choice.
Rust doesn't have a GC so it's stuck to its systems programming niche. If you want the ergonomics of a GC, Rust is out.
Python? Good, but slow, packaging is a joke, dynamic typing (didn't you mention type safety?), async instead of green threads, etc., etc.
- pydry 1y ago>packaging is a joke You should see what package management was like for golang in the beginning "just pin a link to github". That was probably one of the most embarrassing technical faux pass ive ever seen. >dynamic typing Type hinting works very well in python and the option to not use it when prototyping is useful. >Rust doesn't have a GC so it's stuck to its systems programming niche. The lack of GC makes it faster than golang. It has a better type system also. If speed is really a concern, using golang doesnt make much sense.