Friendship ended with Next, now Astro is my best friend.
Next.js 15.1 is unusable outside of Vercel
71–80 of 113 posts
Re: Next.js 15.1 is unusable outside of Vercel
#72Earlier quoted context omitted.
How was Vercel able to frog-boil normal React users with vendor lock-in? React was supposed to be Meta's baby and open source was supposed to defeat vendor lock-in.
because they pushed shiny new features that are reaaaallly good for a certain set of commercial users (think webshops, where time to first contentful paint equals time to money) and the tech is not bad, it's just meh (immature and a bit misguided) after all by flipping the whole thing upside down, defaulting to server-side, a lot of previously hard problems became easy (the usual glueing of different APIs - user, CMS…
Can you suggest alternatives? I've used Next and Svelte[kit] in prod and have been very unhappy with both.
Re: Next.js 15.1 is unusable outside of Vercel
#73Earlier quoted context omitted.
I moved away from Next.js, and switched to Astro. Originally I just wanted to go back to basics, but didn't want to bother with having to set up all my routes, templating, serving static assets, build tasks. Astro just handles all that, and it's SSR by default. I also feel that Astro uses React/Vue as it was intended, as an interactive layer on top of HTML. It also made me realize how little I needed JS frameworks to…
I tried various astro sites, and as a user, a few things keep bugging me. - Visit their docs https://docs.astro.build/en/basics/astro-pages/ - Click `Routes` in the navigation Now: 1. There's a flicker in the content where the sidebar moves on the left 2. The title displays `docs.astro.build` for a split second before it says "Routing | Docs" Especially the second is quite annoying. I see it in every Astro site.
That seems to be mostly because of the way they've implemented their docs. It's definitely not something I have with my own sites.
The flicker seems to be because the collapsible nav items are done on the client, and closed by default.
I'm not sure where the title issues are coming from.
Re: Next.js 15.1 is unusable outside of Vercel
#74I still dont understand the lie, that its difficult to host next.js. I am hosting several nextjs apps for my day job. We just put them in a docker and throw them on the server, whats the confusion?
The confusion is that there are plenty of front-end developers that have no clue what they are doing, and then blame it on the tool. Believe me, I interview plenty of front-end developers each month. The main problem is that building a website is very different than programming a web application. As a senior software engineer with a Masters degree in CS, NextJS works great for me. Another poster here claims an drops…
Dude, I explicitly replied that I pinpointed it to Next. The moment I removed the Image tag and replaced it with a regular , it resolved itself. I didn’t even say I was using three, did I?
Re: Next.js 15.1 is unusable outside of Vercel
#75Vercel recently spammed my work email with news about a local talk/webinar. On the one hand that's useful info (I'm a front-ender after all). On the other hand it's freaking creepy. I've been in this job three months and hadn't signed up to anything Next/Vercel from my work email. That means (at best) they scraped me from LinkedIn and guessed at my email address. At worst I've left a data trail that someone's compiled me into a few categories and Vercel bought me in a bundle. Clever growth hacking, give that employee a bonus, but jeez is it why I hate parts of the interwebs these days.
Re: Next.js 15.1 is unusable outside of Vercel
#76Earlier quoted context omitted.
The confusion is that there are plenty of front-end developers that have no clue what they are doing, and then blame it on the tool. Believe me, I interview plenty of front-end developers each month. The main problem is that building a website is very different than programming a web application. As a senior software engineer with a Masters degree in CS, NextJS works great for me. Another poster here claims an drops…
Dude, I explicitly replied that I pinpointed it to Next. The moment I removed the Image tag and replaced it with a regular , it resolved itself. I didn’t even say I was using three, did I?
My above text was written before you replied to my other message.
And besides, just because using instead of doesn't imply that the actual issue was in , it might also be in another part and triggered it. As I told you, as long as you don't pinpoint the problem, you can't say where the problem lies.
Maybe your definition of pinpointing is different than mine.
Re: Next.js 15.1 is unusable outside of Vercel
#77Earlier quoted context omitted.
because they pushed shiny new features that are reaaaallly good for a certain set of commercial users (think webshops, where time to first contentful paint equals time to money) and the tech is not bad, it's just meh (immature and a bit misguided) after all by flipping the whole thing upside down, defaulting to server-side, a lot of previously hard problems became easy (the usual glueing of different APIs - user, CMS…
Can you suggest alternatives? I've used Next and Svelte[kit] in prod and have been very unhappy with both.
Might not hurt to look into React Router 7 Framework mode. I've started using it in one of my side projects and loving it so far.
Re: Next.js 15.1 is unusable outside of Vercel
#78For Frontend development, my recommendation is Vitejs. For content-heavy sites, try Astrojs!
I've never opted for Nextjs for any client, but have experienced having to get rid of Nextjs from client projects.
Re: Next.js 15.1 is unusable outside of Vercel
#79For Frontend development, my recommendation is Vitejs. For content-heavy sites, try Astrojs! I've never opted for Nextjs for any client, but have experienced having to get rid of Nextjs from client projects.
its crazy how perspective shifted that maybe 4 years ago that next js is preferred choice but here we are
Re: Next.js 15.1 is unusable outside of Vercel
#80Don’t ever use Next. Terrible developer experience, vendor lock in, weird undocumented conventions that make building anything other than some kind of B2B SaaS CRUD site full of undocumented foot guns. My favorite thing I’ve encountered is the Next tag somehow dropping the FPS on a webgl scene on the same page to 2 FPS.
How was Vercel able to frog-boil normal React users with vendor lock-in? React was supposed to be Meta's baby and open source was supposed to defeat vendor lock-in.
They exert immense influence over the React ecosystem, even its documentation.
Example:
https://react.dev/learn/creating-a-react-app
If you are new to React and just figuring out how to get it running, you will likely end up on this page. The first recommendation is Next.js.
The real best way for a beginner to start is IMO Vite. Comes with everything you need to get started and lets you choose what to do next. Curiously, the link to Vite only appears at the very bottom of the page and is implied to be only for those not already served by other options. Wink wink nudge nudge.