Why Not Frameworks?

Ah... Frameworks, the holy grail of web development.

Frameworks

For many, the best solution. For me, probably too much. But why not? Well, it's a personal choice.

I'm a Full Stack developer working 12-14 hours a day, and I use Laravel all day long.

Yes, I really love Laravel. It's so elegant, so powerful, so clean. But I have a problem.

I'm unable to use 100% of its potential.

What's the issue? Simple: excess weight. Or rather, wasted functions and utilities.

"But you're using Flask on this site..."

Exactly, there's the catch.

Flask is not a framework, it's a microframework.

With Flask, you literally write everything yourself—no command-line magic like laravel new, django-admin startproject, or rails new. You write it all: routing, configuration, file structure, everything.

You write what you do. You write what you need. You write what you want.

Beautiful, right?

Although I love Laravel and use it for personal projects, I can't use it for my personal site because I don't need everything it offers. I don't want a bloated site with wasted functions and utilities.

In fact, in this website's manifesto, I explain another reason why I can't use a full framework.

I'm not saying you shouldn't use frameworks. Just that if you're building something you really want to control and understand completely, a microframework like Flask might be your best option.

Back to Philosophy
Back Home
Moon Earth