14 ms·
I will keep using Next.js, because that is what SaaS vendors support on their extension SDKs, and I have better things to do than build an ecosystem. Alternati
by pjmlp 1y ago
I will keep using Next.js, because that is what SaaS vendors support on their extension SDKs, and I have better things to do than build an ecosystem.
Alternatives are great for those without these kinds of constraints.
In which case, I rather use traditional Java and .NET frameworks with minimal JavaScript, if at all.
- mfru 1y agoHow do you deal with the horrendously slow on-the-fly compile times in dev mode? I wonder how anyone gets any work done when they have to wait 10 seconds on every page load on a M3 Macbook Air
- pjmlp 1y agoTurbopack helps, ever used C, C++, Rust, Scala, Swift in large scale projects? Back in 1999 - 2001, every time I wanted to do a make clean; make all in a C based product (actuall TCL with lots of C extensions), it took at least one hour build time.
- mfru 1y agoI guess I am spoiled by Java and Angular then. Both compile for the same time as a page load in Next dev mode, but then everything is smooth sailing (and Angular also does hot-reloading well)