I see the argument, but for you as a coder of CMSes, static is a step down in complexity, but for me (also a coder but, you know, cobbler's children, etc.), interposing a build/deploy system (unless it's on Netlify or some such, and that only adds complexity) is a step up. I "blog" from a variety of places (home pc, work pc, android, ideally linux) and having a build system, with all dependencies resolved, everywhere, is an issue.
At some point (conceivably), it will cease to be fashionable for young women to be involved in politics, at which point Teen Vogue will cease to be leading the revolution.
But, for now, it IS fashionable, and I surely do support it.
There's at least one article somewhere about cell phone use among those in poverty (because I've seen it). If one were to visit young people in extreme poverty (I have), one would see that almost all of them have a cell phone, which, in the US, is taken as a sign of not-really-in-poverty.
But they do have actual economic benefits (in the article, knowing what/where the best prices for goods are, since small business is key).
«our long-standing partnership with Microsoft will continue to support organizations...»
So... I'm not up to speed. Do MS and Redis have an explicit (formal) side agreement that has MS shipping $$ to Redis and Redis declining to sue under SSPL? (Like, "Redis licenses Redis to MS under these specific terms, etc. etc.")
Because, otherwise, wouldn't SSPL also apply to MS?
And if I, as pee-wee cloud services offerer, use Redis, am I SOL...
Ok, but the elephant in the room is masto, unless maybe we get QTs into the protocol (I think). Including the ability to take down a post that's being shamed, if the poster so desires.