Dude, that doesn’t help either

I have to do it all the time. I was born and raised in the south by (relatively) liberal parents. I recognize that some of my neighbors my not be up to the standards of the rest of the country, but (I can’t believe I have to say this out loud) we shouldn’t ostracize a geographic region of people because of social issues.

Social reform isn’t achieved by running up to someone and saying “You’re an uninformed idiot from a flyover state and what you believe is incorrect.” It’s achieved by saying, “I know you don’t really mean that” when someone says some weird shit and calling them out in a more neutral environment. Unfortunately you have to convince people to be better. It’s too easy to just close yourself off and decline into your own beliefs.

Man, saying things like this just further the divide without providing meaningful contributions to any of the current conversations.

I like phoronix.com but don’t bother reading the article comments.

Well, that diagram brings up an interesting point. In fediverse if the host dies the federated content can still live on (theoretically, I haven’t checked to see if they cull content from dead hosts) but ATProto would dictate that the host is missing and therefore all content associated with the host is now immediately 404.

Edit: I stand corrected https://social.coop/@cwebber/113527531906508036

People out here complaining about Gentoo. My brother in Christ, you built the operating system.

I could appreciate a client certification that is optional, like a list of approved clients on their website or something along those lines.

It should not be enforced by killing the client. I like security, but I enjoy software freedom more.

Not sure about the Eco tank line, but the smart tank line botched the IPP interface. Ink level reporting is always wrong and printer status is regularly wrong. Exposed settings are limited to push people to the app.

To be fair, C predates dependency hell. It was either there or it wasn’t. C++ has less of an excuse, but it was just object oriented concepts taped to C so it’s no surprise it was also missing dependency management.

Now with cmake, gnu-make, meson, gradel, and the world of metabuild systems that wrap those, nothing will change. It it does, it might as well kick start world war 3.

I’m currently use RiMusic, but I wish something would automatically sort through my ListenBrainz recommendations

We’ll have a timeline for the plan to make the plan by next quarter

Was actually considering buying premium now that I use YouTube for music more than Spotify, but then the ad stuff happened and now this. Going to avoid it out of principle now.

Sounds like it would specifically be APRS if they were. Neat protocol. Unfortunately no encrypted traffic was allowed last time I looked into it.

https://github.com/MultiMC/Launcher/issues/4102

Wordpress

Dude tried doing that at the Dallas airport recently as well. I do believe they should be getting a larger cut but it’s sketchy as hell to not have anything backing the ride.

I want the statistic on how many Google employees use ad blockers now. It’s basically a necessity.

Because ARM was built to be cheap.

BIOS nowadays is basically a bootloader shim in EEPROM. The majority of the ARM ecosystem wanted flexible and cheap devices. This promoted the use of a small ROM loader burned into the device and a removal of basically all EEPROM from the SoC.

The flexibility came back through the use of a secondary bootloader layer normally stored in the devices primary storage. Most manufacturers use u-boot or coreboot on an SD card or eMMC. Android standardized this as part of their partitioning scheme. All devices have a dedicated bootloader partition housing the secondary bootloader and any additional boot artifacts.

Then phones became wildly expensive and invalidated most of this.

Also, do you think it’s possible that this way of doing things will come to the computer, with ARM hoping to gain a good share of the market and all?

It already has. Most of what ARM is doing to be cheap was already pioneered by PowerPC.

ARM EBBR specifications attempt to standardize this boot flow somewhat, introducing a standard EFI shell in u-boot. This does not solve the dependency on the secondary bootloader, and it doesn’t prevent people from shooting themselves in the foot. It just makes distro interactions with the secondary bootloader more standardized.

This is a short term loss for a potential long term improvement. By eliminating dependency on translation APIs they can force the use of more open solutions like oneAPI which is even getting buy-in from companies like Imagination.

Keeping cuda alive is a bad idea.