Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

While porting to Rust has been a trend, as Prettier runs on every save, the speed boosts will be significant. I'll be trying out Biome soon. Congrats to the Biome project!


I have never noticed any lag from Prettier running on single files. The perf starts to matter with whole-repo format passes.

For interactive use we really should be using long-running, warmed up, processes too, where the start time of Node is irrelevant. Ideally type-checking, linting, highlighting and formatting would run in one language service doing incremental parsing and updates to a shared AST on every keystroke.


> Ideally type-checking, linting, highlighting and formatting would run in one language service doing incremental parsing and updates to a shared AST on every keystroke.

I think this is the reason Biome (originally called Rome) started. Rome's vision was a shared toolchain to yield better performance and to fix config hell.


This effort reflects the excitement in the Python community around `ruff`. Excited to see efficiency and speed gains with a wide impact.


I recommend using the lint-staged tool so Prettier only runs on every save on changed files. It makes a huge difference on large projects.


Biome is also working on a feature that only formats changed files. See the associated PR [0] for more details.

[0] https://github.com/biomejs/biome/pull/753


Tangental but for anyone using lint staged + typescript, I recommend tsc-files[1].

[1]: https://github.com/gustavopch/tsc-files




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: