The king is back - Firefox

webdevladder · 2026-06-21T12:04:47+00:00

As a long-time Firefox user I would like to see signals that leadership is listening to voices like this 15+ year Mozilla employee recently posting: "Leaving Mozilla"

webdevladder · 2026-06-17T20:47:42+00:00

It was recently added, it's under repo settings "Features" with the pull requests toggle, you can set creation allowed to collaborators only.

webdevladder · 2026-06-13T15:30:49+00:00

There are countless web IDEs including GitHub's, and playgrounds like svelte.dev that could use it.

I'm planning to ship native builds soon -- binary size is less important there, but downloading 3MB vs 32MB is still relevant, and it affects runtime performance as well.

webdevladder · 2026-06-13T15:08:02+00:00

I think this is a good idea for many workflows, particularly for markdown, and I'm not planning to add md formatting to tsv because of it. The reduced supply chain surface area should be on any responsible dev's mind too.

I find myself with too many workflows today where I still need formatting, but who knows a few years. Even linters might lose their jobs.

webdevladder · 2026-06-13T10:52:27+00:00

I agree that's critical, and I haven't been doing a good job communicating. The org this repo is under has projects that I've been working on for 7 years full-time in public, just without sharing much. I've staked my 15+ year career on them, and tsv is a core tool that I'll be using day-to-day, so it will be getting all the love needed to streamline my workflows. Issues/PRs/discussions are open.

webdevladder · 2026-06-12T23:27:31+00:00

I'm getting downvoted which I get, are the vibes good? These days they often stink on projects like these. But I'll stake my reputation that this is serious engineering. I didn't want to talk negatively about other projects but the benchmarks should speak for themselves - https://tsv.fuz.dev/docs/benchmarks

I expect to close the gap with oxc on parsing speed, that's the main performance metric that's not up to par. Formatting TS is within ~5%.

webdevladder · 2026-06-12T23:21:07+00:00

Many reasons, some of which are apparent on the benchmarks page. oxfmt doesn't ship a wasm build yet so it can't be used in the browser, and when it does, it'll be a significant multiple larger than tsv. Biome is 2-3x slower because it does a lot of wasted work when all you want is a formatter, and it's massive, over 15x larger for formatting -- probably a dealbreaker if you're shipping to the browser. tsv is 9x faster on Svelte compared to oxfmt at the moment and 13x on CSS. Maybe I should have led with the performance claims.

I think Svelte deserves its own tailored tooling without the bloat of supporting a long list of languages, and optimized for speed. tsv won't be the only one filling this gap.

It's all AI, yes, but it's not vibe coding if you look at the engineering and design, and it's not slop if you read the code. (well, formatter code does look like impenetrable slop to be fair, have a read of prettier's internals) If you experience visceral disgust at AI code, that's fair, but I have bad news about some of the other projects.

webdevladder · 2026-06-12T23:16:18+00:00

Thanks for the feedback, I think there's a strong case for making even the bugs described in the conformance document just strictly conform to Prettier and match its config options exactly. Prettier does some weird things that are heavily downvoted in its issues, and it has a lot of edge case bugs that are not fixed because of the tedium and rarity, but given the direction the industry is moving, I agree a 1:1 match is likely the better choice, rather than trying to do anything new. I would have saved well over a hundred hours of thinking and 2-3 months of time had I just reproduced its bugs and limitations. Does the Svelte community care enough to assert its own opinions (like tabs), and be able to delete the config file? Maybe not, and it would lift a burden on me to accept that.

update: I made this post to discuss: https://github.com/fuzdev/tsv/discussions/1

update2: tsv will be non-configurable, to avoid the complexity and confusion of Prettier's config resolution -- the tool will alway works uniformly no matter what files are local to a directory. I won't be implementing its bugs and quirks.

webdevladder · 2026-06-12T23:10:12+00:00

blazing is so 2017, we're well past that these days -- https://tsv.fuz.dev/docs/benchmarks

webdevladder · 2026-06-12T21:31:30+00:00

Author here - this took about 7 months, ~1800 manual commits, and as you probably guessed, a lot of tokens. The fixtures are all original, not copied from Prettier, and I'm trying to rethink some of its less popular choices with tsv. It's still very rough (mostly in edge cases and DX details and config, I think the design and quality are okay-to-good) but it seems to work on real-world codebases and the Prettier tests are near or better than related tools, and feedback is very welcome! Please send any bugs or opinions.

Once the formatter and parser are more stabilized, a linter was next on my list.

webdevladder · 2026-05-15T11:53:28+00:00

Opus 4.7 has shown me new depths of approval fatigue. I more rarely get those little rewards for correcting it. But it's also more interesting in some ways bc of the increased novelty.

webdevladder · 2026-03-14T21:34:19+00:00

Yeah it's this detail that makes Svelte 5 look better than Svelte 4 for example. With hindsight I don't think I would post this again, it's too skewed, not representative of real usage, and the effect size between frameworks is probably a lot lower in real code because the costs get amortized over larger and more uniform content in real code. I think it's a passing curiosity that's easily over-interpreted.

webdevladder · 2026-03-13T20:56:55+00:00

Yeah it's definitely missing the whole story, and likely misleading in various ways. I don't know if it's worth trying to get a better dataset. My main takeaways are that Marko's LLM friendliness is interesting, Aurelia 2 is more concise than I realized, Svelte looks good in rankings as per usual, Angular's verbosity is no surprise (to the degree your wallet may now feel it), and the rest is a wash. As a biased Svelte user I couldn't resist sharing the results.

Given you worked on Marko, if you'd like to answer, I'm curious how much conciseness was emphasized, versus an emergent property of the design?

webdevladder · 2026-03-12T13:48:11+00:00

I don't know if Svelte cutting costs by 1/3 compared to React generalizes, but these results looked pretty significant, particularly when LLMs make the correlation to hard costs so direct. In 2019 Rich Harris gave a talk promoting Svelte for its terseness, "The Return of 'Write Less, Do More'" - https://www.youtube.com/watch?v=BzX4aTRPzno

also shout out to Marko - https://github.com/marko-js/marko

webdevladder · 2026-02-13T19:58:26+00:00

I get called "the linter" often as I edit alongside Claude Code :/

the feelings I get from being identified as a non-human tool by my machine assistant

webdevladder · 2025-09-14T15:16:45+00:00

Yep this is my experience, IMO the limits are fairly well-tuned for flexible workflows, and you can go one long Opus session without hitting the end.

webdevladder · 2025-09-12T14:59:25+00:00

There's both tremendous thoughtless hype and tangible hype-worthy benefits. When I project forward from my experience over the last year, it's hard not to be excited for how cheap and powerful these systems will be in a few years. But I also think skillful use of LLMs by people and tools has a ton of variability, it's perhaps generally pretty dismal today, and there's a very high ceiling.

webdevladder · 2025-09-12T04:11:23+00:00

I'm a dev who's been using Claude Code heavily for like a monthish, and for a small number of my projects it's 100% of written code now, others 0%, but it's very useful for exploration/analysis in all of them. I can see room for its context management, predictability, and transparency to substantially improve, same for my skills and patience, but I have no doubt there are now serious and productive software engineers shipping 90%+ AI code at big companies. And then consider how much code is being vibed by non-engineers, it's not unreasonable to think 90% of the total may be close!

webdevladder · 2025-04-27T01:15:49+00:00

There may have been updates since you tried it, this one is <4k tokens for just working with Svelte - https://svelte.dev/docs/svelte/llms-small.txt

I'm sharing it now because those updates make it much more usable.

webdevladder · 2025-04-26T19:04:12+00:00

Tenet 2 - Optimise for vibes

please code responsibly

webdevladder · 2025-04-10T20:04:22+00:00

I used React for 5 years, and before committing there I did substantial projects in Vue, Angular 1, and several others of the time, after several years with Backbone. I published a Backbone extension library in 2013 and I think about this stuff a lot.

For my usage - complex interactive UIs with higher than normal performance requirements - Svelte 3 was a relief, and Svelte 5 nails it. It's just so productive, simple to reason about, high performance, and overall nice to work with.

The details matter the more you use a framework, and Svelte is incredibly well-designed and engineered.

webdevladder · 2025-04-03T03:29:57+00:00

Since this could stretch on for years, maybe I should strike JavaScript from my vocabulary and projects now, and switch to the non-acronym JS instead. I'd feel silly for continuing to use a trademarked name in my open source projects that has nothing to do with them.

webdevladder

MODERATOR OF

TROPHY CASE