I've been using lightweight CSS frameworks because I needed the column system they had, discovering Flexbox Grid framework in this article was fantastic!
In the other hand I agree with you... Mostly. Actually I do hate Bootstrap! And it makes me so sad and angry that everyone is teaching Bootstrap to junior programmers as if it was the only way. The only thing I disagree with is that Bootstrap it's "good for fast prototyping".
There are many more frameworks out there designed to prototype easy and faster, such as Bulma CSS, Materialize and even Tailwind (this last one is about utilities but it's escalating so good).
I think those using Bootstrap nowadays probably don't want to try other frameworks or either they can't switch because their projects were built with it from scratch.
Programmer, humorist. Host of the Citizen Coder Podcast. I interview developers from all over the world, from beginners trying to break into the industry to senior devs.
First of all I'm not a coder, I'm a fullstack so I also do design, and when I'm forced to use the guides of Google Material to design a product then of course I'll be also forced to use Materialize, and actually its easier than bootstrap.
In another hand, I've suggested 2 more frameworks really easy and fast to use and prototype which are very extended and useful.
Comment marked as low quality/non-constructive by the community. View Code of Conduct
A fullstack is a coder that programs frontend and backend, hence the term. For you to say you're not a coder means you're ignorant of what a fullstack developer does, yet you say it's your profession. Hence, we mock.
I think that's a little obtuse, @satougg4
To some "coder" carries a tone of derision, or it's seen as reductive- Since it only conveys a small facet of what a developer does.
Personally, I often see it used/misused by people who overestimate their depth of expertise, so for me, it's a red flag.
It's obtuse to assume that because someone wants to clarify that their expertise is not just that "they write code", (but instead they work across a variety of architectures and design and implement systems) means they don't know that their job involves writing code
Read the guys article and figure out for yourself whether he knows what his job involves
Don't use Flexbox Grid framework. It is quick but dirty solution. Let me explain: Years ago people used html table element for page layout but for big projects you should have a separation of content and presentation. That means that for layout people should use CSS but for content HTML. So in your HTML you should have classes like content, article, form, legend, navigation, input, about, menu etc...but in CSS you should have a designer set the layout of those elements/classes by choosigin grid, flex, float or whatever it needs.
But with Flexbox Grid framework you are designing classes to have a predefined layout in HTML, instead of just having class="content" and let that content layout be defined in CSS. I get it, it is quick and convinient but it is wrong in a long run. When you want to change a layout you would need to changee html instead of just changing CSS file. It is not a good practice so we moved away from that a long time ago.
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.
Hello Codedgar;
I've been using lightweight CSS frameworks because I needed the column system they had, discovering Flexbox Grid framework in this article was fantastic!
In the other hand I agree with you... Mostly. Actually I do hate Bootstrap! And it makes me so sad and angry that everyone is teaching Bootstrap to junior programmers as if it was the only way. The only thing I disagree with is that Bootstrap it's "good for fast prototyping".
There are many more frameworks out there designed to prototype easy and faster, such as Bulma CSS, Materialize and even Tailwind (this last one is about utilities but it's escalating so good).
I think those using Bootstrap nowadays probably don't want to try other frameworks or either they can't switch because their projects were built with it from scratch.
Really nice article!
Yeah I've looked at bulma. I'm planning to use it in my personal projects. Seems easier to use than Boostrap.
It is, absolutely😉, and now it has lots of plugins that include javascript!
Whena coder criticize Bootstrap to suggest Materialize, I stop to read 🙄
Both are frameworks with opinionated designs.
Sorry Silvan, but that makes no sense.
First of all I'm not a coder, I'm a fullstack so I also do design, and when I'm forced to use the guides of Google Material to design a product then of course I'll be also forced to use Materialize, and actually its easier than bootstrap.
In another hand, I've suggested 2 more frameworks really easy and fast to use and prototype which are very extended and useful.
fIrST oF iM NOt a cODeR, iM a fULLsTaCK
...Excuse me?
A fullstack is a coder that programs frontend and backend, hence the term. For you to say you're not a coder means you're ignorant of what a fullstack developer does, yet you say it's your profession. Hence, we mock.
I think that's a little obtuse, @satougg4
To some "coder" carries a tone of derision, or it's seen as reductive- Since it only conveys a small facet of what a developer does.
Personally, I often see it used/misused by people who overestimate their depth of expertise, so for me, it's a red flag.
It's obtuse to assume that because someone wants to clarify that their expertise is not just that "they write code", (but instead they work across a variety of architectures and design and implement systems) means they don't know that their job involves writing code
Read the guys article and figure out for yourself whether he knows what his job involves
Don't use Flexbox Grid framework. It is quick but dirty solution. Let me explain: Years ago people used html table element for page layout but for big projects you should have a separation of content and presentation. That means that for layout people should use CSS but for content HTML. So in your HTML you should have classes like content, article, form, legend, navigation, input, about, menu etc...but in CSS you should have a designer set the layout of those elements/classes by choosigin grid, flex, float or whatever it needs.
But with Flexbox Grid framework you are designing classes to have a predefined layout in HTML, instead of just having class="content" and let that content layout be defined in CSS. I get it, it is quick and convinient but it is wrong in a long run. When you want to change a layout you would need to changee html instead of just changing CSS file. It is not a good practice so we moved away from that a long time ago.