This is WAY better than any old school YAGNI post I've ever seen.
It's not another "Keep it simple" rehash, it's about not reinvention the wheel at the platform level.
I don't know why there's always such a temptation to write your framework and THEN write the actual product but it's always there.
Maybe because framework dev is unlimited creativity only vaguely tied to the real product, without even the constraint of having to work and not have bugs.
You might not find out about some of them till you actually try to use it, so you can pretend your framework is great when it's complete crap and will need a year of work to fix, which you'll have to do while you're also doing the actual product.
Hobby project are even more vulnerable to this, because there's zero pressure to actually do the project.
How many people wanted to make a game, so they made an engine, and 5 years later never made a game with it(Occasionally someone else does though, which is kind of cool)?
