I've posted about this before but this is why I'm so FLOSS pilled these days. when all software is broken, it is simply practical and pragmatic to use software you can fix yourself
I've been putting up with first page loads in a freshly booted instance of Firefox taking up to like 20 or 30 seconds for so long and I'm starting to suspect it's the 1password extension causing the issue.
I would try to track it down further, but it's closed source software, so the best I can do is open a support ticket and beg to be taken seriously. Rather than, y'know, just diagnosing and fixing the problem myself.
the guy who famously argued that history was over after the collapse of the soviet union is now banging on about biological sex and free speech on american campuses. beyond parody
I got to ride a watermelon cargo bike today!! Single speed, coaster brake, backwards steering, no e-assist, absolutely freakin ripped. Had such a ball on this thing
The Internet Archive losing its appeal means one thing: pirate stuff. Pirate brazenly. There’s no point trying to do it the nice way - you’ll get shut down anyway. Copy, share, and archive to your heart’s content. It’s the only way we’re keeping digital media and our cultural memory intact.
this is often framed as a static vs dynamic linking argument, but that's a red herring. it's actually about maintenance and support. distro maintainers need to be able to bump a dependency in an emergency - regardless of linking strategy. having fewer versions on deck that you have to support makes this a lot easier.
a good place to start is with all the 0.x crates which are effectively stable but haven't yet gone 1.0 and made the commitment to stability.
as a result everyone pins a different 0.x version and it's an enormous headache for distro maintainers who would prefer to package a minimal set of versions - ideally a single version - to ease maintenance including security updates for as long as they are supporting a release.
it's a sign of immaturity imo that it's such a widespread view in the community to see this as an outmoded, old school way of doing things that needlessly impedes dev velocity.
I am a big fan of rust and think it's a natural fit for linux into the future. What isn't a natural fit is the npm tier dependency sprawl situation.
I really do think we need to listen to what distro maintainers are telling us, because they are the ones who understand how the rubber hits the road when it comes to maintaining and supporting software long term.
i sooooo struggle to deal with this kind of writing style
you can just write "we're not doing masks btw". like just own it. it's fine. it is, for better or worse, the norm.
this kind of writing just reads like you know it's not great, you know it's incompatible with the rest of the accessibility stuff you're talking about, you know to expect some blowback for it, and you're trying to preempt that blowback with therapy speak. it's the appearance of accountability while dodging accountability that gets me
@tursiae totally, and it's just not how the social contract works. I am giving something to you out of my own kindness, take it or leave it, but placing some burdensome task on me is the exact opposite of reasonable
there is a certain originalist leaning among unix people where they believe that unix was a perfectly conceptualised design from the beginning, and that all we need to reach unix nirvana is just do things more like we used to
of course the reality is that everything is informed by the realities of its time, and computing these days looks nothing like what it did 20, 30, 40 odd years ago. keep what's good, chuck out what isn't
the corollary to this is that we have a much better understanding of the domain now.
we scoff at terrible old APIs like libc's gets, but at the time we just didn't really know better. now we do, and it's easy to see why an API like that can't be fixed and shouldn't be used.
by the same token, it's unlikely that more complex constructions like an init system or build system from back then is really all that fit for purpose today. we have more suitable conceptual models for understanding and solving the problems we work with now than we did back then