One could argue those other reasons are symptoms of a bad economy.

Usually to make numbers bigger you have to hit the little plus sign then hit another number

Isn’t this one of those fiscal conservative loonies that wants to put austerity directly into the constitution

I think beeper plus has a bunch of integrations, I wouldn’t be surprised if that included LLMs

You can use matrix to bridge all those to an internal matrix server.

If you want a solution where that’s pretty much already done you can try Beeper

Russia and China entered into a defense cooperative with Iran without any requirement to go to war on the others’ behalf so it’s likely Russia and china supplying intelligence to Iran.

To be fair K8s was created by the Borg creators as a public version of Borg.

The program I use with WINE requires network access to authenticate and because it was for audio production, it had access to my filesystem for samples.

Ten bucks says you downloaded a compromised VST.

This is what I keep trying to explain to people when they laugh at the falling birthrate and go “haha more resources for my kids”

No no, if there are less kids they take those resources away

Japan just hooked up the national health insurance to the national ID.

For those interested:

Pangolin

deleted by creator

You can’t, if the code is open source it can be cloned to not fit in the license no matter what kind of license or fancy shenanigans you do.

The argument most MIT/BSL proponents have is that companies will be more likely to directly contribute if the project doesn’t have GPL “poisoning”.

I usually split the difference and license LGPL for everything.

the GPL v2 doesn’t have any less restrictions around strong copyleft (requiring that a company publish changes for components).

Maybe you’re thinking of the fact that GPL requirements don’t cross the kernel module syscall boundary?

This “poisoning”, effect is the reason the LGPL and AGPL licenses exist.

I agree to some degree but the gnu project doesn’t have a great track record for performative hosting (savannah is very prone to going down for long periods of time.)

I don’t begrudge better hosting infrastructure from a different non-profit.

As a guix user and package maintainer I’m ecstatic.

I’m so proud of the community for rallying around the needs and pain points of everyone and making this decision. This reduces so many pain points for a guix user and will hopefully smooth out the package maintenance process a great deal. Email is simple but trying to do code change communication over it can be very complex and time-laborous.

If you’re curious about functional packaging systems grab guix on your distro and give it a try!

Special shout out to anyone burnt out on Nix lang. Come feel the warm embrace of Scheme’s parentheses. :)

The problem is that the Linux kernel is monolithic so introducing rust into it does have certain repercussions about downstream compatibility between modules.

Right now the rust code in the kernel uses c bindings for some things and there’s a not-insignificant portion of C developers who both refuse to use rust and refuse to take responsibility if the code they write breaks something in the rust bindings.

If it was pure C there would be no excuse as the standard for Linux development is that you don’t break downstream, but the current zeitgeist is that Rust being a different language means that the current C developers have no responsibility if their code refactoring now breaks the rust code.

It’s a frankly ridiculous stance to take, considering the long history of Linux being very strict on not breaking downstream code.