278 karma · joined March 16, 2016
And people are falling over themselves to use Go in places that seem inappropriate. Most of Go's strengths shine in a large team of mediocre developers: Low build times, low abstraction, quick ramp-up, etc. So why do startups choose Go? You're just shooting yourself in the foot. Use OCaml, use C++, use Clojure, hell, use Swift or Rust, just use something that at least pretends to care about expressiveness and abstraction. I actively avoid working for shops that use Go heavily, it's an indicator of cargo-culting.
So your criticism seemed out of touch and (can't believe I'm quoting pg) "middlebrow."
I LOLed at https://www.milkywaybar.com/nutrition
> MILKY WAY® is a delicious and indulgent treat that can be enjoyed as part of a balanced diet and healthy lifestyle.
Why lie? It's heavily-processed, high-fat, high-sugar candy. Of course it's unhealthy, there's nothing inherently wrong with that.
Of course bettermotherfuckingwebsite.com uses #444 on white. bestestmotherfuckingwebsite.com probably dials it up to #777 with a light sans-serif.
The people on top desperately want us gone, and when it happens it'll happen so quickly you won't know what hit you. Software engineers need to recognize this common threat and organize (labor) sooner than later. Even more important is for all engineers to plan for an imminent future where developers are not paid like they are now, if at all. We have it good, but we will be automated away like everybody else, just a little later.
What does this mean? Do you mean "provoked"?
https://github.com/mrdoob/three.js/pull/9310/files#diff-2ac7...
becomes
https://github.com/mrdoob/three.js/pull/9310/files#diff-ff6e...
On the surface it seems bad.