One thing Torvalds enforces is not breaking userland. So it shouldn’t be kernel problems. More likely its some other lib that breaks compatibility.

There was the RustConf Reflections Drama…

Tim Chevalier left Rust over Drama. One of the top two contributors at the time.

Well, it startend with conduit. That was a respectable name. The development slowed down and someone wasnt happy abput not getting pr merged. Then it got forked to conduwuit.

Speed picked back up. There was later a massive meltdown for some reason. To successors emerged continuwuity and tuwunel.

Its also not the first pig cycle in the memory industry. There used to be over 20 manufacturers producing ram. These three survived because they didn’t massively ramp up production when demand increased. So they’ve collectively said, we are not really investing into production.

Mold is already very fast, however it doesn’t do incremental linking and the author has stated that they don’t intend to. Wild doesn’t do incremental linking yet, but that is the end-goal. By writing Wild in Rust, it’s hoped that the complexity of incremental linking will be achievable.

Oh I missed that. Oh no. Rolling your own crypto, surely nothing can go wrong.

For a discord or Telegramm alternative it doesnt need to be e2e.

It’s also a lot harder to make money with open source. You would need to find something to offer on top for money. That can be hosting (nextcloud), support (redhat), consultation (hyper) or additional features(zeds AI offering).

In a side node: when building for geentoo it should be possible to build all rust libs as dylib. The compiler only offers a stable abi for the same version and all flags being equal. When building everything yourself that should work at the coat of updating the compiler requiring a complete rebuild of all libs.

Sourcehut duports git-email.

Step one: Download a C or CPP repository.

Step two: Replace all semicolons with a greek comma.

Step three: ??

Step four: Poison Copilot, so that it randomly insert greek comas that the compilers totally choke on.

They can just sell their normal phone. As long as the user is able to run the installer it doesn’t really matter.

In the worst case it will just be Motorola shipping their base android version with verification and then just flashing grapheme over it. Just the way it currently works with pixels.

Didnt know abput that.

They store where to deliver the message, but not from who that message came.

I should have been more clear.

I meant for self hosting.

Though realistically, even if the service is provided for the public, you could just use an instance of keycloak or something similar with open registration. That’s what an association I’m close to is doing already.

By default, the Credentials provider does not persist data in the database. However, you can still create and save any data in your database, you just have to provide the necessary logic, eg. to encrypt passwords, add rate-limiting, add password reset functionality, etc.

That is exactly the complexity I wouldn’t want. With just SSO it is enough to send a redirect URL to the browser and on the callback set a cookie. No js needed. If your service gets compromised and someone leeks the credentials, just log everyone out.

If i created a service I would go in the opposit direction. Only offer SSO and no other option.

You loose quite a bit of complexity that way.

If anyone ist surprised by that they should look up why niantic was ever founded.

It was always about data collection in the real world.

I mean, if you really want to use a different language, there are macros that enable that for you. Here is the example for Rost. Just Rust, but in German.