3 ms·
Why put another layer of complexity (and dependencies) on top of a solid and battle-tested library like React? Chances are that Next.js will be obsolete in 1-2
by sdevonoes 6y ago
Why put another layer of complexity (and dependencies) on top of a solid and battle-tested library like React? Chances are that Next.js will be obsolete in 1-2 years while React will be even better and maintained (probably React will die in 5 to 10 years, just like any other lib/framework).
- CraftThatBlock 6y agoI don't think you understand the usage of Next if you think it will be dead in 2 years. Application framework that gain good popularity stay alive for very long. Look at a lot of PHP frameworks for example. Next will be alive in 5 years
- dakiol 6y agoHow can you compare a PHP framework like Laravel (that sits on top of a language) with a framework (Next) that sits on top of a library (React) that sits on top of a language (JS)? Next is not like Laravel.
- CraftThatBlock 6y agoLaravel uses Blade for rendering, while Next uses React. They are roughly comparable.
- prawnsalad 6y agoBlade is literally part of the laravel framework, it’s not a third party thing like react is to Next.
- ritchiea 6y agoI have 98% confidence Next will be alive in 2 years. In five years if this company's biggest technical problem is needing to refactor an older front end framework then I have absolutely succeeded in my job building version 1.0.