Optimizing projects to keep only useful code

Great article, David. Simple and objective.

This topic reminds me of the controversy around frameworks from 2014, started by comments of the PHP creator Rasmus Lerdorf.

phpclasses.org/blog/post/226-4-Reas ...

In general, Frameworks that simplify developers' lives are a good idea.

The challenge for less experienced developers is to figure out what they can do when there is an error in the middle of a framework component. If they have not written that component wastes a lot of time figuring out what they need to fix.

Often a simple set of components that you wrote is better than using a complicated set of framework libraries that you do not understand how they work internally.

Recently I was hired to provide a replacement for a project because the maintainer of another Open Source library announced that he would no longer support it. Open Source is a great idea, but you must pay your bills working on your own Open Source packages.

It is not financially viable if you spend too much time working on Open Source projects that do not pay back the developer of those projects. So the time you spend on an Open Source project must be well invested. Using complicated frameworks that take you too much time is not viable.

The good news is the PHP Classes will soon provide a good solution to help PHP developers. Stay tuned for an announcement after June 24, when the PHP Classes site will complete 24 years of existence.

David, keep posting more educative articles like this one because you are helping many developers to learn from experienced developers like yourself.

Rasmus thought exactly the same thing I wrote about.

This is exactly why I love the components on the PHPClasses page, because they are simple and don't require big inheritance chains.
Mostly they follow the KISS principle: Keep It Simple Stupid.

Exactly. Well said.