rich harris @rich-harris.dev · 16hit seems we caught the orange wave, which took me by surprise a bit. i didn't think anyone really cared about frameworks any more! warms the cockles news.ycombinator.com/item?id=4992... 3355
rich harris @rich-harris.dev · 11/07/2026this is a great piece, and i'm not just saying that because i'm quoted in it 414015
rich harris @rich-harris.dev · 02/07/2026lol it's so much simpler than that — the ALS error is happening in the browser. you need to opt in to remote functions. the only mystery here is why you're not seeing a warning in the terminal, I could have sworn we had that. Opened github.com/sveltejs/kit... 210
rich harris @rich-harris.dev · 20/06/2026The idea that Richard Harris, the MacArthur Park singer, was in the Inbetweeners movie has me cackling 030
rich harris @rich-harris.dev · 18/06/2026yeah, you can see it on MDN developer.mozilla.org/en-US/docs/W.... it looks like absolute garbage. amateur hour 130
rich harris @rich-harris.dev · 02/06/2026somehow got this on my first attempt, which is also my last attempt — not going to ruin this moment by trying again 1110
rich harris @rich-harris.dev · 01/06/2026it looks super cool! i wouldn't want to sacrifice the flexibility of using TypeScript to define stuff, but i can certainly imagine something like this 140
rich harris @rich-harris.dev · 30/05/2026the single biggest criticism svelte has received over the years is 'you can't have multiple components in a file'. so we fixed it! by making them unnecessary. with declaration tags (svelte.dev/docs/svelte/...), snippets/each blocks/etc can have their own state: svelte.dev/playground/a... 1120118
rich harris @rich-harris.dev · 23/05/2026not _exactly_ — we actually warn for a closing solidus on a non-void element, because that's where the ambiguity lies 030
rich harris @rich-harris.dev · 16/05/2026ran the Brooklyn Half today. little slower than two years ago, but to be fair the benchmark was running on older hardware this time. now to eat something really stupid 81130
rich harris @rich-harris.dev · 07/05/2026The post you linked above suggests that a data center uses less than 0.1% of the existing deficit. You could destroy every data center in the state and I'm not sure it would change a thing (except presumably make the state poorer, which probably _would_ reduce water usage) 100
rich harris @rich-harris.dev · 07/05/2026He claims that the evidence we have to date, while spotty, suggests that data centers do _not_ devalue nearby properties 100
rich harris @rich-harris.dev · 06/05/2026It's not just standards of course. Recent example: Chrome shipped an 'automatic workspaces' feature that no-one wanted, without outreach, that causes considerable (avoidable) inconvenience and confusion. The Vite plugin by which you use (or silence) this feature? Abandoned. 1231
rich harris @rich-harris.dev · 06/05/2026I personally more or less gave up on trying to engage with standards processes after this interaction, in which the quiet part was said out loud: Chrome is not beholden to other implementers, and no-one _other_ than implementers has any influence at all. So why bother? 4437
rich harris @rich-harris.dev · 23/04/2026actively incentivising larger dependency graphs is bad for the ecosystem 2792
rich harris @rich-harris.dev · 17/04/2026svelte is officially Enterprise Ready™. tell your CTO on linkedin www.thoughtworks.com/radar/langua... 919417
rich harris @rich-harris.dev · 13/04/2026me and the other non-car-perverts in the neighborhood group chat are doing our bit! unclear so far if we're outnumbered 100
rich harris @rich-harris.dev · 12/04/2026about to fly to london for @cityjsconf.bsky.social. you should come! unless you don't write javascript for a living in which case you probably shouldn't anyway here's a 20% off link ti.to/cityjsconf-l... 3506
rich harris @rich-harris.dev · 06/04/2026oh my god wouldn't normally dunk on someone for technical illiteracy but this moron just KEEPS DOUBLING DOWN 0180
rich harris @rich-harris.dev · 01/04/2026huh! this is the translation I get when I read in Firefox — much clunkier prose, but at least no howling inaccuracies. I wonder what underpowered model Chrome is using for this 020
rich harris @rich-harris.dev · 01/04/2026Beautiful work! I spotted one small thing - it says they will walk on the moon? 120
rich harris @rich-harris.dev · 17/03/2026wanted to just reply with this meme but it actually looks pretty neat 160
rich harris @rich-harris.dev · 14/03/2026Yeah it's arguably just a question of preference. I just know that if I saw this code my first instinct would be to remove the loading UI — given the types, how could {props.data} trigger the fallback? — and it would annoy me to realise that I had to look at every callsite to know if it was needed 230
rich harris @rich-harris.dev · 14/03/2026Interesting post! I disagree :) You say "if async is only discovered during side effects, it’s already too late", which is true. The solution is to update async stuff first, _then_ run side effects once resolved. Repeat until settled. So if I have something like this, and `slug` changes... 1130
rich harris @rich-harris.dev · 13/03/2026many such cases! Though this one wasn't quite as bad as the other day when I asked an agent to 'make the tests pass' and it did this 81083
rich harris @rich-harris.dev · 24/01/2026I just want to know which PM at google thought 'you know what people want when they've been at a restaurant for the last 45 minutes? An out of date photo of the menu that's directly in front of them, from which they've already ordered' 5772
rich harris @rich-harris.dev · 22/01/2026I imagine I would agree with this, but guess I'll never know... Gruber doesn't get to have an opinion on design as long as his site looks like this with no ability to zoom in 370
rich harris @rich-harris.dev · 13/12/20259th race done. Guess I'm running a marathon next year 😬 7960
rich harris @rich-harris.dev · 25/11/2025the AbortSignal approach feels correct. you can make it simpler with `getAbortSignal` (svelte.dev/docs/svelte/...): 0110
rich harris @rich-harris.dev · 21/11/2025you might think 'i'll just use a multipart parser'. the remix boys have a good one (github.com/mjackson/rem...). but it's not really a solution, because you can't validate inputs until you've got all the parts, which defeats the object. and it still buffers each file — no incremental processing 4100
rich harris @rich-harris.dev · 05/11/2025on behalf of those of us who can't vote here: thanks, nyc 71954
![Hey everyone, Rich from the Svelte team here. Coordinating all the moving parts for yesterday's launch (last few PRs, doc updates and redirects, CLI release, launch blog post...) turned out to be a bit of a slog so I'll confess I turned off my laptop and went for a beer as soon as it was done instead of sticking around to engage in HN threads and Reddit and so on.
Honestly, I didn't expect the release to generate much conversation at all. There's a lot less focus/interest in front-end frameworks generally these days, for obvious reasons, so I figured the median reaction would be 'oh, the Svelte team are still shipping? good for them' and not much more. It's a joy to see the conversation here whether it's from happy users, or people who prefer different things, or people who have fully outsourced the writing-the-code bit to LLMs and straight up don't care about the underlying tools any more.
Which I totally understand! As framework authors we're very persnickety about the details of the code, so we've been on the slower end of the LLM adoption curve, but even we're starting to delegate more of the work to agents. If you're prompting an app into existence it's natural not to care that much about the particulars. But a question I've seen several times here, and in the zeitgeist more generally — 'in a world of agents why should I care about Svelte vs React vs whatever?' — deserves an answer.
And it's this: your app will be _better_ if you use Svelte. Your JavaScript bundle will use fewer bytes, your server-side rendering will take fewer milliseconds, and your users will reap the benefits: faster, more efficient apps. For all that the agentic revolution has created a huge _quantity_ of software, the _quality_ of the average app stubbornly refuses to budge. If anything, software is becoming less reliable. I think we've all felt that. Using a framework that treats things like accessibility ... [truncated due to alt text limits]](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:anvvmj5rdxhzo26gmhkgshnn/bafkreiawj6dulbeb3ehcrm4eegbeegk6wx6jjxhxda5netdz7fjs5fuidu)
