Maurizio Vacca’s Post

View profile for Maurizio Vacca, graphic

Senior Frontend Engineer presso 1000Farmacie

NextJS is the worst thing happened to the FE industry. Even if you compare it with something like Symfony, it's like day and night. Everything in NextJS is incredibly convoluted for little to no added benefit, user authentication relies on a 3rd party libraries (good luck in finding one that actually works) and authors clearly have no clue about how HTTP works. Documentation is missing or is incredibly poorly written, to the point that more often than not you end up looking for undocumented features on their issue page on Github. Also, are you using anything different from the last version available? Sorry, no documentation for you (which I'm not convinced is even a downside at this point, since you've to reverse engineer most things anyway). As a professional and someone who's been around for a while, I can't believe this "thing" is flagged as production ready and it's considered as one of the best FE framework available. We surely lowered our quality standards over the course of the years.

Did you say that the worst thing that happened to the FE industry is at the same time, considered one of the best FE frameworks available? 🙄 How come? Who considers it one of the best FE frameworks? Developers, right? Perhaps it is really one of the best FE frameworks available because it effectively resolves real-world issues for both developers and users. As a developer with over two decades of experience working on real projects, (ASP/PHP/LAMP/MERN), I believe your assessment is unfair. Next.js is actually one of the best things to happen in the web industry. Just thinking about how it helps to make the web faster, is enough for me to say that you are wrong. It might have some downsides for sure (nothing is perfect, right?), but a lot of people are working constantly on it to make it better.

Kristi Mita

Lead Front-End Software Engineer at NEON | Full-stack | React | React Native | NextJS | Angular | Ember | NodeJS | AWS

5mo

Disagree, they provide an auth library, plus you can build your own, or use any of the react auth libraries (client side), choice is yours. Documentation has some missing info for the new versions, but you can find it in the previous versions. Page loading time is greatly improved with server components, no need for using third party libraries to manage global state most of the time. These two are enought for a react dev to use it. If you had been using react for the last years, you know redux is a nightmare, context not so good on large projects. Not to mention the Vercel infrastructure for hosting your app. Tons of features our of the box, no pipeline needed, feature flags support, firewall, analytics, app logs etc. It's not cheap but worths the money.

Milton Ivan García López

Software Engineer | Javascript | React Native | Vue.js | React | TypeScript | Next.js | Node.js | Designer | UI/UX

5mo

I can't believe you call yourself a senior and go around denigrating an evosystem that has contributed so much to the community. If you don't understand it doesn't mean it sucks. And here I give you examples of big companies that use nextjs. OpenIA Netflix Twitch Github Uber Nike Spotify If it's so bad why use it? Argue that

John Robert McCann

Software Engineer at Tablet Hotels | Building Accessible, Scalable, and Documented Web Apps

5mo

You keep saying that there is no documentation for previous versions, but the documentation for previous versions is found on GitHub https://github.com/vercel/next.js/tree/v12.3.4/docs

Oussama Boughizene

Full Stack developer at Critical TechWorks | BMW Group

5mo

It's not bad, but it's definitely overhyped and heavily marketed. The fact that Vercel's VP responded to you speaks volumes about how much they care about their image. I've never seen this level of attention from any other mainstream framework.

Vishesh Dugar

SDE @ION || 2x AWS Certified || MERN Stack || Flutter || @LeetCode 700+

5mo

I am familiar with rage-quitting. Might be a skill issue, or might not. But public opinion (as demonstrated by the comments section) doesn’t agree with you. Personally, i never had the need of next.js and didn’t use it so can’t comment on it.

Lee Robinson

VP of Product at Vercel

5mo

Hey Maurizio, I'm sorry to hear it feels difficult. - For authentication, you don't need to use a third-party library. If you would like to see an example with just HTTP, I have a tutorial / example that shows a simple cookie-based auth: https://www.youtube.com/watch?v=DJvM2lSPn6w - Can you share more about the specific things you were looking for in the documentation that weren't there? Happy to get those added. We do keep version history at the bottom of some docs pages, if there are relevant notes to mention, and also keep upgrade guides and codemods in the documentation when moving between versions. Hope this helps. Thanks for the feedback.

Ayush Singh ⚛

Accenture | Building GPT | AI | LLM | NextJs | Python | ReactJS | JavaScript | TypeScript

5mo

People don't like thing if they don't understand. I recommend you to eat some almond on daily basis.

James Mahy

Open to work 🍔 Seasoned Full stack engineer

5mo

Why are you comparing Next to Symphony they're not even designed to solve the same problems. Next is just a lightweight framework for React, that's it.

Like
Reply
Waleed Tahir

Crafting AI-integrated Websites 💻 that Elevate Business Ideas to Success. | 18 Y/O Full Stack Web Developer | MERN Stack | React | Next Js | Node Js | Angular js

5mo

Bro if you are getting any bug we can solve it together but please dont blame Next js for that now 😂 Vercel Please help this guy

See more comments

To view or add a comment, sign in

Explore topics