I just skim through and make sure everything makes sense. Especially naming and comments.

What do you think a self review is?

If you couldn’t figure out what flutter is in 10 minutes that reflects poorly on you much more than anything else.

It’s weird that you are aware of this but still decided to prsent it as “hiring a dipshit to make a shitty java clone”. It pretty clearly says that Eich wasn’t the one that wanted to make it java-like.

That only works with c# though. What they are suggesting is compiling any arbitrary language to wasm and run that anywhere. Which is technically already possible with WASI and any of its supported runtime.

Yes a strict 80 character limit would be bad but that’s why modern formatters aren’t strict and default to 90-100.

I’ve pretty much never seen code that would have been more readable had the lines been longer than that.

My main argument is still that shorter lines are more readable. I just think it’s a bullshit argument to say that long lines are fine because large monitors exists. I don’t see how that makes me crazy.

How does it make code neater? All it does is add a ton of empty vertical space. It makes files arbitrarily longer at essentially no benefit.

How are browser not that already? What’s missing?

They are an open standard and used to make many thousands of apps.

I have a massive ultrawide and I still 100% believe in line limits. Long lines are harder to read in general but even with a limit of 100 I frequently have 3 files opened next to each other and I can’t read entire lines easily. Line limits just aren’t about the size of the monitor and I can’t believe people still say that.

Performance is always about doing as much as possible with as little as possible. Making a game runs faster automatically makes it more efficient because the only way it can run faster is by doing less work. It’s just that whenever you can run faster it means the game has more room for other things.

On the subject of dom manipulation from wasm I highly recommend this video https://youtu.be/4KtotxNAwME. It’s from leptos author, one of the more popular wasm framework. The TLDR is that modifying the dom isn’t the bottleneck for wasm.

You can absolutely modify the dom, you just need to go through a thin js glue layer between the dom and wasm

The video is essentially saying the exact opposite of what you are saying. It’s showing leptos to be much faster than react and I know primeagen doesn’t think rust is harder develop.