You don’t need a framework that makes you a blog in 10 minutes.

I can’t deny that it’s impressive that you can set up a blog, e-commerce, or anything else in the amount of time it takes to name that blog or e-commerce.

is not what you need

Even if you’re building one of those, you might not want a framework that does this for you.

Your needs are your own and while it is easy to set up, will it continue to help and work for you?

It doesn’t matter if you can build up a project in minutes if after that everything you need to build takes hours.

it’s a wedding

Choosing a framework is akin to marriage.

There will be framework for good or bad and it’s a messy thing to divorce (if it’s even possible).

Plus, it’s often hostile to infidelity, so when you can’t solve a problem in that framework with its accepted tools, you’re in for a bad time.

How to evaluate a framework?

As with everything in programming… it depends.

The most important thing is how much support it has and whether or not you can see it grow. (Telling, and unfortunately, that means that as good as it looks, fresh off the oven framework probably isn’t what you should be considering.)

Then you should evaluate how they work and how they tell you should use their framework.
Do you agree with their choice or would it be a different way?

And lastly, does it help you with what you need most? And how hard is it to bring third-party solutions to locations it doesn’t cover?

A framework serves itself first

Some players can influence a framework too much to solve a specific need only because they need it. Even if you try to PR a solution, the owners may not agree with it.

I’m saying this because they probably created the framework for some reason and have their own beliefs about what and how they should solve it. And your need for anything is not a priority for them.

Have you gathered all the essentials?

If you know exactly what you need along the way you can assess whether the framework you are considering has everything you need and helps you with all of that.

You might also consider that whatever you think isn’t done the way you would or will cause some sort of problem along the way.

If you’re building your own framework, you absolutely need your own version of “build a blog in 10 minutes”

Unless you’re solving some real niche problem that makes it easy for creators to share a framework with their fanbase, you can just spin something up fast and make it work if you need a lot of fun. Complicated steps are required and what not.

The best framework isn’t always about being “the best”, but about using enough people to solve a problem and drive it forward.

And the more people are using it, the more content gets created…

If you’re into React, you’ve probably heard of NeXT and if you’re an updater, you might have thought that NeXT 13 was revolutionary. You’ve probably even heard of remixes and thought that remixes were doing some of those revolutionary things before. And if go down the holes, you’ve also heard of RedwoodJS which came up with an amazing way to do some of those revolutionary things.

At this point I’m not sure which one is “best”, but next probably takes the crown because it’s so widely used that no matter what your problem, you’ve got similar problems and there are ways to solve them. There are enough people. Being so widely used also means that people already know how to use it and starting new projects with it is a good option as you will easily find people productive with it.

Unsplash. Photo by Alex Knight on

Leave a Comment