Edit: There's some more discussion about Turbopack at https://news.ycombinator.com/item?id=33333695.
Looks like they launched a webpack alternative called Turbopack today:
> Next.js 13 includes Turbopack, the new Rust-based successor to Webpack.
Looks like they launched a webpack alternative called Turbopack today:
> Next.js 13 includes Turbopack, the new Rust-based successor to Webpack.
It always amazed me that such a big project can just live without docs.
an excuse not to write docs, ever
it's endemic in the majority of companies I've seen in the last 10 years
hopefully tooling (eg. docs.rs mostly automatically generated and pleasant to use) will help in the long term
One recent offering I enjoyed working with was esbuild, as I could use it's CLI as part of my existing build system incrementally instead of planning my whole system around it.
1. Does code written a particular way?
2. Does it need to be configured?
3. Does it conflict with other tooling?
4. Does it have limitations that are too restrictive?
5. Does it cause bugs/issues that are difficult to resolve?
The ideal tool just does its thing, doesn't need any code written or configuration, works no matter what other tooling you're using, has no limitations, and will never itself cause a bug.
That might not be realistic to do 100%, but I think it's what all tools should be aiming for.
How many apps are dealing with 3,000+ modules?