From 86844ef93dd0189e4544d37fe469bfdc589df8f3 Mon Sep 17 00:00:00 2001 From: Mikkel Svartveit Date: Wed, 13 Dec 2023 23:23:56 -0800 Subject: [PATCH] Add tweet to blog post --- src/content/blog/nextjs-14-is-not-ready.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/content/blog/nextjs-14-is-not-ready.md b/src/content/blog/nextjs-14-is-not-ready.md index 82b1f26..ea60c50 100644 --- a/src/content/blog/nextjs-14-is-not-ready.md +++ b/src/content/blog/nextjs-14-is-not-ready.md @@ -53,3 +53,7 @@ I have admittedly not checked out this tutorial. It’s most likely great. Still Despite this year’s somewhat disappointing update, Next.js is clearly evolving. Along with React Server Components, I can imagine a future where Next.js is an even stronger contender in the current realm of web development tools. While SvelteKit is still my go-to for the smoothest developer experience, I’m excited for what’s in line for Next. New developments in the React ecosystems are just too big to ignore. Once Turbopack is ready, partial prerendering is more widely available, and the server component paradigm settles a bit, Next.js offers a compelling argument for revisiting the world of React. Until then, I am sticking with Svelte. + +
+ +