If you spend a lot of time on a single framework, you will transcend and become a sort of frontend diety, growing multiple extra limbs allowing you to type in CSS classes faster than any mere mortal
What’s sad is that web development is only a nightmare so websites can be worse.
I genuinely believe it’s part of the concerted effort by the cabal to make us accept a ‘new normal.’
They don’t want an environment where anyone feels like they can make a website. They want us to believe we need to spend years studying before we can do anything, and even then we can only do what our bosses tell us to.
Generally I find many these frameworks will make some complicated things simple, but the cost is some things that were once simple are now complicated. They can be great if you just need the things they simplify - or in other words can stick to what they were intended for, but my favorite way of keeping things simple is to avoid using complicated and heavy frameworks.
Why is that silly? As long as the classes follow a strict naming scheme & have useful abstractions, that seems much better than having to give every node a unique class name that doesn’t necessarily have much meaning. I can’t count the number of “container” and “wrapper” and “content” classes I’ve seen & written, where the names don’t describe anything useful.
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.
If using plain CSS, usually it’s enough to set
widthappropriately, andmargin-leftandmargin-righttoauto.If using a Modern Frontend/CSS Framework, then may God have mercy on your poor soul.
(Seriously I just started a new project with TailwindCSS and I’m so confused. But not entirely desperate yet.)
So what is the point of these frameworks if they make it harder?
If you spend a lot of time on a single framework, you will transcend and become a sort of frontend diety, growing multiple extra limbs allowing you to type in CSS classes faster than any mere mortal
Until everyone moves over to the next thing and you start from 0 again. Web dev is a nightmare.
What’s sad is that web development is only a nightmare so websites can be worse.
I genuinely believe it’s part of the concerted effort by the cabal to make us accept a ‘new normal.’
They don’t want an environment where anyone feels like they can make a website. They want us to believe we need to spend years studying before we can do anything, and even then we can only do what our bosses tell us to.
Generally I find many these frameworks will make some complicated things simple, but the cost is some things that were once simple are now complicated. They can be great if you just need the things they simplify - or in other words can stick to what they were intended for, but my favorite way of keeping things simple is to avoid using complicated and heavy frameworks.
I think they exist because of ignorance.
People who don’t understand how to do a task will usually choose the wrong tools for that task.
If someone is trying to cover up their lack of knowledge, they will usually make things more complicated than they need to be.
w-... mx-auto, replace the 3 dots with your desired width value, and that’s it with tailwindI’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…
Why is that silly? As long as the classes follow a strict naming scheme & have useful abstractions, that seems much better than having to give every node a unique class name that doesn’t necessarily have much meaning. I can’t count the number of “container” and “wrapper” and “content” classes I’ve seen & written, where the names don’t describe anything useful.
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.