3 ms·
Not sure why ESBuild is included since it's in Go and there's no working link to learn more about a hypothetical speedup over ESBuild. Having used both swc-nod
by vlovich123 4y ago
Not sure why ESBuild is included since it's in Go and there's no working link to learn more about a hypothetical speedup over ESBuild.
Having used both swc-node and Rome after having used ts-node and prettier/eslint. SWC is a lot more finicky than ts-node (which itself is quite finicky) with a lot less documentation when something goes wrong (& often just looking at your setup sideways can cause it to stop working in surprising ways). Certainly I enjoy using ESBuild and I doubt swc could fill that niche right now (too immature I think). Rome is "special" in that it has none of the depth of eslint's TypeScript linting support and has very strange opinionated defaults that make no sense with limited configuration because the whole philosophy of that project is "just follow our rules without any configuration". Rome is to its word quite fast but given that it does a fraction of the linting eslint can do, it's hard to say whether that speedup will win out.
Special shout out to dprint. While it too has Rome's disease of limiting configurability, it does have a sensible amount of it and it is drastically faster than prettier. I will note though that one thing that still annoys me is that two identical ASTs will result in different output formats because the input formatting can affect the output (i.e. it tries to preserve input, particularly around line breaks). I understand the philosophy of it but I'm not sold if I'm trying to enforce a consistent style across the codebase.
- satvikpendem 4y agoThe Rome team ran out of funding and had layoffs, if you didn't know. I'm also a Rome user and it's sad to see.
- qudat 4y agoDo you have any resources online about this? I'm using Rome as well -- quite enjoying it -- but we are running into its limitations which this news does not instill confidence.
- conaclos 4y agoWhile that's true, the project attracted new core contributors. The development slowed down, but the project is still in active development. A new release is planned for this month.
- qudat 4y agoOh that's good to read! I'm pretty excited about rometools and desperately want to get out of this super pluggable linting world with a dozen+ eslint related packages. Everyone wants to use airbnb's style guide anyway, just make that the default with some minor overrides and I'm happy.
- satvikpendem 4y agoIt's on their Discord. While there is going to be a new release, the development definitely has slowed down. People on the Discord at least are thinking about whether a fork makes sense, since the Rome trademark is with the corporation and not the OSS project, if I understand correctly.
- satvikpendem 4y agohttps://discord.gg/rome https://discord.gg/rome for those interested
- johnnypangs 4y agoI would argue that SWC is more mature than esbuild as SWC is on a version 1+ release (the author on their site says that is “late stage beta” and vite still doesn’t use it for production builds), has been around for 2 years longer than esbuild (going by github histories) and is being made by more than one (very capable) person.
- vlovich123 4y ago¯\_(ツ)_/¯. Just relating my experience. I've found the ESBuild plugin ecosystem to be quite mature and blazingly fast. Any additional speedup of SWC wouldn't be felt as the startup overhead of npm to do `npm run build` dominates whatever time ESBuild spends.
- conaclos 4y agoESbuild seems more popular than SWC. Moreover, ESbuild has really good documentation and a great CHANGELOG. It is always a pleasure to read a new entry in its CHANGELOG. IN the other side, the changelog of SWC is too close to the code. This makes hard to understand what is added in a new version from the user perspective. I also chose ESbuild over SWC because ESbuild has no dependencies. SWC has more than 130 (transitive) dependencies [0]. [0] https://npmgraph.js.org/?q=swc https://npmgraph.js.org/?q=swc
- conaclos 4y ago> Rome is "special" in that it has none of the depth of eslint's TypeScript linting support and has very strange opinionated defaults that make no sense with limited configuration because the whole philosophy of that project is "just follow our rules without any configuration". This was true at the start of the project. They added many configurations asked by dev such as semicolons and indentation style. Any lint rule can also be disabled.