It is pretty clear to me there are a couple schools of thought on how to describe UI and it is a sort of passing ships in the night scenario. While I see value in single file Components you don't need a special format for it. Having standardized entry points is just config objects all over again. It's this endless loop: functions -> config -> classes -> functions -> ... Everyone has their own opinion where it should stop. These paradigms can really influence the design of libraries and the direction of how future features will work. React has been pushing functions and functional composition for really good reasons. Adding convenient abstractions can eventually diverge. But unfortunately its probably one of the things that makes a given library feel "right" for the user.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It is pretty clear to me there are a couple schools of thought on how to describe UI and it is a sort of passing ships in the night scenario. While I see value in single file Components you don't need a special format for it. Having standardized entry points is just config objects all over again. It's this endless loop: functions -> config -> classes -> functions -> ... Everyone has their own opinion where it should stop. These paradigms can really influence the design of libraries and the direction of how future features will work. React has been pushing functions and functional composition for really good reasons. Adding convenient abstractions can eventually diverge. But unfortunately its probably one of the things that makes a given library feel "right" for the user.