Something I still don't understand after all these years, is why all the conversation around #NixOS treats it as a "use it as-is" distro (which it really just isn't very good at!), and not more people are talking about what it could uniquely offer as a technical foundation for an actual end-user OS.
activism(?) meta, "you", potentially hot take (2)
It's interesting to see how this gets far less interaction than my critical posts usually get. I was kind of expecting that, though - as this is likely implicitly criticizing many of my followers, rather than some unspecified 'others', and so hits closer to home.
I do hope that people take this criticism to heart, even if they don't want to boost/favourite/reply to it.
The top 0.1% wealthiest Americans control about $20 trillion in assets.
A tax on them would raise $340 billion and never touch anyone worth less than $50 million.
If you're worth less than $50 million and opposed, you might ask yourself why and who you are furthering the interests of. https://esq.social/@andrew/113033909325519493
some people might need this reminder sometimes, i know i do
A mild case of a disability is still a disability
if you feel bad for "claiming" the title of disabled because your case is "mild" and "others have it way worse", remember that even your "mild" disability is vastly different from the healthy/abled experience, you have more in common with those that have it worse than with those that aren't disabled at all
Laptop in de klas: Goedkoop voor de school, duur voor de ouders.
Scholen gooien hiermee niet alleen de kosten de schutting, ook de hele strijd om de data en privacy komt bij de ouders op het bord.
Waar scholen samen met Sivon, Kennisnet en de Rijksoverheid eindelijk BigTech aan de AVG houden (soortvan), kunnen ouders dit nu opnieuw gaan doen. Terwijl scholen vaak een WindowsPC of Google Chromebook voorschrijven: "Klik maar even op OK"
what are some problems you've run into in the terminal with folders? so far I have:
* accidentally putting 1 million files in a folder, so it's impossible / very slow to list
* you deleted a folder while you're still in it in the terminal, and everything gets weird
* something about symlinks (what?)
what am I missing? (only problems related to folders please!)
Maybe the answer to everything here isn't really "the web sucks at DX", because it genuinely, truly, honestly has been making enormous strides in that aspect, but "we need better education/documentation on how to develop things end-to-end"
MDN actually does a really good job of this! But maybe we need more focused guides that are less technology-centered and more task/application-shape-oriented.
big question that's been popping through my head recently is:
so we're acknowledging that the obsession with DX has been a driving force behind the JS industrial complex or whatever, and the increasing bloat of webapps at the expense of users.
But should we put some of the blame on the web platform itself for not centering DX in such a way that doing the right thing is, in fact, most easily done through native APIs and plain HTML/CSS? Are web standards still moving too slow on that front? Are they still a bit too gun-shy?
Dumping responsibility on developers for trying to make their own lives easier when the tools you give them by default, as good as they are, still require them to jump through some hoops to do the right thing, seems like a losing strategy in the long run, no?
I've been having a lot of fun relearning and reevaluating a lot of my assumptions around web dev, but it's been a lot of work and there's really not a lot of easy, centralized education/documentation on how to put all these disparate pieces together into something cohesive. I just kinda have a bunch of lego blocks that got dumped in front of me and told to make a fancy, progressively enhanced, low-JS MOC millenium falcon out of it.
And I'm JS/TS developer with 15+ years of experience who works in FAANG and is really passionate about this stuff. I don't think I'd be able/willing to do all this otherwise.
@ireneista Perhaps too clever by half, but a concrete and well-enough thought out hope is indistinguishable from a policy proposal.
And even if you’re SUPER PURE along one vector, you’re always going to miss some other one someone feels very motivated to discipline you about.
And this must be okay for some people! But I try very hard to live in a state of at least partial uncertainty, because the alternative is a real vulnerability to Going Bad without realizing it. The downside of that stance is that shit just doesn’t roll off. This is true for a lot of us, I think—maybe artists most of all, bc art requires sensitivity.
I think one of the hard things about fedi, culturally, is that a whole lot (most??) of us are here because we are refusers of norms. And which norms and which levels of refusal differ.
So even if you’re at the 80th to 99th percentile of resistance to corporate social media OR mainstream party politics OR mainstream journalism OR cars OR the normalization of repeat covid infections, there will always be people popping up to tell you that by not being completely pure, you’re killing everyone.
The new contribution policy I'm considering for my open-source projects:
"PRs are only accepted for trivial fixes (documentation typos, fixing broken links, that sort of thing), but not for code. Please file an issue instead, if you've found a problem with the software. And if you wish to become a contributor, please reach out to me."
The reason for this approach: "one-off" PRs often cost more time to review and coordinate changes on, than it would take to just do it myself. Which would be fine, *if* there was a reasonable chance of the contributor sticking around, and putting the newly learned things into practice on future contributions.
But they almost never do, and it's not sustainable to put this kind of effort into an endless stream of one-off contributors who I will never see again. The whole point is to distribute the workload, not increase it. Having long-term contributor relationships also makes things like funding (of contributor work) much easier to deal with.
Thoughts?
We've got "first amendment auditors" noodling around in Vermont. These are people who come into public spaces such as the public library and film with (often) a pretense of being citizen journalists but often just being provocative and playing "gotcha" games with people who don't know/understand rules for filming in public places.
The ALA Office for Intellectual Freedom (I helped!) created this useful guide. Get your library policies in place before they show up!
https://www.oif.ala.org/auditing-the-first-amendment-at-your-public-library/
Technical debt collector and general hype-hater. Early 30s, non-binary, ND, poly, relationship anarchist, generally queer.
Sometimes horny on main (behind CW), very much into kink (bondage, freeuse, CNC, and other stuff), and believe it or not, very much a submissive bottom :p
Feel free to flirt, but if you want to actually meet up and/or do something with me, lewd or otherwise, please tell me explicitly or I won't realize :) I'm generally very open to that sort of thing!
Further boundaries: boosts are OK (including for lewd posts), DMs are open. But the devil doesn't need an advocate; I'm not interested in combative arguing in my mentions. I am however happy to explain things in-depth when asked non-combatively.
My spoons are limited, so I may not always have the energy to respond to messages.
Strong views about abolishing oppression, hierarchy, agency, and self-governance - but I also trust people by default and give them room to grow, unless they give me reason not to. That all also applies to technology and how it's built.