If Trump just happened to find one of these ticks embedded in him, I wouldn’t be upset about it. I might even have a BBQ and invite him

I hear you, but these are solve-able human problems, not code problems:

Manager: Jose revert your commit, thanks. Jose: okay, it’s been reverted, I won’t do that again, thanks for explaining to me why exactly what I did was the wrong thing to do.

I’ve had this exact conversation about this topic at least a half dozen times over the last decade.

When it comes to legacy code, almost all auto formatting tools I’ve used allow you to ignore whole directories and files, which can be very handy for legacy areas of the codebase not yet ready for this transition.

As for scenarios where large rewrites are necessary, it’s best to separate from any actual work, so the blast radius is focused, and that commit can be marked properly using .git-blame-ignore-revs which completes fixes the history issues that are common amongst those who don’t know what they are doing.

Definitely a painful process it can be, but it’s better to fight this battle than it is to try and get 1,000 humans to agree on something as vague as “style”

These days it’s very common to write whatever code you want, and a formatter automatically rewrites it to conform to the projects rules during precommit.

Which is great because it allows you to focus on intent instead of format, and completely avoids any team disagreements or change rejections for trivial bullshit.

Often this is the correct pragmatic power user solution in UX design. Trying to solve it by default for everyone is much harder and will ultimately alienate some user.

But when people get bothered by an experience it is much easier for them to find the hidden setting that makes them happy again. It also preserves the existing experience, while allowing for greater customization in the long term.

Once a decent compromise is identified, that’s when it’s time to flip which setting gets to be the default.

We in this forum are a specific type, few use lemmy, and few invest in Arm directly.

SpaceX and Arm aren’t comparable, f.e. I know a college student investing in Space X, as well as an Elderly man, a cousin of mine who works in marketing, etc. It’s normal joes who want in. That never happened to Arm, and I’d be surprised if it ever does. It won’t be mainstream. I don’t know anyone personally who invests in Arm other than myself.

I’m talking about norms and sensationalism, not the state of a technology.

Notably ARM was not mainstream when it IPOd either, meaning it was a safe® bet at the time.

Most IPOs have become sensationalized to drive up interest, which is terrible for everyone except a select few.

Actually it technically does get irradiated by neutron activation, but the half life of Nitrogen-16 is only 7 seconds, so by the time it reaches the filters it’s already poof decayed away. (Very small amounts)

Same, I use Jetkvm for this too, has worked great

I’ve never owned a flip phone that I couldn’t plug in and swap the battery with a new one without it turning off. If that wasn’t normal with your phones I’m not sure why, maybe different circuitry?

Regardless making devices easy to repair, and thus open and maintainable was what I was getting at.

Codeberg / Forgejo and Tangled are my favorite options. Tangled because while it is VC backed, the open source and federated model are well thought out. If you haven’t read the source code I highly recommend it, it’s genius.

Just make hot swapping batteries normal again like it used to be.