John_Phoenix
Expert Member
- Joined
- Jul 8, 2017
- Messages
- 1,087
- Reaction score
- 624
In terms of CSS Frameworks, CSS has enough to get you to a layout/skin, a framework just gets in your way most of the time, eg. bootstrap with its 3/4 nested divs per element. The "other" problem with frameworks is the disconnect from the design process, the designer knocks out 12 pages, pouring over the checkboxes/fields/navigation and you as the frontend/ui guy has to $h!t in their sandbox because those elements could be built, if you include a new plugin just for a 300ms animation (and don't say you havent done this, we've all done it)
I agree with droid, a meta DSL is required that speaks to each component on 3 levels HTML/CSS/JS and the meta DSL is responsible for compositing the 3 pieces together. That way, the underlying structure is a pool of components with no state, and the DSL orchestrates these components into place, still with no states. Then your data comes in and populates the components "at that moment in time".
What would this meta language look like, probably JSON, back in the day (5/10 years ago) it would have been XSLT...
I do have one serious friggin issue with the way frontend is being done at the moment, in terms of frameworks/gulp/react and everything in between. Its so wasteful. A hard and fast rule in development is: the fastest function is NO function.
Why waste time processing templates in react, writing a Framework specific language only to have it translated twice! (JSX -> JS -> HTML) I mean come on... I could use all that horsepower to do everything react does. And yes, I completely understand that facef*** is trying to make the world a better place, and create a unified rendering platform, but the question is, at what point does a framework become a bloated piece of overkill. Vue is the same, you look at this and go... holy crap, this is so over-engineered.
Your thoughts?
I agree with droid, a meta DSL is required that speaks to each component on 3 levels HTML/CSS/JS and the meta DSL is responsible for compositing the 3 pieces together. That way, the underlying structure is a pool of components with no state, and the DSL orchestrates these components into place, still with no states. Then your data comes in and populates the components "at that moment in time".
What would this meta language look like, probably JSON, back in the day (5/10 years ago) it would have been XSLT...
I do have one serious friggin issue with the way frontend is being done at the moment, in terms of frameworks/gulp/react and everything in between. Its so wasteful. A hard and fast rule in development is: the fastest function is NO function.
Why waste time processing templates in react, writing a Framework specific language only to have it translated twice! (JSX -> JS -> HTML) I mean come on... I could use all that horsepower to do everything react does. And yes, I completely understand that facef*** is trying to make the world a better place, and create a unified rendering platform, but the question is, at what point does a framework become a bloated piece of overkill. Vue is the same, you look at this and go... holy crap, this is so over-engineered.
Your thoughts?
