Would be cool to use a Replit Bounty next time!
$20k bounty was claimed
11–20 of 345 posts
Re: $20k bounty was claimed
#12I'm looking through the docs, specifically the formatter stuff ( https://biomejs.dev/formatter ), and it feels like all the examples are backwards? Am I missing stuff?
That’s giving the diff between prettier (“correct”, yet red) and their implementation (green, yet arguably incorrect)
Re: $20k bounty was claimed
#13> One question you are probably wondering is why would the Prettier team fund another project!? In practice, Prettier has been the dominant code formatter for JavaScript and as a result of a lack of competition, there has been little incentive to push on performance and fix various edge cases. I was indeed wondering that but the answer doesn't really answer the question for me. Why not set a bounty to improve Prettie…
Maybe prettier will consume the biome work and offer it as an option for prettier going forward.
Re: $20k bounty was claimed
#14I'm looking through the docs, specifically the formatter stuff ( https://biomejs.dev/formatter ), and it feels like all the examples are backwards? Am I missing stuff?
What do you mean by "backwards"?
The "diff" appears to be backwards (it's subtracting what prettier would emit, and adding back the original).
Re: $20k bounty was claimed
#15While 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.
Re: $20k bounty was claimed
#16I'm still salty that all my eslint plugins decided to remove perfectly fine linters in lieu of Prettier. I find Prettier to be way too heavy handed and hard to reason about, and yet another tool that I never asked for...
Re: $20k bounty was claimed
#17I'm looking through the docs, specifically the formatter stuff ( https://biomejs.dev/formatter ), and it feels like all the examples are backwards? Am I missing stuff?
That’s giving the diff between prettier (“correct”, yet red) and their implementation (green, yet arguably incorrect)
It feels backwards to me from a purely linear time perspective, you have an input, transform it, diff would be the patch, to the desired output.
Re: $20k bounty was claimed
#18Speed is always welcome, but I just wish prettier was a little less opinionated. Specifically around line length, it will just not leave my formatting alone. I find prettier formatted code much less readable than unformatted code, and this isn't a problem I have with other code formatters like rustfmt.
Do you have any examples where prettier code is much less readable? I haven't really ran into that issue and have been very happy with prettier.
Re: $20k bounty was claimed
#19> One question you are probably wondering is why would the Prettier team fund another project!? In practice, Prettier has been the dominant code formatter for JavaScript and as a result of a lack of competition, there has been little incentive to push on performance and fix various edge cases. I was indeed wondering that but the answer doesn't really answer the question for me. Why not set a bounty to improve Prettie…
Different approaches with different constraints and less baggage can potentially discover areas of improvement that weren't otherwise visible in the original project. (i.e. they weren't locked into the "Prettier mindset", if such a thing exists)
Re: $20k bounty was claimed
#20> One question you are probably wondering is why would the Prettier team fund another project!? In practice, Prettier has been the dominant code formatter for JavaScript and as a result of a lack of competition, there has been little incentive to push on performance and fix various edge cases. I was indeed wondering that but the answer doesn't really answer the question for me. Why not set a bounty to improve Prettie…
Maybe they want an implementation to have an understanding of potential perf of a non-js solution, but know that it’d cost them more than $10k to have an employee do it. So instead you offer 10k, someone else offers 10k, and the final product is “owned” by a third party but your questions are answered.