Metadata driven framework!!!

[r rad]

I want to share with you all something that has been bothering me for a very long time: 

In all the free or documentation texts about Jam.py you can read that Jam.py is: 

- Open source 

- Python framework 

- Event driven 

- With a hierarchy of business objects 

- With a hierarchical event management scheme over those business objects 

- With support for multiple databases 

- etc. 

In our circles they would say, well those are the most common classifiers. In this way, Jam.py is comparable to other frameworks, built on similar principles, and used in a similar way. 

Okay, that's OK. But why isn't it written anywhere (or I didn't read it) after the first two, the most important classification: 

- "Metadata driven" framework. 

This classifier says almost everything about the internal construction of a framework: 

- It has absolutely nothing to do with MVC or MVT frameworks 

- The application is usually built through auxiliary tools (Builder) and left in the database or JSON files (or both). 

- The core of the framework reads data about parts of the application and dynamically creates objects from them, in this case Python, with which it works further. 

- and so on. 

So there is no python class that defines the model. Here the definitions are closed in admin.sqlite, namely the items and fields tables, which when read and passed through the meta layer become python objects that can accept data and then be passed to the presentation layer. 

About "metadata driven" programming it is not worth wasting words except:

- It's not programming for beginners, if they want to make an even more complex application 

- It is not a framework that you will learn in two days 

- This framework is made for creating large applications, without spending on standard elements, as is GUI, DB, etc., with minimal inclusion of code in the event-driven layer. 

Well, more or less we all know that. But we don't know why? 

Why didn't anyone write anywhere that the framework is "metadata driven"? Why has no one clearly and without any doubt, written such a fact, which would save a lot of time for those who want to learn it seriously and who could end up asking online for additional explanations about the principles of "metadata driven" programming. 

If someone knows, they are free to write these, but not assumptions, only facts. 

PS. I spent a lot of time studying all possible types of frameworks until I stumbled upon one that has the same development and execution scheme and realized that Jam.py is a "metadata driven framework". 

Why it was not written, I did not understand. Maybe you can help me understand? 

Greetings, Radosav