At least a while back there was not a built-in GC on the WASM runtime side, so the GC has to be shipped with every app.

They’re most likely actually responding from Mastodon.

No way they will ever be in sync.

I’m pretty sure Louis is just another recipient of FUTO’s funding, not “the” other partner to this dude.

Yeah, for this the only real argument is performance, I was answering in general.

Both. Primarily most software written in C should be rewritten to a memory safe language, be it Rust or some other alternative. Because there is a lot of software written in C, this is a veeeeery long term goal, and will probably never be achieved 100%, but at least Microsoft seems to be on board with this.

I have run nextcloud:latest on Docker for the last 2 years and have had 0 problems. Maybe upgrading all the time works better than by releases.

And where l is not the same as 1

I mean it worked for long enough 🤷‍♂️

Nope, the article says that what is and is not a grapheme cluster changes between unicode versions each year :)

Import from OpenAPI, yes. Super useful if you use Swagger and it starts lagging :)

Webpack takes 10 minutes to build the release bundle in a project at work…

More control? If you’re speaking from the app developer’s perspective, dynamic linking very much gives you less control of what is actually executed in the end.

Except with dynamic linking there is essentially an infinite amount of integration testing to do. Libraries change behaviour even when they shouldn’t and cause bugs all the time, so testing everything packaged together once is overall much less work.

This is AMD64 - extensions to x86_64/AMD64 are created all the time, after a while they become expected by software distributors and compiled software relies on their existence. That’s why new games don’t work on old CPUs.