3 ms·
I had to RTFA three times to understand what was bothering me about it: it basically takes sensible principles about software development and turns into a self-
by rglullis 6y ago
I had to RTFA three times to understand what was bothering me about it: it basically takes sensible principles about software development and turns into a self-affirmation exercise about the author's work where he applied those principles and packaged as some grand wisdom about "frameworks".
The first half boils down to (a) research existing solutions, (b) avoid NIH when you can and (c) refactor your code as you find commonalities and points of re-use. The second part is mostly about designing a system that could be used/extended by someone else (separate the generic from the the specific, treat it as open source).
Those are very valid points. Thing is, in following those very valid points one could probably write another article with a far greater number of examples (and a far better lesson) where the best course of action is to NOT roll your own framework and prefer to adopt some existing code and make the necessary extensions/modifications.
To illustrate, I checked the morepath "framework". It seems to tick all of the boxes one would expect from a proper open source "framework". It even has more documentation than I would expect from such a small open source project. The one point where it fails is that it never gets to give one simple example of a pain point that this project solves that all of the other million web frameworks don't.
In the end, it seems that the author is looking for an ex post facto rationalization for some of his projects that had a lot of his time invested but no external interest afterwards. Too bad that it seems that he also took the wrong lesson out of it.
- skinnyarms 6y agoI would read that article, and vote it up, but I don't think we need to be harsh towards this one. It's a good read, makes some good points and I'm thankful for it.
- rglullis 6y agoWere it something pointing out the trade-offs that he found when rolling his own frameworks and I wouldn't be so put-off by it. But when an article wants to argue for something and its justifications could be used to conclude the exact same opposite? I fail to find those good points, to be honest.
- fahrradflucht 6y agoThere is a long page in morepath's documentation explaining how it differs from others. [0] [0]: https://morepath.readthedocs.io/en/latest/compared.html https://morepath.readthedocs.io/en/latest/compared.html
- rglullis 6y agoYes, I read it. My point is that there is nothing on that page that helps me understand what pain it solves that other frameworks don't and it doesn't bring one single use case to try to convince the reader that these design decisions led to a better application with any of the alternatives. In other words, after reading it I am left with the feeling the author wrote one long masturbatory piece of documentation for some software that only him is ever going to use.