An interesting trend over the past few years has been how many of the popular static site generators and frameworks we rely on are tied to a company that aims to monetize usage of that tool (to be clear, I am not judging this – just noting its rise). In Jamstack, I feel this initially started with Gatsby but nowadays includes Next.js, Astro, Remix and Fresh. While the framework is open source, the monetization is often tied to services that deeply integrate with framework features on day one.
While they aren't owned by a company, tools like Eleventy and SvelteKit (part of Svelte) have development fully funded by Netlify and Vercel respectively. It's worth noting that this model differs significantly as, in practice, features of each are not tied to specific offerings from the service that funds them.
|
|
|
Demystifying the New Gatsby Framework
Gatsby 4 came out in October 2021 with a lot of new features. This post digs into the major ones like deferred static generation, server-side rendering and build time optimizations. It also looks at how this integrates with Gatsby Cloud, and briefly how Gatsby 4 stacks up against Next.js.
Juan Diego Rodríguez
|
|
Deno's Fresh Uses Server-Side Rendering for Faster Apps
This takes a deeper look into Fresh (the new SSR-focused application framework for and by Deno), discussing it with Deno software engineer Luca Casonato. He notes a key differentiator is that Fresh is designed for running on the edge.
Loraine Lawson
|
|
✂︎ Tools, Resources & More...
|
|
|
Pre-Rendering and Data Fetching Strategies in Next.js
A good introduction to rendering options in Next.js, especially static rendering and ISR, and how to fetch data for them. I quibble with putting SSR under pre-rendering but it’s not central to the article.
Ifeoma Imoh
|
|
