@pythonantole9892
The only thing that bootstrap lacks is influencers and hype men. We live at a time where people use tools not to solve a problem but because some influencer has said so.
@scrooge-mcduck
3:45 Not correct: you can edit/override Bootstrap's default CSS and style it however you like/can. 4:10 Basic component looks like this, yes but it can look however you want if you spend the time to style it. That's what these are - basic. Bootstrap is going nowhere.
@soulless8471
PHP, JQuery and Boostrap will never die!
@SXsoft99
Boostrap is css groping your components and adding prefedined functionality on top. Tailwind goes in the direction that you write web components with predefined style and manual functionality and then reuse (vue, react, blade, etc compoents). Bootstrap is still used in many admin themes but the problem with most of them is that they have been written bad for customability and clients wants to buy them and change them too much.
@herosova
its just a tailwind promotion video
@deb783
BOOTSTRAP IS NOT DEAD Web Development is not about this or that - there is no one way of doing things, modern web development has so many options including core CSS, Bootstrap and Tailwind, each of these technologies have their limitation and strengths. In some situation core CSS is useful or in others Bootstrap or Taiwind can be useful too. These technologies can work together or independently. It doesen't matter end of the day, what matters is what product you are delivering at the end of the day.
@akaDL
PHP, MySQL and Bootstrap will live on. Younguns, don't fall for this noobtrap of chasing the shiniest new thing.
@mikeswheels
You guys are making the point for bootstrap in this video. The whole point of the framework is to come up with the wire frame and the MVP through rapid prototyping. Tailwind CSS is a decent tool for a lot of people working in react and other similar component type systems. Personally, when it comes to bootstrap the semantic structure of the CSS and ability to customize each declaration means I can take advantage of the cascade and modern CSS tooling. With tailwind, I could declare my class structure and use tailwind variables inside, but even Adam advises against this.
@minhkhoa4783
I worked with Material UI + ReactJS, when the project grew, performance degarded significantly and painful. Instead of focusing on development, I had to waste my time to optimizing the UI. Eventually, falling back to Bootstrap was the right decision, no more UI optimization shit. As long as it helps, it's not obsolete.
@mr.mike678
I moved to Tailwind because I love Thailand.
@tugrultopuz
I think the criticism of Bootstrap here might stem from a misunderstanding of its true potential. Bootstrap is actually very adaptable to CSS best practices, especially when you pair it with Sass for custom styling and PostCSS for optimizing the final output. Yes, if you're only using it out-of-the-box, it can seem bloated or restrictive, but skilled developers use mixins, variables, and custom builds to create clean, modular, and maintainable code. I’d say this is more of a skill issue than a problem with Bootstrap itself, developers who understand its deeper features can achieve far more efficient and flexible results.
@onlylars
I recently started a project with Tailwind but i just spent too much time customizing my Elements and had very long class names which just looked awful in code. I then switched to Bootstrap to make it easier to get the project done first, but might replace elements one by one later on with tailwind. I just think tailwind feels like inline css
@wildfireDZ
Tailwind recreated the same problem Bootstrap solved : writing inline css, only different. Tailwind components are also another way of writing css classes
@stuffthatmightbeinteresting
Isn't tailwind and bootstrap addressing different issues. Why people don't recognized this. Tailwind is an substitute for CSS and bootstrap offers a done component, button, input, etc. Am I wrong about this one? I saw a lot of people comparing the two but it doesn't make sense to me.
@mosiuoasesing2846
With tailwindcss, you end up with too much css for doing anything, even just a mere button. Eg, in BS, you just go like: 'btn btn-primary'. Tailwind needs a lot of css for what BS achieves with just that. A lot of times we are not interested in the ability to customize things, we just need to finish work faster, and BS is extremely good at that. So, BS is still very alive
@oussamatouhami5027
Thanks bro for this video, it was rich of information about bootstrap.
@lolhp._.
I feel like new devs are going to tailwind very fast without knowing vanilla css much.
@llothar68
The main problem is that css is wrongly designed. Today people want components, so css applying from the inside out, but it was previously designed outside in (defined for the whole page then specializing). Thats why native GUI programming is a much better engineering approach. Unless this huge problem is resolved it is not really worth the difference.
@marcodev3375
I prefer vanila css than bs & tailwind. Much better customization and no crazy long classname.
@CodeSource