3 ms·
I don't see a contradiction. Were ESBuild already written in Rust, Rust would be the present of JS infrastructure. The author hopes it merely to be the future.
by nine_k 4y ago
I don't see a contradiction. Were ESBuild already written in Rust, Rust would be the present of JS infrastructure. The author hopes it merely to be the future.
- kekkidy 4y ago[dead]
- streptomycin 4y agoYeah but that future is probably a long ways off, if it ever comes at all. Currently ESBuild has 5x as many npm installs as Rome and SWC combined, and the gap doesn't seem to be shrinking https://npmtrends.com/@swc/core-vs-esbuild-vs-rome https://npmtrends.com/@swc/core-vs-esbuild-vs-rome
- Patrickmi 4y ago[dead]
- acemarke 4y agoFWIW, that doesn't take into account that Next actually has its own wrapper around SWC, and also vendors it. I think it's probably the largest consumer of SWC: - https://github.com/vercel/next.js/tree/canary/packages/next-swc https://github.com/vercel/next.js/tree/canary/packages/next-... Those add up pretty fast: - https://npmtrends.com/@next/swc-linux-x64-gnu-vs-@next/swc-win32-x64-msvc-vs-@swc/core-vs-esbuild-vs-rome https://npmtrends.com/@next/swc-linux-x64-gnu-vs-@next/swc-w...