18 Nov 2018 - by 'Maurits van der Schee'
I love Ruby on Rails and I was reading Ben Halpern review of David Heinemeier Hansson's Keynote on Railsconf. I agree with Ben Halpern that the reduction of "the mental load for developers" is an undervalued concern in the world of web development frameworks. In this post I will define some even stronger goals for web development frameworks.
Ben Halpern continues:
This is a pretty clear and strong statement, followed by another strong statement:
Rails [...] often fails to benefit quickly from the latest and greatest tools or architecture principles. It's occasionally brutal in this way. But the acknowledged trade-offs keep it healthy.
I completely agree with Ben.
I believe that a there are three things a good web framework should have:
They should aim to reduce the following:
One of the thing we can do without is Dependency Injection (a popular method to implement Inversion of Control).
Dependency Injection has numerous serious disadvantages. Most web applications are simple administrative applications with web forms that do little more than simple CRUD. Most have some form of asynchronous jobs, but these are often developed in another technology. It simply does not pay off to be this flexible. The web development framework designer already knows what you are going to build and what is needed for that. I feel that function libraries with stable, well designed and documented APIs are the pragmatic choice that fits much better.
So, it may be clear that I believe that simple is better. With that “vision” I wrote MintyPHP. Whether you like it or not you may decide for yourself, but it certainly is easy to learn and about faster than CakePHP or Laravel, while providing the same abstraction layers to keep things organized.
Check out https://mintyphp.github.io/