[HN Gopher] Next.js is the most frustrating, opinionated mess I'...
___________________________________________________________________
Next.js is the most frustrating, opinionated mess I've ever had to
deal with
Author : bundie
Score : 23 points
Date : 2023-06-25 20:19 UTC (2 hours ago)
(HTM) web link (twitter.com)
(TXT) w3m dump (twitter.com)
| beezlewax wrote:
| This is a pretty low effort post. I don't use next much but I've
| played around with it.
|
| They messed up launching the app structure when it wasn't fully
| functional but I'm under no obligation to use it.
|
| It seemed to me when I did check it out that'd I'd probably want
| to stick with the more battle tested next style though.
| silverbax88 wrote:
| When I learned React after two decades of web programming with
| C#, JS and even older tech like ASP or JSP, it was an effort.
| React has a LOT of stupid in it, but it's still got some great
| features.
|
| Next.js fixes quite a few of the initial problems with using
| React even though there's still some stupid and even some new
| stupid introduced.
|
| I'm definitely building in Next.js now, not vanilla React.
|
| I think the problem is that SPAs are limited in use, but a lot of
| devs ONLY build SPAs and that creates a mess. Before Next.js, if
| I was building anything _other_ than an SPA, I 'd really have to
| wrestle with if I should build it in MVC or React...because it
| was a _lot_ more trouble in React to do it well. But I don 't
| have that problem with Next.js.
|
| I suspect that people struggling to work with Next.js from React
| don't have the experience of web app development before React
| existed, so suddenly they are faced with the same learning curve
| of people who had to figure out React when they were used to
| full-stack development.
| YetAnotherNick wrote:
| In fact it's quite opposite. App directory has lot of quirks
| that I learnt building in it after experience in react. Just
| after using it for two weeks I found there is no global 404,
| you can't use things like window and document, server
| components are close to useless where you can't even read
| cookies in server component(you can't read it in client
| component in server as well even though next has it), it's
| better to stay away of API routes, you can't use environment
| variables in prod but you could use in dev, you could easily
| trip yourself by using 'next/router' instead of
| 'next/navigation' etc.
| CosmicShadow wrote:
| I've been using it for years and it's something where you need to
| learn what it's for and how to use those parts properly (static
| vs server), but once you get that figured out it's pretty quick
| to do a lot of things well. I haven't tried the new app directory
| or server components yet to make things even faster as why break
| something that works good enough. I think to take advantage of
| them you have to really understand the advantages and weaknesses
| of what came before them and why you would want to do the new
| thing.
|
| Forcing NextJs to do something it's not meant to do (which I
| spent months doing last year) is not fun and leads to frustrating
| and wheel spinning, but doing what it's supposed to do I feel
| like I can spin up something so fast and easily and deploy to
| Vercel quickly and have a full web app in no time that has
| amazing speed. I wish they had a tier above pro, but below
| enterprise though for those who make a living off using it, but
| can't justify $1000/month just so someone will answer a phone
| call or email as to why their platform is failing with no errors
| and now you can't earn a living.
___________________________________________________________________
(page generated 2023-06-25 23:02 UTC)