3 ms·
The content is mostly ok, but the title suggests that there's some obvious alternative to Go that we should be using. If he's implying it's Rust, then he's tota
by icholy 4y ago
The content is mostly ok, but the title suggests that there's some obvious alternative to Go that we should be using. If he's implying it's Rust, then he's totally disconnected from reality.
- bovermyer 4y agoIt's buried in the article, but I think the suggestion is "use almost any language other than Go" rather than Rust specifically. The takeaway - if you gloss over the ranting and look for the good bits - seems to be that you should choose a language that handles a lot of the boilerplate for you (e.g., no verbose error handling) and has FFI. It's not a bad argument, and it's making me think about how and when I use Go. For that, at least, it's worth reading.
- wperron 4y agoIt's really not, and it's even saying so explicitly in the article.