Doesn’t help they pick the oldest guys in the room to become the pope.

You’d be surprised

It’s the Cypherpunk’s Manifesto all over again.

TCP over IP as a protocol is an “open standard”. Network implementations are nearly always strictly proprietary.

The “protocols” behind browsers are public. HTML, CSS, and ECMAScript are all well defined on sites like the Mozilla documentation. You are free to implement your own browser that follows these standards.

PvP combined with PvE The infinity signs might signify the huge amount of players and other environment entities?

Same here. I did not think twice about this picture or a few other posts in the past and yet there are pitchforks in the comments and I think to myself “What are you all on about?”. I rue how unrecognizable AI “slop” has gotten.

It just means they are lazy and have no respect for other people’s intellectual property.

It’s not open source by choice. In fact, they tried breaching the license to keep it closed source.

The graph makes no sense. Did a generative AI make it.

Buy EU products!

I see you’re a person of culture. I too get flashbanged every morning by all my lights.

Your cat must be in on the conspiracy. Perhaps even part of the deep state.

VSCode is not even a true IDE like, for example, VS itself.

Great details! I know the difference personally, but this is a really nice explanation for other readers.

About the last point though: I’m not sure Go always uses the maximum amount of kernel threads it is allowed to use. I read it spawns one on blocking syscalls, but I can’t confirm that. I could imagine it would make sense for it to spawn them lazily and then keep around to lessen the overhead of creating it in case it’s needed later again, but that is speculation.

Edit: I dove a bit deeper. It seems that nowadays it spawns as many kernel threads as CPU cores available plus additional ones for blocking syscalls. https://go.dev/doc/go1.5 https://docs.google.com/document/u/0/d/1At2Ls5_fhJQ59kDK2DFVhFu3g5mATSXqqV5QrxinasI/mobilebasic

Well, they’re userspace threads. That’s still concurrency just like kernel threads.

Also, it still uses kernel threads, just not for every single goroutine.

I absolutely love how easy multi threading and communication between threads is made in Go. Easily one of the biggest selling points.

Hands down the best game I ever played. The immersion is unreal and the ending left me with goosebumps and a dropped jaw.

Still, 200 should not be returned. If you have your own codes, just return 500 alongside that custom code.

It sometimes will still decide to murder your boot manager.

I doubt it but Schengen would be nice with them.