4 ms·
Next.js is extremely limited compared to Rails, so you're still not comparing apples to apples. Add to next.js a librarydatabase access, background jobs, csrf a
by midrus 5y ago
Next.js is extremely limited compared to Rails, so you're still not comparing apples to apples. Add to next.js a librarydatabase access, background jobs, csrf and related security stuff, migrations, server side caching of data, *validation*, email sending, email receiving, testing, and I could spend an entire day listing things Rails gives you that Next.js won't give you. Web development is not just rendering html, unless you're building just landing pages, there's a lot more going on.
- jerrygoyal 5y agoNot next.js, but nest.js is a better opponent for rails
- midrus 5y agoHow to do an unique validation in a full stack framework (Laravel): https://laravel.com/docs/8.x/validation#rule-unique https://laravel.com/docs/8.x/validation#rule-unique How to do a unique validation in nestjs (didn't find it in the docs, so had to Google it): https://gist.github.com/zarv1k/3ce359af1a3b2a7f1d99b4f66a17f1bc https://gist.github.com/zarv1k/3ce359af1a3b2a7f1d99b4f66a17f... No thanks. This is still apples vs molecules to mount your own apples.
- andyfleming 5y agoThe commenter you replied to did provide a fair correction as far as the right layer to be comparing. They didn't specifically suggest that Nest.js (started in 2017) is as mature as Rails (created in 2004) or Laravel (created in 2011).
- midrus 5y ago>Not next.js, but nest.js is a better opponent for rails What part of that comment says anything about layers or maturity? By that rule I could compare rails to express and say they are about the same.