Ephera

Yeah, that sounds about right for what I remember, too.

Huh, I swear I've seen a version of this comic where the shopkeeper has been robbed blind in the last panel.

As the other comment said, outside the browser WASI is what does IO. As for DOM access in the browser, I doubt they want to reimplement the DOM API, because:

• It's insanely complex. This wouldn't be done within one release, but rather take years to add a substantial amount of APIs.
• No one wants to have to maintain two versions of the DOM API documentation. You'd need to basically translate the entirety of MDN to some WASM API description. And in the end, hardly anyone would read it either way, because they're likely using some wrapper library to interact with the API.
• If you're using such a wrapper library anyways, it hardly matters to most people, whether this library generates JS API calls or some WASM API calls.

I try to stay as far away from JS as possible, and I do not think it's worth developing a WASM DOM API. With a competent framework, you can develop complex web-UIs without ever touching JavaScript, which is good enough for me.

Yeah, part of the reason I like open-source. The devs don't need to sell you anything, so they can just tell you that what they made is a steaming pile of garbage.

I've been noticing that when I read an English text to someone who also speaks my mother tongue, that I will switch to my mother tongue for reading out numbers. For some reason, it feels pretentious to pronounce it in English.

Jujutsu is a Git frontend, from what I understand, much like there's tons of Git GUIs. So, you interact with it in a different way, but you still push to a Git repository and others can interact with your code by using Git.

I guess, it somewhat lessens the grip of Git, because they can hook different backend services (e.g. Subversion, Mercurial, Fossil) into this frontend, and from what I understand, they plan to develop an own backend eventually. But yeah, for now, the communication standard is still Git.

I also have to say, I feel like many people don't realize how much dexterity and skill it takes to constantly crank that camera.

The twin-stick camera controls are a terrible solution, even if they may be the best we have. They are a major barrier for entry IMHO. With 2D games, you could hand a controller to someone, who doesn't play games very much and they'd still typically be able to play along. But with 3D games, that's so much harder, because now you have to press buttons and move the camera at the same time.

So, I imagine, even when the hardware became available, that various studios still tried to find simpler solutions.

Yeah, that is crazy to me. I understand them wanting to make other games in between and that making those games takes a few years each. Rationally, I'm on board with the decision-making and the math that leads to this.
But that the result is a generation who didn't have an Elder Scrolls part released in their childhood, that still feels like far too grand of a concept.

If you mean a DNS sinkhole, like Pi-Hole, then that shouldn't be a problem. Pi-Hole acts as a DNS provider, so:

• It could also act as a DoH provider. Someone seems to have done this for Pi-Hole here: https://discourse.pi-hole.net/t/can-pihole-act-as-a-doh-or-dot-server/56106
• You could disable (or not enable) DoH in Firefox to make regular DNS requests at your Pi-Hole, but then your Pi-Hole can use DoH to forward the DNS requests to outside DoH providers. Pi-Hole seems to support with either cloudflared or dnscrypt-proxy.

On Android, there's also ad blocking solutions that run a VPN server on your device, to terminate certain requests that way. I'm not entirely sure how those work, but if needed, they could presumably also run a DoH provider on your device.

Kind of felt like that last week. Our web-UI would automatically reload when you switched tabs, clearing out what the user had entered into a form. I started debugging, but the build times of our web-UI have been abysmal, making it extremely tedious to sprinkle log statements over the code for narrowing down what triggers the reload.

So, I decided to fix the build times first. The solution wasn't complex, basically just pull out a module into a separate library to benefit from incremental compilation, but with all the import changes and some additional restructuring, it still ended up being around 2000 lines of code changed.

Then I went back to debugging the reload problem, looked at it for 10 minutes, maybe rebuilt 3 times or so, and then made a lucky guess where I just changed one word for another and that fixed it. 🫠

"Trignometry" might be my favorite typo.

Yeah, this seems to be a display name, not some technical identifier. Microsoft cares about displaying it correctly, because it's their product, but I doubt anyone else does...