In reply to mark k..

@peter, no need to twist my words. I didn't say that using backbone was an obvious mistake that could have been avoided at the time, all I said that having the experience, repeating the same state of mind which lead to that mistake is a problem and sign of immaturity.

Wordpress refuses to grow as a software development organization, and the same state of mind of "hacking something quick using the hip tools de jour" is still prevalent. Just the fact of wordpress not being able to actually enforce its coding standard on its own code is a sure sign for that.

The media library is something that was not designed and was just hacked, under the assumption that if the code works it is good enough. Same is happening with the customizer that it is basically a long number of hacks with no design, the rest API which also was not designed for the community but only for the needs of whoever worked on it, and it is in core only because its developers were deemed to not be mature enough to accept "it is not ready" call made by matt (in retrospect his reasons were wrong, but that is not the point here), and now we have gutenberg which even before its 0.1 release started to suffer from feature creep.

As basically it is the exact same people being driving core through all this mishaps, it is not clear why one should assume any lesson would be applied today when you did not see all those people learning much before.

If whatever framework is selected without moving all the core to it (which is basically what pento and others advocate), it does not matter which one it will be as it will be a long term fail, incurring technical debt for other people to handle because "We are not mature enough to do boring things".