I guess this line of thinking works for embedded systems, I did not think of that. And sure there are a lot of redundant and bad frameworks out there, but all those exist because someone thought like you, that they don't need no framwork, or nothing suits this problem, and they wrote their own. All the good ones also started like this, but they are usually the result of many iterations and multiple people's pooled knowledge and is usually maintained, it is pretty arrogant to think you can beat that solution unless your project is extremely specific (which fits embedded). I've seen maybe a handful of no-framework-build-everything systems, at least one of them was not terrible built, but it was still a nightmare to maintain compared to similar sized projects.