zlacker

>>ustad+(OP)
Has Go become the new PHP? Every now and then I see an article complaining about Go's shortcomings.

>>figmer+Ta
Go is a pretty good example of how mediocre technology that would never have taken off on its own merits benefits from the rose tinted spectacles that get applied when FAANG starts a project.

>>pydry+Zb
I don’t buy this at all. I picked up Go because it has fast compilation speed, produces static binaries, can build useful things without a ton of dependencies, is relatively easy to maintain, and has good tooling baked in. I think this is why it gained adoption vs Dart or whatever other corporate-backed languages I’m forgetting.

>>christ+Bd
I tried out one project because of these attributes and then scrapped it fairly quickly in favor of rust. Not enough type safety, too much verbosity. Too much fucking "if err != nil".

The language sits in an awkward space between rust and python where one of them would almost always be a better choice.

But, google rose colored specs...

>>pydry+we
I’m almost with you. If there was a language with a fast compiler, excellent tooling, a robust standard library, static binaries, and an F#-like type system, I’d never use anything else.

Rust simply doesn’t cut it for me. I’m hoping Roc might become this, but I’m not holding my breath.

>>christ+Bi
OCaml? Possibly Haskell as well?