Man this took me on a wild ride once.
Environment variables stopped working: https://github.com/vercel/next.js/issues/53367
The <Image> component stopped working: https://github.com/vercel/next.js/issues/53715
(Both of these were, afaik, exclusive to self-hosting, rather than running on Vercel)
It accomplishes nothing and obscures the sign posts that would help the next developer that encounters the same issue.
Funny, trying to open the post's link (https://nextjs.org/blog/next-14) with JS disabled, it renders a "beautiful" blank page.
I recently tried to rebuild my Jekyll blog with Nextjs. This felt way too hard for something that was basically a nunch of static pages, but I pushed through and ignored that feeling.
This, though? It's confirmation that my type of use case wasn't a priority for this library.
This is gold level comedy. I am not sure how no one in the tech industry is seeing this.
The default bundle size is also nowhere near 1MB. Next 13 and server components entire point is to reduce the bundle size by not shipping JS that is only ever called on the server.
I.e everything that’s done here[1]
Oh no. You can’t. You need to set “images.unoptimized = true” and be happy about it if you’re not using a cloud image service.
https://nextjs.org/docs/app/api-reference/components/image#l...
https://vercel.com/blog/vercel-welcomes-rich-harris-creator-...
From the same link above: >> "Joining Vercel enables Rich to work on Svelte full-time, giving the project its first dedicated contributor. The governance of Svelte does not and will not change – it's still the same independent, open-source project and community. With Vercel's backing, Svelte can get even more ambitious."
It allows you to build full-SSR apps with Tailwind and JSX, has support for SQLite and HTMX, and is in general a great return to how web dev used to be / should be.
"and why"?! Staggering levels of negligence there.
Fuck 1MB of JS to render a static HTML page.
Fuck the image component, and not being able to optimise your image unless you use their cloud service for no reason at all.
Fuck spending 3 hours working out why you’re not able to use relative image paths in MDX files and have to shove everything in /public.
Fuck fighting five layers of configuration and bundlers and libraries and GitHub issues to try and load a WASM file without having the whole thing break.
Fuck some half-assed play at being a static site generator and a backend framework, that conveniently works best on your overpriced cloud service.
Use Astro. It’s what next.js pretends to be
https://astro.build/