Everything should be written in #Rust, but not everything deserves it.
And that’s when I reach for #Go
And in the end I get paid to write #JavaScript and #PHP
@jesuscova as long as I get paid, I don't care, it all sucks
@schizanon with this economy I’d write Visual Basic for money
@jesuscova TBH these days I think Go and JavaScript are equally robust, with a nod towards JavaScript (really, TypeScript) for giving me slightly fewer footguns and a lot more third-party libraries.
Go is great for multithreading, but I need to multithread something at the process-interior level so infrequently I don't care. 90% of my multithreading these days is multiple services on multiple machines doing RPCs over JSON.
@mark I deff agree with you.
I saw a few weeks ago this JS proposal where a function that could throw could return an error value as in Go, which I’d rather do every time over try catch.
https://github.com/arthurfiorette/proposal-safe-assignment-operator
With this in the language, it would humble myself to just use a strict TypeScript for most cases.
@mark @jesuscova JavaScript has no type check at runtime, so go and even PHP are better here.