This isn't related too directly to WASM, what you want is DOM rendering only, you would theoretically reject canvas and WebGL rendering I imagine. But you could create DOM nodes with WASM. The only difference is that WASM is not as easy to decompile, but I can't imagine you're really unminifiying and patching Javascript are you?

I'd imagine similarly there were points in time where people who go to concerts just to see the electric guitars and lighting setups.

Why even try an start a conversation with that attitude? Wayland doesn't get nearly as much hate as Windows, Chrome, or iOS. But I guess literally nothing is worth writing an article that has the word "fuck" in it 7 times, because that crosses some kind of ultimate line?

Do people recommend the API surface should be totally flat and the same for all developers?

Most web programmers fall into that bucket for example. If you're the type to recoil at XMLHttpRequest, reaching to fetch or other even newer stuff. Then you'll balk at Win32 and be in a never ending pit of new Windows technology. I'd argue this is true of basically all new software. It's worth starting with whatever the oldest most compatible version of your target and ignoring the advertising and hype.

You can copy/paste or drag code snippets the chat window and they automatically become context like. (@myFile.cpp:300-310)

You can click any of the generated diffs in the assistant chat window to instantly jump to the code.

Generated code just appears as diffs till you manually approve each snippet or file. (which is fairly easy to do with "jump to next snippet/file" buttons)

These are all features I use constantly as someone who doesn't vibe but wants to just say "pack/unpack this struct into json", "add this new property to the struct, add it to the serialization, and the UI", and other true busywork tasks.

But clearly people in other cultures have a huge problem with it. Don't fall victim to survivorship bias + echo chamber.

There's not another obvious solution to the problem, it's debated in every thread. (no laptop + homeschool is not a real option for 99% of people)

Did it in ~300 lines of node.js, was trying to learn how to use JS for server stuff, seemed like a good idea at the time. It still works 5 years later, but it stands as a reminder to me to never use async/await.

I've never used Zig either, I just disagree that requiring constant maintenance is a good.

But in the world of desktop development it's possible for a library to be "done", having a 100% stable codebase going forward and requiring no maintenance. And it's not bad, it's actually good.

Requiring every dependency to be constantly maintained is a massive drain on productivity.

It it really true the LLM's are non-deterministic? I thought if you used the exact input and seed with the temperature set to 0 you would get the same output. It would actually be interesting to probe the commit prompts to see how slight variants preformed.

https://webassembly.org/features/