While you were seeing those problems with Java at Google, I saw seeing it with Python.

So many levels of indirection. Holy cow! So many unneeded superclasses and mixins! You can’t reason about code if the indirection is deeper than the human mind can grasp.

There was also a belief that list comprehensions were magically better somehow and would expand to 10-line monstrosities of unreadable code when a nested for loop would have been more readable and just as fast but because list comprehensions were fetishized nobody would stop at their natural readability limits. The result was like reading the run-on sentence you just suffered through.

Comments URL: https://news.ycombinator.com/item?id=47404833

Points: 1

# Comments: 4

Watch as they stand at the watering hole, bored and listless. A sad look on their faces, knowing that now that Go has generics, all their joy has left their life. Like the dog that caught his tail, they are confused.

One looks at his friends as if to say, "Now what?"

Suddenly there is a noise.

All heads turn as they see the HN post about UUIDs.

One of the members pounces on it. "Why debate this when the entire industry is collapsing?"

No reply. Silence.

His peers give a half-hearted smile, as if to say, "Thanks for trying" but the truth is apparent. The joy of hating on programming languages is nil when AI is the only thing looking at code any more.

The Go hater returns to the waterhole. Defeated.

"Automation Should Be Like Iron Man, Not Ultron" https://queue.acm.org/detail.cfm?id=2841313

In fact, the author shows that this is an evolution of go vet and others.

What’s new, however, is the framework that allows home-grown add ons, which doesn’t have to do everything from scratch.

It’s accurate to say that a user is waiting for the change to propagate if they are sitting there clicking re-try as they wait for the cascading cache expirations to do their thing.

Years ago MS depended on Windows. It was the profit center. Everything MS did was a moat to sell more seats. Even MS-Exchange was just a ploy to force enterprises to stop deploying any other operating system.

That all changed with Azure.

MS realized they could make billions in Windows or trillions with Azure.

They changed the org structure. Now Azure is at the top and everything else is a moat or a way to draw people to Azure. They changed the sales commission (your multiplier doesn’t kick in unless you’ve sold enough cloud services).

Windows is no longer a profit center. It’s a cost center.

Anything that scares people away from using Windows is a benefit.

Let those other suckers spend money developing operating systems. As long as it runs on a VM in Azure, Microsoft will profit.

Windows being worse and worse isn’t a bug. It’s a feature.

Then they realized interoperability could make them more money, and they invited him and his team to Redmond for a week of working with MS engineers to understand the latest protocol versions. Oh wait, no, it was because the EU forced them. https://www.theregister.com/2007/12/21/samba_microsoft_agree...

Where are you from?

Many advanced Go features start in certain platforms and then expand to others once the kinks are worked out. It’s a common pattern and has many benefits. Why port before its stable?

I look forward to your PR.