bug or backdoor?

What different way of doing things?

If I want sequential execution, I just call functions like in the synchronous case and append .await. If I want parallel and/or concurrent execution, I spawn futures instead of threads and .await them. If I want to use locks across await points, I use async locks, anything else?

I can't follow that it's hard to learn and unintuitive

Typst

A lot of love for a company which doesn't even let you chose the apps you want to use.

A wonderfully out-of-date sentiment.

What do you mean? Something like "freedom is so last year, it's all about obedience now"?

oh I just love the replies

This is not a bad thing.

Please explain?

Unless you choose your hardware first…

at least you can still decide on the software you install

How do you not install all the ads?

There is native to the OS and there's native to the machine.

Anyways, I'm both cases you don't really have to write it twice.

Native to the OS: write only the UI twice, but implement the Core in Rust.

Native to the machine: Write it only once, e.g. in iced, and compile it for every Plattform.

hopefully not implying needing a gc for memory safety...

Yeah, there's always Fil-C (Rust isn't memory safe in practice).

oh that would be a dream

> And if the alternative is a memory-unsafe language

and if not?

> and if not?

If the alternative is memory-safe and easy to build, then maybe people will switch. But until it is it's irresponsible to even try to get them to do so.

Until? Just take what's out there - it's so easy to improve on Electron

Like what? Where else (that's a name brand platform and not, like, some obscure blog post's cobbled-together thing) can I start a project, push one button, and get binaries for all major platforms? Until you solve that people will keep using Electron.

There are quite a few options. Many of them look dated though. I think that's the usp of electron.