Think twice before choosing your go-to framework in the AI era. Vibe-code, SaaS, framework, custom code, or no-code? You might be surprised what’s now best.
As an experienced developer, I would historically select my favorite OSS framework (only if it’s a good fit). But AI has changed the equation.
~ Vibe Code ~ (using AI to write the app)
Great for *fast* prototyping and for simple projects. You may even be able to launch simple production projects on it. But it can be dificult to maintain, and you’re likely to need to rewrite it from scratch when you want to refine/improve it.
~ SaaS & No-code ~ (Paying for online software)
You’re limited to features the company provides. If you need to add something custom, you may be out of luck. At least maintenance and updates tend to be done for you!
~ OSS Framework ~ (Drupal, WordPress, React, Laravel, etc)
You have full control over what you build and a community of people who understand your project’s architecture to ask for advice. Nice! Downside? That community may alter the software over time and you may need to invest non-trivial time into keeping your project up-to-date, even if you’re happy with it as-is. Additionally, you’re inheriting all of the framework’s technical debt & features that don’t apply to you.
~ Custom code ~ (raw code, no framework)
Code exactly what you need, update it on your own schedule. Sounds great but this requires significant time & expertise, especially in performance, security, accessibility, and UX.
=====
Where does AI change the equation most?
IMO, for highly experienced architects, it makes “custom code” the best choice more often where OSS Framework would previously be a no-brainer. Not by vibe-coding, but methodically using it to write individual functions, one at a time, more quickly and with fewer errors.
Seasoned architects know exactly what their application needs, how to secure it, how to improve performance, etc. And they know how to write and organize the code.
With this approach they can:
- write an application from scratch
- using their preferred languages’ most modern features
- with no historical technical debt
- upgrade only what they choose to, when they want to
- lower ongoing maintenance costs significantly
When are OSS frameworks are more appropriate? Usually, especially if the app will continuously be updated over time, and be worked on by many people.
But for an app that will be built once and sit in maintenance mode for 10-20 years, being built by a skilled expert? Custom code without a framework may be the way to go, for both the frontend & backend.