biome (web tooling ecosystem) initial thoughts: the configuration is annoying but dang is it fast.
i *want* to like it, but when a two line prettier config gets migrated to all this i have some questions. i'm pretty sure most if not all of these options are already default. are the defaults not guaranteed to be the same between versions? is the migration tool just a bit shit? who knows. i gotta find out before i commit to anything.
also, the default indentation style is tabs. why? i don't mind this, but it'd be nice if it was justified in the documentation. along with anything about formatting options for languages other than javascript?? why???
Quick and Dirty Linting, by @stoyan:

This post is another installment of the series dedicated to building sightread.org. Parts 1, 2, 3, 4, 5, 6. I've been using TypeScript (actually JSDoc + tsc --noEmit) as my linter for a while. Well, TBH, I didn't do it intentionally, it's just something Claude does outta the box. I saw some linting
Just a year ago, the first thing I did when returning to an old project was to make sure it had the latest Biome for code quality.
Nowadays, I seem to reach for a Spec-Engineer agent command/workflow first.
And then, ask the spec-engineer to plan how to get the latest #Biome in place 😆 😆 😆
[완벽한 린터를 기다리지 않기로 했다: ESLint V9 마이그레이션, 그리고 Biome 하이브리드 도입기
ESLint V9로의 마이그레이션과 Biome 하이브리드 도입 경험을 공유한 기사. ESLint V8 지원 종료에 따라 V9로 마이그레이션한 과정과 성능 문제 해결을 위해 Biome를 도입한 사례를 설명한다.