I think this makes you implicitly are a part of this trend, because even less pro user software exists in Rust because of your decision

Seriously, that's a good point. I'll seriously consider my position when gccrs becomes a bit more mature.

Thanks for your reply.

are you implying that using Rust involves using MS products?

So Swift didn't turned out like they imagined and Rust is just the next best alternative to that failed vision using Swift.

So far this is the first and only shift

They were doing their own custom language before Swift.

didn't know

> The browser and libraries are all written in C++. (While our own memory-safe Jakt language is in heavy development, it’s not yet ready for use in Ladybird.)

https://awesomekling.github.io/Ladybird-a-new-cross-platform...

only thing I could find - has it been actually used in Ladybird after all?

No, they never completed or adopted their own language. It was back in the SerenityOS days, before the browser forked into its own project.

https://github.com/SerenityOS/jakt

Benefit: saves battery on OLED and goes easier on the OLEDs themselves

Oxymoron

last time I researched enums in TS for a project, they were a mess such that it was better not to use enums in the first place

did you profile what made it so slow specifically? sounds waaaaay worse than I would expect

I did. I don't remember the specifics too well but a lot of it was cold starts. So just crunching the massive wasm binary was a big part of it. Otherwise it was the matchit library and js interop marshalling taking the rest of the time.

edit: and it cold started quite often. Even with sustained traffic from the same source it would cold start every few requests.

the JS layer is slow, indeed, but it shouldn't be that much slower that it meaningfully impacts frontend apps

A demonstration of that by the creator of Leptos:

https://www.youtube.com/watch?v=4KtotxNAwME

Fascinating video, thanks for sharing.

I git blamed it and if I read it correctly it seems like they even use version 1 as a default, because that's the actually spec compliant option: https://github.com/matrix-org/vodozemac/pull/287

These days Matrix does even have native support for conferences