The idea is create the conditions to use reusable components in Moodle.
This’s not a small issue,
Because everybody wants to be more concentrated in the business layer (if we talk about an LMS better is: educational layer).
Don’t reinvent the wheel, (but reinvent yourself).
Readable, reusable, maintainable, scalable, we listen this words every day. In the PHP world many things happened, Symfony did a dramatic movement and generated many PHP components, Laravel used some of this and now is a strong framework. The developers wants to reuse their knowledge in this world of changes.
Many projects are using Symfony components, Moodle use some of them in the testing layer.
Moodle give me a lot and my little contribution is put this issue on the table.
Is this a new idea? Maybe not https://tracker.moodle.org/browse/MDL-43836
I want to be honest, I choosed course/edit.php intentionally because from my point of view this is the core of Moodle around of this (I’m talking about the course) you have the activities and resources.
WWW is moving very fast, in the past everybody looks Jquery but now many developers work with frameworks like Reacjs, (Vuejs is growing and angularjs was a cloud in sky) maybe the team from Jquery will revert this situation, maybe not. From my point of view the front-end now is a very dynamic field.
Moodle is now Barcelona! good choose and very good luck.