Show newer

the Javascript ecosystem is essentially a failed anarchist society (long) 

What it used to be:
- many early adopters were anarchists/communists/etc.
- a huge public commons of highly reusable, high-quality, collaboratively developed libraries on npm, built for the benefit of the public, not for profit
- high degree of interoperability between different people's work, no need for pointless busywork to redo the same work over and over again
- successful(!) 'community specs' designed through community consensus (Promises/A+, CommonJS, etc.), gaining near-universal adoption
- fundamentally different structures from other language ecosystems, both technical and social, to make this work

What went wrong:
- large influx of users from other ecosystems due to hype in startup circles, unfamiliar with the established practices and reasons why
- early adopters failed to effectively convey and explain the ideological basis
- corporate adoption and subsequent capture; increasing "business value", leading to corporate steering of many essential pieces of the ecosystem (language spec, Node.js, etc.)
- npm became npm inc., a for-profit corporation, eventually being acquired by Github due to its large userbase, placing control over the public commons and its namespace in private hands
- ideological basis was forgotten, early adopters eventually left for greener pastures, now an almost purely parasitic environment of people leeching off the commons without guarding its integrity or health
- community-consensus specs started being replaced by "official", by-decree-from-up-high language specs (CommonJS -> ESM, Promises/A+ -> ES Promises)
- widespread adoption of these "official" specs, even though they were in many ways worse, due to their "official" label and many people assuming that what a central authority says must be correct or better
- rapid increase in shiny, well-marketed new tooling that is not interoperable with the existing ecosystem at all, and frequently works less well
- more and more commercial/proprietary 'sidecar' services (eg. Snyk) that you are expected to use, sometimes replacing open initiatives
- now an ecosystem and public commons that is rotting in every aspect with no real hope for recovery

... we should probably learn from this?

i should really look at clothing other than tshirts + hoodies but what even is there

ok i thought I lost this in weird git fuckery but I just had to do even weirder git fuckery to get it back

git.pixie.town/f0x/nixos/src/b

that's the custom ISO generator with install script for my Framework, after that it's borg extract for /home and /persist + morph deploy

Show thread

me peering at the screen

oh i can just turn up the brightness way more

everyone talking about a stuck ship? call that boatosocial

guerilla marketing campaign for gotosocial by making horrible puns/bits all day every day

@haskal but with just the whole spec doc + swagger outline you're screwed yeah...

@haskal hmm maybe i should write a tutorial... because when you know the routes / general flow it's a very easy platform to write bots for imo?

IHM - Walpurgis Night

better one day late than when i next remember this song i suppose :p

youtube.com/watch?v=bOd7QNXmCG

just because people there have their pronouns in their bio and say acab it does not excuse who they federate with

Show thread

please. i am begging you to stop interacting with absturztau.be

@val @charlag nothing is perfect but this takes active harmful effort as opposed to just sharing your post around all the vanilla instances you blocked, which makes a huge difference (no more shadow threads of fash replying to eachother under your posts, unbeknownst to you).

If an instance is actively circumventing stuff like this there's infinite other ways to do so as well.

Show older
Pixietown

Small server part of the pixie.town infrastructure. Registration is closed.