Shouldn’t they be designed in an intuitive manner that makes misuse more difficult than regular use?
Otherwise, why even bother using them? It’s like now you need to know all the ins and outs of CSS and a trendy framework that will lock you into their ecosystem.
Kidding aside, I think the popular frameworks these days are incredibly well made. Frontend web has always been hell, and if your job is producing functional web GUIs, you can’t do it on a large scale without them.
Based on my own experience developing GUIs, I’ve reached the conclusion that creating them through code is obsolete.
We should be focusing on developing GUIs to develop GUIs, like Godot, instead of ‘frameworks’ that make an obsolete method of doing things even more cumbersome and complex.
I’m doing a small hobby project (a ladder/ranking system for playing beer sports with my community), and I tried out Tailwind.
I gave up and loaded Bootstrap instead, but I will probably end up just writing all the CSS myself.
Seems so silly to have 15 CSS classes on a single DOM element…
Who’s saying you’re using the frameworks correctly?
Shouldn’t they be designed in an intuitive manner that makes misuse more difficult than regular use?
Otherwise, why even bother using them? It’s like now you need to know all the ins and outs of CSS and a trendy framework that will lock you into their ecosystem.
Kidding aside, I think the popular frameworks these days are incredibly well made. Frontend web has always been hell, and if your job is producing functional web GUIs, you can’t do it on a large scale without them.
Based on my own experience developing GUIs, I’ve reached the conclusion that creating them through code is obsolete.
We should be focusing on developing GUIs to develop GUIs, like Godot, instead of ‘frameworks’ that make an obsolete method of doing things even more cumbersome and complex.
Well, I find bootstrap very intuitive, and I don’t have 15 classes on my elements. That’s why I was asking.