I'm doing crystal bindings for pipewire and wayland clients. It is nice to be able to do so much with so little. github / yxhuvud / [pipewire_cr | wayland_client]

I'm not certain I buy it, but I find it a little hard to motivate the training being fair use if used to regenerate the project in a different licence.

It is fairly ok for meetings and calendar integration.

It is dogshit at chatting, however.

> It is fairly ok for meetings

… when it works. And if you never have to change camera or microphone settings.

> and calendar integration.

The little notification that pops up telling you your meeting is about to start based on your calendar? The one you better not click in the first 5 or so seconds it's there, because then you'll end up with an error message that tells you absolutely nothing, have to go back to the chat, and try again?

No, it's not usable. For anything.

We would have, if the expensive memory was a long term trend. It is not - eventually the supply will expand to match demand. There is no fundamental lack of raw materials underlying the issues, it is just a demand shock.

Also, it's not like we have regressed in the process itself either, which was historically the limiting factor. As you said this is purely an economics thing resulting from a greedy shift in business focus by e.g. Micron.

What you are asking for is to make a library definition replacement to .h-files that contain sufficient information to make rust safe. That is a big, big step and would be fantastic not only for rust but for any other language trying to break out of the C tar pit.

What Apple restricts and is legal are not the same. Apple is doing malicious compliance and the legal system ain't buying it. But it takes some time and iterations to shake out.

The legal system has said absolutely nothing about what Apple is doing yet.

In many cases government texts are not covered by copyright, so it may not even be relevant here, regardless of it is is allowed to copy the data or not.

In the UK government records are generally covered by Crown Copyright (which is its own slightly more restrictive weird thing) rather than in the public domain. I haven't checked to see what the status of the court listings are, but the default is very different to the US.

There are middle grounds - for example you could redact any PII before publishing it.

That's what Ukraine does, but I guess we have more resources to keep the digital stuff running properly and not outsource it to shadycorp.

What we do here in sweden is that you can ask the courts for any court document (unless it is confidential for some reason).

But the courts are allowed to do it conditionally, so a common condition if you ask for a lot of cases is to condition it to redact any PII before making the data searchable. Having the effect that people that actually care and know what to look for, can find information. But you can't randomly just search for someone and see what you get.

There is also a second registry separate from the courts that used to keep track of people that have been convicted during the last n years that is used for backgrounds checks etc.

Unless you have link time optimization you would lose out on optimization and performance.

The whole thing is essentially a workaround for lack of sufficiently good/easy ways to package code in the ways people want to use it.