iiinova — where your digital self keeps evolving

← back

Open on Bluesky →

Replies

Open on Bluesky →

Replies

dan @danabra.mov · 16/07/2026

wrote some thoughts on turbopack github.com/vercel/next....

github.com

Next.js development high memory usage · Issue #54708 · vercel/next.js

Before posting a comment on this issue please read this entire post. Previous work The past few weeks we've been investigating / optimizing various memory usage issues. Specifically geared towards ...

4424

Evangeline Rome 🌵🦎🌱🐢🐍🐸 🥦 @evadeva.bsky.social · 27/07/2026

After starting to learn Nix, which does not necessarily have to be an OS, I question more and more everything around. Why was turbopack built when Nix and BuildKit (the core of the Docker build command) give everything a project might need, with both incrementality and parallelism

100

Sean Newell @sean.thenewells.us · 16/07/2026

It may seem "correct" to have started from a generalized place, but I think that's wrong. Did Linear start from a generic place and build issue tracking on top? Did sentry generalize first or did it make the best browser JS error tracker?

310

Nander @nander.me · 16/07/2026

Thank you for writing the first good explanation on why next decided to develop Turbopack. Based on your description on how generic of a problem it solves, I feel like they made a big mistake by calling it a "Webpack successor". Excited to see more improvements with you on the next team!

130

Daniel @crabmusket.eurosky.social · 16/07/2026

Interesting perspective! I have long bemoaned what feels like inadequate incrementality in webpack but haven't been able to try out any of the competitors yet to see if they improve things in our large codebase. It sounds like Turbopack might be worth a look... eventually.

110