In our continuous pursuit of delivering the best developer experience, we've made a bold decision. We're dropping serverless support for Next.js. While this framework has its merits, we believe that simplicity and maintainability are paramount for us as a bootstrapped company. In this blog post, we'll explain the reasons behind our choice and shed light on our vision for the future.
One of the primary factors influencing our decision is the frequent and sometimes drastic changes introduced by Next.js. As a small company, keeping up with these changes and ensuring backward compatibility becomes increasingly challenging. It diverts our limited resources from focusing on delivering new features and improvements to our users.
Next.js, in particular, has gained significant momentum with its integration with Vercel. However, it also tends to write features that are tightly coupled with Vercel's infrastructure, making it difficult for us to compete head-on. Rather than engaging in an uphill battle, we'd rather focus on providing a unique value proposition and differentiate ourselves in other areas.
As developers ourselves, we value simplicity and the ability to have full control over our codebase. Frameworks often introduce a learning curve and require developers to adapt to their specific paradigms. We believe that achieving similar results can be done with a simple build file, reducing unnecessary complexity and dependencies.