Luís Fontes

svelte.dev/blog/sveltek...

I have been writing this post about the economics of open source, on and off, for 13 years. I wasn't expecting to end up at "Microsoft should send corporations a huge bill" but nothing else we've tried has worked. https://seldo.com/posts/nobody-pays-for-open-source-we-can-force-them-to/

The real AI risk is inside the labs (a reply to Amodei's post on open weight models): antirez.com/news/172

📊 LayerChart 2.0 is officially released! After ~16 months of development and 67 pre-releases, the official 2.0.0 release has been published! 🎉 This includes the Svelte 5 rewrite, CSS framework agnostic, improved API and state, numerous new components and chart types, and so much more!

I'd want the opposite of "mute thread" on @bsky.app as a feature: "subscribe to thread" à la slacks "get reply notifications". Really useful when someone asks a good question and I'm interested in seeing the answers.

‘The problem is that LLMs inherently lack the virtue of laziness. Work costs nothing to an LLM. LLMs do not feel a need to optimize for their own (or anyone’s) future time, and will happily dump more and more onto a layercake of garbage. Left unchecked, LLMs will make systems larger, not better’

📊 Massive LayerChart update (6 months in the making…) Data-driven primitives, overhauled state (transform, brush, series, tooltip), 10+ new components (image, statistical, spatial), canvas improvements, chart export (png, svg), new docs, and so much more! next.layerchart.com/docs/guides/...

I wanna say this out loud. A few months ago, I told Evan that @voidzero.dev should stop sponsoring me. I burned out, and I couldn't help Vite as before. But they decided to continue supporting me while I was down. And by doing so, they helped me get back on my feet sooner. Thank y'all ❤️

everyone is a PM now, whether you like it or not

saiu na Folha @folha.com

Something is moving regarding svelte custom renderers...help us bring this to the finish line! 🧡

my best code is written in a two-step process: 1. kludge a working prototype together, don’t worry about the code AT ALL. the point is understanding how the requirements function in reality 2. destroy the prototype completely. build the app for real using my better mental model

And here’s a startup offering influencing/propaganda services. Called it ;) www.404media.co/a16z-backed-...

i wrote about atproto and why it matters

the main thing that makes me uneasy about llms is the cultural backdrop of global war on knowledge. the war on knowledge isn’t new but now it’s cheered on from tech too. tools for thought pivoted to slot machines because that’s what people want. “how things work” is buried under opaque indirections

When a chatbot gets something wrong, it’s not because it made an error. It’s because on that roll of the dice, it happened to string together a group of words that, when read by a human, represents something false. But it was working entirely as designed. It was supposed to make a sentence & it did.

I expect that consumer-facing AI programs will continue to improve and they may become much more useful tools for everyday life in the future. But I think it was a disastrous mistake that today’s models were taught to be convincing before they were taught to be right.

One of my favorite all time articles on why leaders keep incentivizing making the wrong product choice is "The Preventable Problem Paradox" medium.com/@shreyashere...

Most times, talking about roles and responsibilities when teamwork is hard is the wrong move. When you’re outcome-driven, people can set aside their egos and collaborate. When it’s turf-driven, the best ideas can’t surface because people have to stay in their lanes.