DEV Community

Discussion on: How I massively improved my website performance by using the right tool for the job

Collapse
peerreynders profile image
peerreynders

and me moving from Next.js does not mean I think it's a terrible tool!

Taking on the migration from Next.js to 11ty was likely - significant.

Given the predominant values among those who already have adopted Next.js (e.g. for their blog) I suspect having to trade component centric development for templating (including JavaScript templates) would be a hard sell (***).

Astro could be seen as an alternative, capable of producing similar results without having to sacrifice the amenities of their chosen component framework.

(*** Though 11ty is an excellent choice for developers learning HTML/CSS/JS; allowing them to create static web sites with build-time JavaScript rather than immediately diving into a JavaScript heavy tool for client-side rendering.)

Collapse
whitep4nth3r profile image
Salma Alam-Naylor Author

Taking on the migration from Next.js to 11ty was likely - significant.

You're not wrong! I've got a blog post in the works that will explain my process... kind of an "Eleventy for Next.js developers" approach.

Astro is next on my list to look at for a project I'm working on!

Collapse
harshhhdev profile image
Harsh Singh

Yes! Astro has gained a lot of traction, and the things which you can do with it are absolutely nothing short of amazing. Considering most portfolios are static, astro is a perfect fit.

And for SSR, Nextjs has always been there but now there's Remix, giving developers more choice and freedom.

Collapse
peerreynders profile image
Thread Thread
harshhhdev profile image
Harsh Singh

Didn't know this existed.

But looking at it, from a first glance, it seems to be very early in development therefore (probably) lacking libraries and support that Next has, such as [NextAuth(next-auth.js.org/). There also isn't much support for stuff like custom middleware. But sure, it'll fulfill the needs of your CRUD todo app.