i guess joggers are kinda a “casualty of broad language”… people see pedestrians, people think walking is okay
but also just like bikes on the freeway are a hazard, i’d say pedestrians of all kinds on the veloway is a hazard… they’re always just going to be much slower
yeah tbh i think for this to work they probably need a pedestrian access running exactly beside it so there’s no reason for pedestrians use the separated cycle lanes
people are gonna be entitled and fighting that is a losing battle
hard disagree on what belongs in the same commit history… a single merge should be an entire feature, and your commit history should read like a change log
Squashed commits are not atomic … overall task requires modifying multiple different systems
that’s why monorepos exist
i’d say squashed commits aren’t always atomic, but this is one of the biggest reasons people add the complexity of a monorepo: if changes cross multiple systems, ideally their merge/revert should be an atomic operation
you either have deployment complexity (ensuring the feature is in all deployed systems before switching over), code complexity (dealing with the feature only maybe exiting in parts of the system), or repo complexity (where tools manage a monorepo and thus commits and PR/MRs are atomic across your system)
“not actively harmful” and “notionally the bare minimum” are pretty low bars and i’m glad that, for once in modern memory, mozilla cleared them
faradays cage is still around and solid!
i mean, we should stop hiring business consultants to write software lol
there are small/local consultancies that actually do a great job: just like hiring a team of contractors
large multinationals with a focus on accounting and business with “oh also we do salesforce” is the real problem… they optimise their costs rather than focusing on quality
cheaper than fixing myki
australia’s notes all have tiny signatures of the governor of the reserve bank, and the secretary to the treasury and have for at least as long as i can remember… i don’t think it’s a vanity thing in that case
codeberg seems to be the new hotness
you install a distro because of all the software it includes and how they interact out of the box
you’re completely right that systemd is a background service that most people don’t care about, but it does make the whole system more reliable, and much easier to administer for servers or workstations (enterprise management; not personal)
you certainly do want an init system… even sysv-init is an init system: you need something that runs as pid 1 that triggers other services. systemd starts services, and also ensures they’re in the correct security contexts, running as the correct users, makes sure they’re healthy, tracks dependencies (not just order; this speeds things up because it can be parallel, ensures failures don’t cascade, and means there’s far less jank in random bash scripts)
this isn’t a big political statement: this is an acknowledgment that linux users - not all, but some - will want/require something like this… and systemd user database is the place where that information is stored on modern linux systems
waiting for california would be us-centrism… california isn’t the only place in the world that exists; it was just the trigger
forget cookies, reload, begin; forget cookies, reload, begin
… auto clicker
they’ve said “we speak for the widest used extended user service in linux”… because… that’s what they are
to say they “speak for the distros” is ridiculous: in that case, every time they merge a feature they “speak for the distros”… they speak for their own software, which is implemented by distros precisely because they implement things like this
because theyre being pragmatic… laws are starting to be introduced around the globe for parental controls - whatever that means in each jurisdiction. given that, there needs to be options available to people wanting to, or required to comply with said laws… the best place to do that is in a user record, as an optional field… extensible user records, in modern linux, are stored in systemd
it needs it in a similar manner to how it needs location, email, real name, etc: it doesn’t functionally need it, but it’s a place to store the metadata associated with a user such that other applications can use it
because whilst systemd-initd is the part that everyone is generally aware of, that’s linked to systemd-logind so that processes can be started as different users… process init, session management, and user management are intertwined
they don’t have to be for sure - sysv init proves that - but in modern linux, they are and that comes with a load of benefits
https://deepwiki.com/systemd/systemd/6-user-and-session-management
good thing it’s entirely optional then!
or just don’t set it
tell me you have only a passing understanding of how modern linux is architected without telling me you have only a passing understanding of how modern linux is architected
a great illustration of the dunning-kruger effect