And document it yourself, and maintain it yourself, and build an ecosystem of extension for it yourself, and create video tutorials for it yourself, and ...
A minimalist off-the-shelf framework can go a long way.
I like frameworks that do not do much more than provided by their libraries that get exposed by it. So I can always swap out libraries, or carry a long certain libraries after moving on from the framework.
It all depends on 1) how far away from the off-the-shelf framework you are going (or want to go); and 2) how many of your projects you are using it for.
Ideally, you would want to create a plugin/extension to the framework to do your custom thing. But sometimes -- especially when writing games -- you can end up doing things the framework (engine) was not designed for, so end up having/wanting to implement your own thing.
An extension ecosystem and video tutorials really aren't needed for an in-house framework.
Also, with 3rd party extensions, they tend to be poorly made/maintained, and at most do 80% of what I need. If lucky enough to find an extension that does what I need, then it's likely that 80% of it does things that I don't need, which just adds to the bloat and complexity.
And document it yourself, and maintain it yourself, and build an ecosystem of extension for it yourself, and create video tutorials for it yourself, and ...
A minimalist off-the-shelf framework can go a long way.
I like frameworks that do not do much more than provided by their libraries that get exposed by it. So I can always swap out libraries, or carry a long certain libraries after moving on from the framework.
reply