Sven Slootweg (soft-deprecated) @joepie91@pixie.town

For disabled pride month, here are a few disability emojis I've made! Feel free to add them to fedi servers and discord and stuff if you want :D

Starbucks was ordered to rehire half a dozen employees they fired illegally (with compensation for back wages plus interest) , reopen a store in Ithaca, NY that they closed in retaliation for union organizing and much more. The case file, including described remedies, is linked at the end of this story.

https://ithacavoice.org/2023/07/nlrb-judge-orders-starbucks-to-reopen-ithaca-collegetown-location/

#Starbucks #UnionBusting #Labor #Union

The tv at this hot dog shop is still in store demo mode

Sometimes I think of two things to put into a CW that shouldn't go together to create intrigue, then I come up with a post afterwards that ticks both boxes, like a sort of writers prompt or whatever they're called. CWs are good, you know. Social medias without them built in are missing out on a whole extra layer of Cursed Content™ to be enjoyed in a safe and controlled environment. Don't forget your hazmat suit x

Snapcast (https://github.com/badaix/snapcast) is terrifyingly good at what it does. Got several devices on the home network all playing back the same stream...with no perceivable latency at all. Not a ms... 😨

update: i am sweaty from carrying buckets of water but however the potatoes do, they will at least have been irrigated Once

Something that continues to amaze and frustrate me in equal parts, is that many of the "web has gotten overly and irresponsibly complex" criticisms are aimed primarily at React...

... even though it's probably the only 'modern' development stack whose design actually plausibly lets you opt out of its broader ecosystem and is designed somewhat standard-ly, unlike the 'competitors' like Angular, Vue, etc., which are rarely mentioned in this context

Like, to be clear, React does have its own problems, but also this sort of thing makes me wonder how many of those criticisms are well-informed, vs. how many are just based on imprecise anecdata

Here, have a starter pack of *valid* criticisms to make about the web instead:

1. Standards development is, de facto, controlled by Google; because they are the only implementor with any serious weight to throw around anymore
2. The web development industry, like the broader software development industry, has a serious problem with susceptibility to hype; technology choices are almost entirely marketing-driven
3. Individual developers (again, like the rest of the software industry), especially the well-off and privileged ones, often feel no responsibility whatsoever for the accessibility and effects of what they build
4. The incentives in designing libraries and frameworks are such that it is always more appealing to develop a monolithic difficult-to-maintain framework, even though that is technologically the worst choice; because it gives you a clearly brandable and marketable unit rather than a forgettable tool in the toolbox
5. The educational pathways for web development are almost entirely controlled by large tech corporations (directly or indirectly), and serve as "potential future employee" training courses rather than genuine in-depth education

You will notice that the common factor is "capitalism and kyriarchy", and not "javascript"

Reasons I will not take your "the web is broken" blogpost seriously (non-exhaustive):

- Does not distinguish between different ways of using tools that are designed to be used in multiple ways
- Does not distinguish between tools and their ecosystems (where those are plausibly separate)
- Recommends as the 'solution' some hyped-up novel thing that fails to clearly explain how it actually solves problems better than previous options
- Recommends as the 'solution' some commercial product
- Assumes that anything that is "standard" (usually for a remarkably narrow definition of the term) is automatically qualitatively better
- Recommends as the 'solution' some sort of strange infrastructure design that seems conveniently designed to fit one specific service provider (looking at you, Netlify)
- Does not recognize or understand the reason that "web apps" exist, and that that is a separate consideration from what web *sites* should look and work like
- Suggests replacing technologies that have nothing to do with the problem being described (usually HTTP is the victim there)

Seriously, there are so many valid criticisms to make, and so many possible paths forward. Do better, people.