Hacker News new | ask | show | jobs
by jordn 1128 days ago
Is this good/stable now? Worth switching from Pettier and eslint?
6 comments

“Pettier” whether a typo or not is hilarious and apt. And I’m not even being insulting. I love how petty it is. :)
How is it petty? It just formats code, instantly, without complaint. That's almost the opposite of petty
It fixates on trivial things. Petty. Pedantic. Again: I don’t think it’s a bad thing. It’s what I asked for.
How does a formatter fixate on anything? It formats. It has to have an opinion on formating.
It very opinionated. I don't know if that makes it petty though.
I’d say it’s the exact opposite, since it prevents petty arguments over formatting and style.
As long as it stays away from my code.
Use it since ~6 month. It is fast and works without bigger problems. But you have to learn and accept, that you can not modify much things like in prettier,. You have to use it as it is. That is the philosophy of their tools.

And after a while it is ok. You realize, that you spend before much time to modify everyhting, that is not really necesary.

I love it, I hadn't realized how much time I waste formatting my code until I turned on prettier autoformat in my repo.
3 years of using prettier and I still curse it daily for not letting me have more than 1 empty line to delineate related sections of code in large files for readability.
Add `// -----------------` in between blocks to work around this issue, and IMO provide much better delineation of content blocks e.g. imports vs definitions.

I do miss C#'s use of macros to allow defining arbitrary blocks that can be named and folded though.

In Jetbrains Webstorm you can create foldable regions. Happy customer.

https://www.jetbrains.com/help/webstorm/working-with-source-...

It is quite stable at the moment. I would still recommend taking a close look at the changes that Rome suggests, especially for large codebases: I think that some bugs are still expected.

The LSP (VSCode extension) is less stable at the moment.

The tooling itself is in relatively good shape in my usage, although the VS Code extension currently has a number of rough edges (frequent crashes, etc.).

It’s worth a try, but wouldn’t necessarily recommend ‘switching’ wholesale at the moment.

It links against a more recent glibc than Amazon Linux supports, so in my case it’s not ready for usage on EC2 hosted CI machines.
I suppose it’s “JS-stable”, given it is version 12, cutting 2 majors in 6 months.