<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nextjs on Blog</title><link>https://blog.rickwaterman.com/tags/nextjs/</link><description>Recent content in Nextjs on Blog</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 24 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.rickwaterman.com/tags/nextjs/index.xml" rel="self" type="application/rss+xml"/><item><title>Vercel Is Great for Frontend Teams</title><link>https://blog.rickwaterman.com/posts/vercel-is-great-for-frontend-teams/</link><pubDate>Tue, 24 Feb 2026 00:00:00 +0000</pubDate><guid>https://blog.rickwaterman.com/posts/vercel-is-great-for-frontend-teams/</guid><description>Vercel&amp;rsquo;s developer experience is the best in the business, and for a frontend team without cloud depth it is the right call. But if your organization already has AWS CDK or Terraform specialization, you are paying a markup on Lambda and CloudFront for an abstraction you do not need, with spend controls that lag, private networking behind an Enterprise contract, and a self-hosting story that has finally caught up.</description></item></channel></rss>