for crypto, lots and lots of people losing money, especially middle class people and Black people were the ones who suffered from crypto scams. for ai, people losing work, bosses demanding more, and right now, paying higher electricity bills. that has been extremely polarizing.
where previous technologies have been oppositional they've mostly been that in opposition to companies, not individuals, never touching the level of interpersonal warfare that these technologies seem to have at their absolute core.
crypto was an oppositional technology to central banks, etc, reinforced by constantly telling people that they'll 'stay poor' and so on. it was built on resentments. ai has done the same: providing robot artists to demean the work of real ones. nearly gloating about job destruction.
which may be true! it's a more real technology. okay, after having thought about it I have a much clearer response to your initial prompt: because they are technologies with clearly defined losers, which are almost defined by how they define losers
i totally agree that llms are a more real technology with actual adoption, but i can log into linkedin and provide you with an endless stream of stupid claims, or look at openai's webpage for the sentence "It may be difficult to know what role money will play in a post-AGI world."
at the height of crypto mania, people said that mortgages would be on the blockchain, websites would be all on web3, and fiat currency was on its way out. i can't find a parallel to any of the other trends on that list other than llms, which people imagine as replacing capitalism itself.
imho because - they're both post-2016 largely right-wing cultural movements with a lot of uniquely odious people at the helm - unlike the rest of the list, they've both had dramatic personal impact on people's finances, mostly negative - both are much more totalizing than the rest
Published our plans for Tuist's next cycle: runners, full Gradle parity, faster Swift registry, test attachments, and sharding. Going deeper into infrastructure.
community.tuist.dev/t/ou... Proud of how much we ship at Tuist with 4 people. First cycle of 2026 done: Gradle cache, Linux CLI, flaky test detection, crash stack traces, bundle size alerts.
community.tuist.dev/t/20... 
Your AI rate limits are probably off.
Above 5% 429 errors: too tight. Below 0.1%: too loose. Here's the right baseline and 3 lines of Netlify config to set it.
netlify.com/blog/how-to-rate-limit-ai-features-and-avoid-surprise-costs 
Browse and pick individual skills here:
skills.sh/prisma/skills Prisma Skills are here.
Prisma 7 changed a lot. Your AI agent doesn't know that yet.
→ bunx skills add prisma/skills 
was able to port it relatively easily! www.val.town/x/stevekrous...
i think @tijs.org also has a val town at proto oauth demo running already too 
Now in Atuin 18.12 - custom keybindings! 🐢
One of our most-asked-for issues, the Atuin search tui now includes super flexible keybinding support. No more being stuck with our defaults
Read more: blog.atuin.sh/custom-keybi... 
Coming this Wednesday: LSP semantic token support. Zed can now use information from your language server for richer syntax highlighting. For example, highlighting of snippets in Rust doc comments.
"take an edible and setup kubernetes" challenge
We're bringing Tuist's cache + insights to Gradle 🧱
If your team uses Gradle and slow builds are a pain, I'd love to chat. Looking for early collaborators to shape this with us.
Global low-latency cache nodes close to your CI. We handle the infra.
contact@tuist.dev or DM me!
https://tuist.dev So cool!!!
i read about @mapbox.com publishing new maps with vantor imagery and wondered "who's vantor" and made this chart (based on wikipedia sources) www.mapbox.com/blog/mapbox-... 
Zednesday 🎁
thank you for the kind words! <3
yay we're trending on github! ⭐️
