I second this. The design team at Apple must rework their copy as soon as possible.

This is clearly an issue, and it isn't even the biggest issue on macOS Tahoe UI.

No, it was not good.

Sorry.

TypeScript is way, way too slow to use for desktop applications. People try and, surprise surprise, those applications are slow as shit.

Qt has a C++ backend, so C++ is used. Qt is relatively safe and well designed.

Qt uses "slow as shit" JavaScript in its UI markup language:

https://doc.qt.io/qt-6/qtqml-javascript-expressions.html

Is your complaint with Electron, the "browser as local GUI app" framework that's been popular with SaaS vendors for their "native" apps?

Right, for small scripting, not for the majority of the app. All the backend interaction is in C++.

Like, electron is fine, but it's orders of magnitude slower than it needs to be for the functionality it brings. Which is just not ideal for many desktop applications or, especially, the shell itself.

Ultimately people use electron because they know HTML, CSS, and JS/TS. And, I guess, companies think engineers are too stupid to learn anything else, even though thats not the case. There is a strong argument for electron. But not for Linux userland dev, where many developers already know Qt like the back of their hand.

TypeScript transpile to Javascript - do you really want your operating system's shell written in slow ass Javascript? Modern C++ with hardening rules for the compiler[1] is pretty safe.

[1] https://best.openssf.org/Compiler-Hardening-Guides/Compiler-...

> do you really want your operating system's shell written in slow ass Javascript?

What, like GNOME Shell you mean?

Please permanently delete this repo forever.

I am having nightmares right now.

Who is stupid enough to use Qt in 2026 when you have React Native?

> They should rewrite it in Rust.

Why they? You should do it.

indeed

They actually should. As such a rewrite went so well for sudo-rs.

The article mentions 100% code coverage with tests as one of requirements from their users, and having "safe languages" emit defensive asserts and checks when compiling correct code means 100% branch coverage is impossible. How do you propose to address it with rust?

What

It's either trolling or sarcasm. May be both.

Not trolling. Everyone knows C is not safe.

C is safe if you know how to write it. Jokes aside yes you need to be more careful.

Life as a whole is not safe, and not everyone seems to be aware of this.

The kernel must adapt to Rust, not the other way around. Rust is the way!

Just use Chrome on a MacBook Pro M4 like everyone else

It's not up to me to use Google's browser. It's up to them to make webpages that work for all.

This flashed back so many of these comments, I unconsciously reached for the downvote button. Well done sir.

No thanks, I'm good.

Use it on an Air and there aren't even fans to be spun up