4 ms·
It's hard to take Vercel at face value these days with all of these improvements and announcements. Are we supposed to - in hindsight - understand that odd vers
by thinkingkong 3y ago
It's hard to take Vercel at face value these days with all of these improvements and announcements. Are we supposed to - in hindsight - understand that odd version numbers of their codebase were really just unstable releases all along? The app server implementation wasn't really meant to be used because it was an experimental release?
I'm having a difficult time not being salty about this entire situation. There are basic production requirements that haven't been addressed for years because their hosting platform provides it. You don't like the way they do logging? Sounds like you need an attitude adjustment.
- JCharante 3y agoI read the release notes but don’t understand what you’re talking about re: app router. They mentioned that they’re still supporting app router and pages router.
- leerob 3y agoCorrect, the Pages Router is very much still supported with new improvements being made. The performance improvements in this post apply there. The same APIs and features included in Next.js 1.0 still work today with the Pages Router.
- ervine 3y agoPlease take this seriously: stop advising in github issues to switch to App router as a solution to bugs in page router. It's not an option for large next.js projects, and certainly does not convey what you're saying here.
- leerob 3y agoCan you be more specific on the issue? It’s possible there’s a reason why App Router was recommended in this case.
- boredtofears 3y agoI stopped paying attention when someone recently told me that everyone uses nextjs because “nextjs is meta right now”. Mind you this person has been a developer for about 3 years (not that there’s anything wrong with that but it gives you an idea of whose buying into this stuff) Vercels devrel is by far the best thing that they do, miles ahead of their engineering.
- tomjakubowski 3y agowell to me part of the reason to identify "the meta" is not to go along with it, but so you can develop tactics to counter it -- but maybe not everyone thinks that way Really though, it's not true that "everyone is using nextjs", so it's not "the meta" anyhow. I think most developers can safely ignore it
- boredtofears 3y agoI think anyone who says everyone uses X now exists in some kind of bubble when it comes to technology. I don't want to counter their point just for the sake of countering it but if a person's only supporting argument for using a tool is "everyone uses it" there isn't much of an argument to be had in the first place.
- johnfn 3y agoSo you stopped using a product because a junior engineer liked it? That doesn't strike me as the best rationale to make a decision.
- boredtofears 3y agoSo you start using a product just because other people tell you they are popular? That doesn't strike me as the best rationale to make a decision.
- bentruyman 3y agoThat's not the argument being made. Nobody said that.