I still prefer the time of Win 2K (or max Win 7)

Windows 2000 was peak usability. Windows XP was also good, especially with the Classic or Standard themes.

The problem is deallocation... unless you tie the allocated object to an arena allocator with a lifetime somehow (Rust can model that).

Yep, rust forces you to think about lifetimes. Zig only suggests it (because you're forced to think about allocation, which makes you naturally think about the lifetime usually) but does not help you with it/ensure correctness.

It's still nice sometimes to ensure that you have to think about allocation everywhere, and can change the allocation strategy for something that works for your usecase. (hence why I'm looking forward to the allocator api in rust to get the best of both worlds).

People that wouldn't buy it, aren't customers :)

And Javascript free web...

IMO, we need a RSS optimized browser that would also block Javascript before user interaction (or even more).

How would "RSS optimized" work in the context of a browser?

Reacting somehow to user input, even if not perfect, is more important for me... That's why we have HW cursors, and frame interpolation in games, etc...

HW cursor is an implementation detail, and are used by basically every wayland implementation.

And reacting is one thing, big black rectangles blinking on screen is another.

Once upon a time (maybe even before pthreads) I made an automatic version of this using SIGALARM for profiling.

I made a wrapper (using LD_PRELOAD) around XSelectInput that would trigger the signal 0.1 seconds after a keyboard/mouse (or other event) was received... Then it would dump stack traces every 0.1 seconds where "slow" UI code was being executed (before next call to XSelectInput).

Not Cyrillic?

Yeah, I remember switching from OS/2 to Linux when OS/2 was more or less abandoned.

Same here... I do not wish for a laptop with >65W USB-C power requirements.