

IMO ist das ganze viel einfacher: sie sieht es als ihre Aufgabe, die fossile Industrie am Leben zu halten bzw. zu stärken, ohne Rücksicht auf Verluste. Der Schaden, den sie aktuell verursacht, wird die erneuerbare Industrie für Jahre bis Jahrzehnte schwächen. Das ist genau das Ziel.

























As a passionate Golang hater, I can gladly explain!
if err != nil, even though that’s already bad enough. But the really fucked up part is the:=bullshit. It makes moving code around unnecessarily annoying, and it’s telling that few other languages share Golang’s approach._much easier to read, and this leaves upper/lower to signal other details. But I see that this is mostly personal preference.All in all IMO most Go code is 5x longer than necessary to actually express itself in a readable manner, all because the language still doesn’t have proper error handling or generic support (until recently at least). At the same time it’s fairly inflexible, the type system is still shallow and basic, and it’s still way too easy to shoot yourself in the foot.
The only good thing Go has going is the single file deployments, but I’ll gladly spend one hour of every remaining day of my life setting up containers, if it means I never have to touch anything Go again.