http://perpetual.education is a design/programming school. We like to be part of the discussion over here at Dev.to / We have time-slots for free conversations for career advice IRL : )
Let's see a list of "things we can just do" already...
If you're making a quick MVP for a desktop-only dashboard app - and you only have a night... and you already know bootstrap from years of already using it... then great... but otherwise? Just write CSS!
I always prefer CSS Grid or Flex Box before I consider using a CSS framework. And if I do use one it is because a company wants to use it for a project or something. Vanilla is more than good enough now.
I agree in terms of layout and what not and also admit that yes, I have to because employer X has already decided.
I use this term vanilla javascript and vanilla css because it's such a well-understood one. But am I being fidgety that I prefer now to say platform javascript or platform css? Vanilla has always bugged me somehow. I literally had a debate with a friend because on AgnosticUI site it says "It even works in vanilla JavaScript 😎 "; and it links out to that funny vanilla javascript page that pretends to be an actual framework. But I feel we should rename this thing. What do you think?
Well... it depends a lot on the project... personally even though I like writing up raw CSS (making use of --var declarations to emulate what frameworks do) it is handy to have a simple scaffolding stylesheet to lean on and do a lot of the heavy lifting. When you have many projects on at once you need to find all the time you can get for delivering them, and simpler lightweight frameworks are perfect for that.
I personally try to stay away from clunky and bloated frameworks, and opt for things like Tailwind.css that you can just sprinkle here and there to help out with some of the more tedious parts of UI design. The framework shouldn't dictate the appearance too heavily (like Bootstrap does), but it should just be there to catch your fall when you need it, and let you stay in the driver's seat in terms of appearance.
This is the bit that excites me, and gives me new confidence in frameworks. More and more of them are opting to be just a single simple CSS stylesheet, mostly using --var declarations to do all of the hard work, and the result is frameworks that are more flexible and 'modern' than the old days where we'd have to override thousands of styles by hand. Tailwind is a great example of that new approach.
http://perpetual.education is a design/programming school. We like to be part of the discussion over here at Dev.to / We have time-slots for free conversations for career advice IRL : )
How is tailwind modern? It's just a ton of unreadable utility styles that you have to memorize. They've just created a new metalanguage - and now they can charge people to use 'pro.' It's like the first idea that ever happened... and then we realized it was bad - and now tailwind is doing it x100 10 years later. How is that modern?
Tailwind is highly modular, and doesn't hold your hand, so it's more 'modern' than the traditional frameworks like Bootstrap that have opinionated ideas about how a card or a menu bar should look. If you have a problem trying to memorise utility styles you can always refer to documentation, so I don't think that's an argument against Tailwind.
If you want to do absolutely zero thinking when you're writing HTML, but still have the power of a framework to support it, you can always turn to classless frameworks: github.com/troxler/awesome-css-fra...
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's 2020, we don't need CSS "frameworks" anymore :)
AMEN!
Let's see a list of "things we can just do" already...
If you're making a quick MVP for a desktop-only dashboard app - and you only have a night... and you already know bootstrap from years of already using it... then great... but otherwise? Just write CSS!
I always prefer CSS Grid or Flex Box before I consider using a CSS framework. And if I do use one it is because a company wants to use it for a project or something. Vanilla is more than good enough now.
I agree in terms of layout and what not and also admit that yes, I have to because employer X has already decided.
I use this term vanilla javascript and vanilla css because it's such a well-understood one. But am I being fidgety that I prefer now to say platform javascript or platform css? Vanilla has always bugged me somehow. I literally had a debate with a friend because on AgnosticUI site it says "It even works in vanilla JavaScript 😎 "; and it links out to that funny vanilla javascript page that pretends to be an actual framework. But I feel we should rename this thing. What do you think?
Well... it depends a lot on the project... personally even though I like writing up raw CSS (making use of --var declarations to emulate what frameworks do) it is handy to have a simple scaffolding stylesheet to lean on and do a lot of the heavy lifting. When you have many projects on at once you need to find all the time you can get for delivering them, and simpler lightweight frameworks are perfect for that.
I personally try to stay away from clunky and bloated frameworks, and opt for things like Tailwind.css that you can just sprinkle here and there to help out with some of the more tedious parts of UI design. The framework shouldn't dictate the appearance too heavily (like Bootstrap does), but it should just be there to catch your fall when you need it, and let you stay in the driver's seat in terms of appearance.
This is the bit that excites me, and gives me new confidence in frameworks. More and more of them are opting to be just a single simple CSS stylesheet, mostly using --var declarations to do all of the hard work, and the result is frameworks that are more flexible and 'modern' than the old days where we'd have to override thousands of styles by hand. Tailwind is a great example of that new approach.
How is tailwind modern? It's just a ton of unreadable utility styles that you have to memorize. They've just created a new metalanguage - and now they can charge people to use 'pro.' It's like the first idea that ever happened... and then we realized it was bad - and now tailwind is doing it x100 10 years later. How is that modern?
Tailwind is highly modular, and doesn't hold your hand, so it's more 'modern' than the traditional frameworks like Bootstrap that have opinionated ideas about how a card or a menu bar should look. If you have a problem trying to memorise utility styles you can always refer to documentation, so I don't think that's an argument against Tailwind.
If you want to do absolutely zero thinking when you're writing HTML, but still have the power of a framework to support it, you can always turn to classless frameworks: github.com/troxler/awesome-css-fra...