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.
@@heathbruce9928nope, ES6, is just a superset of JavaScript with new commands and syntax like spreading array and arrow funcs, jQuery is more of animation l library
@@fairylychee I haven't looked using frameworks. Especially for CSS. I wanted to learn the language myself. And about 10 years ago jquery was necessary. JavaScript was all but forgotten and the web was moving forward. Once the w3c focused on it and can't to with es6, jquery's days were numbered. At last to me.
.. for those "experienced developers" (aka "frontend engineers") who don't know that everything said about Tailwind there applies to… well… CSS… alone.
Even if it is promotion, the real fact can't be ignored. I myself was a bootstrap fan till 2022 now I'm using tailwind and I'm happy with it. I will never go back to bootstrap again. Any framework or library fails to adapt the developer expectations and frustration will disappear.
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.
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.
@@xhavierj3915 what make you think it less popular ? there is more a lot admin theme made with Bootstrap rather than tailwind. The survey was made based people talk not what they use. For example is you are a noob you will asking on stackoverflow about tailwind, but if you were expert you don't need to asking on stackoverflow. So their survey is not accurate and not valid.
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.
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.
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.
there is no misunderstanding for those who criticize Bootstrap, I've been coding since 2009 and I never used bootstrap when it started getting popular simply because its very "LARGE" and "BLOATED" and you get a lot of CSS you dont even need, I have tried almost all CSS framework that ever existed and Bootstrap is one of the heaviest you could use. if you are going to use a pre-processor like SASS/LESS why would you even pick bootstrap as the base style when there is a lot much lighter like Bulma, Miligram, Pure, Skeleton, Spectre and so much more which are way lighter than Bootstrap. the only people who keep using bootstrap are those who never cared about bundle size which impact the page speed and performance, as well as those who never even tried other and much lighter CSS framework. and in terms of Tailwind, there is no comparison, TailWind creates your own CSS bundle at compile time, you dont even need to use the classes directly in html, and you can structure your class like doing Vanilla CSS/SASS then use function/directive to apply the styling, thats why its getting popular for those who want to write less code but feels like writing Vanilla SASS/SCSS
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.
Tailwind recreated the same problem Bootstrap solved : writing inline css, only different. Tailwind components are also another way of writing css classes
Vanilla css has it's downs too. Takes more time, when your project gets big you start to run out on ideas of what class name to use on each element since the class name is supposed to identify what that element is about.
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
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.
It's because TW is heavily promoted by SPA frameworks. Same as Vite - 90% of it's popularity is based on the fact that SPA frameworks adopted it for scaffolding and pretty much all guides on internet use default scaffolding. Opposite example: state manger Zustand was not so lucky and could not make itself THE "default state manager", so it's almost forgotten nowadays. But it tried so hard buying bloggers to promote itself last year...
@@ruam263 start with vanilla css as a beginner. dont jump to using css libraries. i dont know much vanilla css libraries that works without a framework but bootstrap might be good with only html css and js. react and vue have alot more options
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
Exactly my experience - As a backend developer who knew a bit of Bootstrap, I tried to learn Tailwind, but I felt it was too verbose and went back to Bootstrap. Anyway, my Frontend code never makes it to prod, I just write MVPs to demonstrate my BE functionalities and then the FE team takes over if the products gets the nod to graduate from MVP.
@@babatundeojerinde didn't know that exists. this now just even more looks like writing css with shorter names lol. Well for my current project bootstrap is enough to get the job done and if i wanna make it look better then i guess i'll switch to tailwind
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.
You have to declare one thing here. Are you promoting Tailwind here? I use Bootstrap religiously, and frankly, I am not going to abandon it anytime soon. Not all people want a home-cooked meal, they prefer fast food instead.
@@CodeSource Comparing Bootstrap to Tailwind doesn't make sense. Tailwind gives solutions for 25% of what Bootstrap does. Where do you have components and JS in Tailwind. Do you even understand differrences? Did you ever used Bootstrap or other COMPONENT library? What's the point to compare them to CSS utility lib?
Bootstrap with SCSS is the best combo and I've been using it most of the time. Right now I am learning NextJS with Tailwind for my personal project. I've noticed that Tailwind is a bit messy when I look at it, a lot of inline CSS. I prefer using SCSS cos I want to lessen the bootstrap classes and avoid writing inline css. I will never abandon Bootstrap and SCSS 💖💖Bootstrap is the reason why I fall in love with SCSS
@@multiwebinc isnt that the thing that bootstrap does very well for free? Their site is really hard for me to navigate but from what I can tell the components are what you pay for.
I used to use ready to use libraries like Quasar, Material UI and Bootstrap, but it was always a hassle to customize and add functionality to these components. The recent emergence of owning your components provided by ready-made components from shadcn/ui levering tailwind and headless ui feels to be right move towards getting the best of both worlds of ease of integration and customization.
Comparing Tailwind CSS and Bootstrap isn't entirely fair because they serve fundamentally different purposes. Tailwind CSS is a utility-first CSS framework, focusing on providing low-level utility classes to build custom styles.Bootstrap, on the other hand, is a component-based framework, offering pre-built components like buttons, cards, and navbars.
Perhaps bootstrap can exist as a useful tool that meets a specific set of requirements without trying to be too much more than it is now. API stability and reliability when it does what people need today is quite valuable. I have plenty of projects that don’t need more than what bootstrap offers and migrating away from bootstrap would be a lot of work.
The only type of tool that may kill bootstrap is a css only solution (eg bulma), but then bootstrap retains it's compat with old browsers as needed. One could argue that bootstrap's rigidity also helps with some customizeability.
“Experienced” devs use the right tool for the job. The right tool is the one the team knows, fits in, gets the job done fast and doesn’t create a maintenance hell due to over-customization.
Nah, Bootstrap is okay to build tech prototype UI, but designers don't use 12 columns system any way. It's easier to use something like library for typograaphy and library that makes life easy with adaptability. Also CSS is a lot more powerful now, you don't need so much browser specific prefixes.
@@gppsoftware you talk about something that don't exist. It's not how big business operates. And Brand Styles is not CSS. You can do whatever. Colors, Typography and spacing usually a 3 pages from Brandbook, you don't have to use special magical CSS for it.
@@gppsoftware for me this is almost a BS level, there websites looks so generic and idiomatic with jquerry and stuff. For me it looks like a Business that runs B2B outsource for corruption schemes and basically steal money. It's hard to take this serious. I remember "VEKA" had something similar, but they had there own Font, way of write things - they don't use capital letters, 1000+ pages os brand book and lots of other hardcore branding porn. For now companys that use there own CSS libraries looks like was run by Psycho or Bandits, kinda like a Redflag so far.
Bootstrap's out of the box functionality is very good. It also pairs very well with jQuery and is highly customizable if you know what you're doing. That, or just use stack overflow
Absurdly, some people have been predicting the end of certain technologies for a long time, but nothing ever changes. Take PHP, for example- I remember hearing over 10 years ago that it would be dead within two years. And what happened? After 10 years, It’s still widely used and supported by a large community of developers, and many of the world's most successful companies continue to rely on it. Enough with these baseless predictions-who cares about this nonsense?
If there is a designer involved in a project, use Tailwind instead of Bootstrap. It's a nightmare to "hack" the Bootstrap components. Tailwind with the utility first approach require no hacks.
It reminds me of that time were 😅 they posted "Java is dead". As a dev, it's much wiser to know the key foundations and not just blindly follow these posts.
Is this like a 2 year old script? Tailwind is also popular among beginners and soon you'll end up with a bloated pit as the amount of classes you write on a single div grows enormously over time. And Bootstrap DOES have component-driven design support. This video showed up just after I integrated Bootstrap into React a couple of hours back lmao.
well, still working on $10k project with bootstrap and jquery :D .... yep i'm old ...of course i would force new kids to learn newer tech ...just like the old days when we had to learn mootols, jquery or prototype
Bootstrap is so inconvenient to use with modern frameworks, and when you need to customize the component - you have all those css overrides. It brings more headache than solution. The reality is it's not a framework-first library - at least it doesn't position itself as. In the times when SaaS projects are thriving, and all component libraries are "showcasing" their components in the "Dashboard" example, bootstrap's dashboard is example is like from 2000s. Maybe that's why it's not hot anymore?
We got rid of Bootstrap in favor of….writing CSS again. After a while you will stop being a front-end developer and become a Bootstrap developer, they aren’t the same thing. We will not be using Bootstrap, Tailwind or Foundation. We’re instead just going to be developers.
I gave up on bootstrap and all others a long time ago. My own and personal framework is 1/10 in weight and complexity of any of these solutions and quickly and totally customizable, all with scss and no js.
@@LongJourneys like sure, you don’t have to think of values because someone else thought of them and created a set that you can use, but you still need to know css pretty well to build anything AND tailwind only offer a small array of predefined things like cards, buttons, alerts etc for free. If I’m building some simple application and I don’t care that much about the design, then I might as well use bootstrap and not worry about design issues. If I care about design, then I’ll make my own decisions on everything.
If you feel Bootstrap restricts you, I fail to see how Tailwind is any better. You could, you know, just use css and do exactly whatever you want, but I guess that would require more effort than most modern devs can be bothered to exert.
Good video, but there’s a really weird audio artefact throughout the video in the bass. It’s a little creepy… it sounds like lots of quick deep woofs or growls.
Truth is html evolved so much it now supports natively most of the functionnalities that lead to the creation of bootstrap. It still is a great fwk, but one day they should just display something like moment.js on their homepage "do you still need bootstrap today"
Tailwind also has cons. Sometimes dom elements can have very big class names. With code editor extensions you can just collapse class attribute value but anyway you just should understand each style which is applied inline which is inconvinient I think. I am afraid that very soon we come to a conclusion that writing ur own css is better approach for readability and performance 😅 I think bootatrap can gain popularity again if they use tailwind's approach of removing ghost selectors and modulize javascript to use only needed features.
Great developers use none of them. When using bootstrap or tailwind your HTML will look so verbose you'll get tired just by watching it. Nowadays css is super powerful, there are tons of Great new features you don't need Bootstrap nor Tailwind.
This feels kind of biased though. You can't say that Bootstrap is dying while it's still the most widely used CSS framework out there. There are right tools for the right job and new tools will always make existing tools less used. This applies to all things. Nothing wrong with having more tools.
The notion that experienced developers only choose Tailwind is concerning. Why should it be an issue if an experienced developer prefers Bootstrap? Personally, I find Tailwind’s class-heavy approach cluttered, whereas Bootstrap keeps my code clean and speeds up development. Instead of making generalized statements, shouldn’t we let developers choose the tools that work best for them? If one developer feels comfortable with Bootstrap, they should use it. Others might prefer Tailwind or a different framework-and that’s okay. Developers should be empowered to work with the tools they know and enjoy.
Bootstrap dying? Are you kidding, right? Finally we got a html/css framework mature enough... i right want more options out there, but say Bootstrap is dying sounds so naive 😅.
Ok I don't profess to being a web developer rather I tend to have focussed elsewhere. I did use bootstrap on my site and it really helped get it desktop/mobile ready. Listening to what you say about the different versions of bootstrap, it seems new versions come along with support for newer browsers capabilities and that's great, but is bootstrap really surviving or is it just the name that lives on?
Bootstrap - enabling speedy prototyping and backend developers to concentrate on functionality while maintaining an adequate user interface Tailwind - enabling front-end developers to remain relevant
I used to customize my own bootstrap utility classes, just import some of bootstrap sass files, and make own variables.scss, but then tailwindcss comes in, so say goodbye
Oh I thought it’s only me who has observed that BS is waning. I thought it’s because of TW and JS frameworks. I always thought that BS should have versions for at least the big 3 JS frameworks. Third party ports for me are lacking and I would use only if it’s BS team itself would develop it.
Follow CodeSource on X - codesource.io/X
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.
Exactly. Bootstrap is the best.
Tailwind labs pays influencers 100% they make a ton of money from selling TW themes
Maybe but it's not as easy to customise bootstrap websites. It's still good but definitely outdated.
@@raahimfareed So what you suggest?
PHP, JQuery and Boostrap will never die!
Isn't es6 essentially the same as jquery?
@@heathbruce9928nope, ES6, is just a superset of JavaScript with new commands and syntax like spreading array and arrow funcs, jQuery is more of animation l library
@@heathbruce9928 only if you take your sweet time to learn how to use it
it is, while php is undead We should no longer use jquery and bootsrap anymore
@@fairylychee I haven't looked using frameworks. Especially for CSS. I wanted to learn the language myself. And about 10 years ago jquery was necessary. JavaScript was all but forgotten and the web was moving forward. Once the w3c focused on it and can't to with es6, jquery's days were numbered. At last to me.
its just a tailwind promotion video
It's also correct in what it says.
.. for those "experienced developers" (aka "frontend engineers") who don't know that everything said about Tailwind there applies to… well… CSS… alone.
How to get promotion money? 😂
@@CodeSource An unpaid promotion is still a promotion
Even if it is promotion, the real fact can't be ignored.
I myself was a bootstrap fan till 2022 now I'm using tailwind and I'm happy with it. I will never go back to bootstrap again.
Any framework or library fails to adapt the developer expectations and frustration will disappear.
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.
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.
but is is getting less popular and tailwind is traking over, every other reacdt project that i see is using tailiwnd css
yes don't believe anything what tech youtubers saying. Trust what your local job market search not youtubers 😆
@@xhavierj3915 what make you think it less popular ? there is more a lot admin theme made with Bootstrap rather than tailwind. The survey was made based people talk not what they use. For example is you are a noob you will asking on stackoverflow about tailwind, but if you were expert you don't need to asking on stackoverflow. So their survey is not accurate and not valid.
@@xhavierj3915 tbh react and tailwind are both garbage
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.
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.
TAILWIND IS CLUTTER!
PHP, MySQL and Bootstrap will live on. Younguns, don't fall for this noobtrap of chasing the shiniest new thing.
I moved to Tailwind because I love Thailand.
😂😂😂
😂😂😂😂
😀 The only wise comment in this sea
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.
there is no misunderstanding for those who criticize Bootstrap, I've been coding since 2009 and I never used bootstrap when it started getting popular simply because its very "LARGE" and "BLOATED" and you get a lot of CSS you dont even need, I have tried almost all CSS framework that ever existed and Bootstrap is one of the heaviest you could use. if you are going to use a pre-processor like SASS/LESS why would you even pick bootstrap as the base style when there is a lot much lighter like Bulma, Miligram, Pure, Skeleton, Spectre and so much more which are way lighter than Bootstrap. the only people who keep using bootstrap are those who never cared about bundle size which impact the page speed and performance, as well as those who never even tried other and much lighter CSS framework.
and in terms of Tailwind, there is no comparison, TailWind creates your own CSS bundle at compile time, you dont even need to use the classes directly in html, and you can structure your class like doing Vanilla CSS/SASS then use function/directive to apply the styling, thats why its getting popular for those who want to write less code but feels like writing Vanilla SASS/SCSS
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.
I love bootstrap Grid, a solid easy to use responsive solution.
Tailwind recreated the same problem Bootstrap solved : writing inline css, only different. Tailwind components are also another way of writing css classes
Tailwind gives the power of css without the mental burden of coming up with class names. That is a major plus imo.
I prefer vanila css than bs & tailwind. Much better customization and no crazy long classname.
Vanilla css has it's downs too. Takes more time, when your project gets big you start to run out on ideas of what class name to use on each element since the class name is supposed to identify what that element is about.
@@lolhp._. Kind of solved in a easy way the naming problem with nested css
@@requindr how?
@@lolhp._. You can reuse .icon name in different context for example.
header { .icon { ... } }
.card { .icon { ... } }
@@requindr fair.
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
My reusable React components look like this The Tailwind classes go in the component definition file.
@@mike-365 only works if you use react, angular... Most of the time we are just serving html.
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.
I feel like new devs are going to tailwind very fast without knowing vanilla css much.
I agree.
agreed 100%
It's because TW is heavily promoted by SPA frameworks. Same as Vite - 90% of it's popularity is based on the fact that SPA frameworks adopted it for scaffolding and pretty much all guides on internet use default scaffolding. Opposite example: state manger Zustand was not so lucky and could not make itself THE "default state manager", so it's almost forgotten nowadays. But it tried so hard buying bloggers to promote itself last year...
What do you suggest for new dev? Vanilla css and bootstrap or css and Thai?
@@ruam263 start with vanilla css as a beginner. dont jump to using css libraries. i dont know much vanilla css libraries that works without a framework but bootstrap might be good with only html css and js. react and vue have alot more options
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
Exactly my experience - As a backend developer who knew a bit of Bootstrap, I tried to learn Tailwind, but I felt it was too verbose and went back to Bootstrap. Anyway, my Frontend code never makes it to prod, I just write MVPs to demonstrate my BE functionalities and then the FE team takes over if the products gets the nod to graduate from MVP.
100% agree
You could actually use the @apply directive to shorten class names.
@@babatundeojerinde didn't know that exists. this now just even more looks like writing css with shorter names lol.
Well for my current project bootstrap is enough to get the job done and if i wanna make it look better then i guess i'll switch to tailwind
Tailwind sucks, it results in horrific and long class sections in your html. I hate it
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.
Tailwaind is like a kick in your ass if use it...don't do that. Learn CSS.
The benefits and downsides balance each other out., If you like it use it. If you don't, then don't use it.
You have to declare one thing here. Are you promoting Tailwind here? I use Bootstrap religiously, and frankly, I am not going to abandon it anytime soon. Not all people want a home-cooked meal, they prefer fast food instead.
Why would I promote Tailwind?
@@CodeSource Comparing Bootstrap to Tailwind doesn't make sense. Tailwind gives solutions for 25% of what Bootstrap does. Where do you have components and JS in Tailwind. Do you even understand differrences? Did you ever used Bootstrap or other COMPONENT library? What's the point to compare them to CSS utility lib?
Ruby on Rails, JQuery and Bootstrap was absolutely ahead of their times
Damn, I love bootstrap
i've exhausted using tailwind, and move back to bootstrap 5 after their release... such a fresh air when moved back
Bootstrap with SCSS is the best combo and I've been using it most of the time. Right now I am learning NextJS with Tailwind for my personal project. I've noticed that Tailwind is a bit messy when I look at it, a lot of inline CSS. I prefer using SCSS cos I want to lessen the bootstrap classes and avoid writing inline css. I will never abandon Bootstrap and SCSS 💖💖Bootstrap is the reason why I fall in love with SCSS
I've created a tailwind.css like bootstrap based framework that allows you generate the needed css while benefiting from bootstrap classes
wow cool
@@learneverythingscience it's called custom-bs
@@sanusihassan7125 Nice, will try to check it out
Is it worth to pay 350 EUR (+taxes) for tailwind when you have bootstrap 5 for free?
Tailwind is free
You're getting Tailwind CSS mixed up with the Tailwind UI All-access license.
@@multiwebinc isnt that the thing that bootstrap does very well for free? Their site is really hard for me to navigate but from what I can tell the components are what you pay for.
Bootstrap is still widely use in backend development my friend!
The best solution is to create your own CSS Framework so you can have the best of both worlds.
I used to use ready to use libraries like Quasar, Material UI and Bootstrap, but it was always a hassle to customize and add functionality to these components. The recent emergence of owning your components provided by ready-made components from shadcn/ui levering tailwind and headless ui feels to be right move towards getting the best of both worlds of ease of integration and customization.
Well, I like bootstrap and won't be changing any time soon.
Comparing Tailwind CSS and Bootstrap isn't entirely fair because they serve fundamentally different purposes. Tailwind CSS is a utility-first CSS framework, focusing on providing low-level utility classes to build custom styles.Bootstrap, on the other hand, is a component-based framework, offering pre-built components like buttons, cards, and navbars.
Perhaps bootstrap can exist as a useful tool that meets a specific set of requirements without trying to be too much more than it is now. API stability and reliability when it does what people need today is quite valuable. I have plenty of projects that don’t need more than what bootstrap offers and migrating away from bootstrap would be a lot of work.
The only type of tool that may kill bootstrap is a css only solution (eg bulma), but then bootstrap retains it's compat with old browsers as needed.
One could argue that bootstrap's rigidity also helps with some customizeability.
This is NOT the story of Bootstrap, this is a Tailwind CSS commercial!
“Experienced” devs use the right tool for the job. The right tool is the one the team knows, fits in, gets the job done fast and doesn’t create a maintenance hell due to over-customization.
Bootstrap is not dying tailwinds is getting complex people are going back to Bootstrap
Nah, Bootstrap is okay to build tech prototype UI, but designers don't use 12 columns system any way. It's easier to use something like library for typograaphy and library that makes life easy with adaptability. Also CSS is a lot more powerful now, you don't need so much browser specific prefixes.
@@gppsoftware there is no benefits, it's okay to do things in most comfortable way.
@@gppsoftware you talk about something that don't exist. It's not how big business operates. And Brand Styles is not CSS. You can do whatever. Colors, Typography and spacing usually a 3 pages from Brandbook, you don't have to use special magical CSS for it.
@@gppsoftware give me the names.
@@gppsoftware for me this is almost a BS level, there websites looks so generic and idiomatic with jquerry and stuff. For me it looks like a Business that runs B2B outsource for corruption schemes and basically steal money. It's hard to take this serious. I remember "VEKA" had something similar, but they had there own Font, way of write things - they don't use capital letters, 1000+ pages os brand book and lots of other hardcore branding porn. For now companys that use there own CSS libraries looks like was run by Psycho or Bandits, kinda like a Redflag so far.
i am not about to get out of bootstrap, to make it straight, i hate tailwind
Bootstrap's out of the box functionality is very good. It also pairs very well with jQuery and is highly customizable if you know what you're doing. That, or just use stack overflow
Bootstrap rules, and with variables and other generators it can be customised for your brand
I like this explain, please agree “Bootstrap Studio” like a solution to diagram and optain results
Good job! I find that also the animation is great! What do you use as a softwar? Thank you.
The is the first video I watched. I subscribed. Great content❤
If Bootstrap drop SASS and use TailwindCSS it will be a big change
Bootstrap wont die just like wordpress
Rule #1 Never choose a software with a meaningless name
Which one has a meaningless name?
As long as browsers still understand these framework nothing is dead
I use Bootstrap heavily.
Front End is full of fads, instead of shipping actual products fast. No wonder junior FE devs can't get work.
Well, I use boostrap for school works (Typically fast for demo), but for company design, I use AntDesign for customization.
Bootstrap is great! It's still a very good choice for making web apps.
Tailwind is gasing out but Bootstrap has been the choose for starting more projects again even at the enterprise level.
Absurdly, some people have been predicting the end of certain technologies for a long time, but nothing ever changes. Take PHP, for example- I remember hearing over 10 years ago that it would be dead within two years. And what happened? After 10 years, It’s still widely used and supported by a large community of developers, and many of the world's most successful companies continue to rely on it. Enough with these baseless predictions-who cares about this nonsense?
If there is a designer involved in a project, use Tailwind instead of Bootstrap. It's a nightmare to "hack" the Bootstrap components. Tailwind with the utility first approach require no hacks.
It reminds me of that time were 😅 they posted "Java is dead". As a dev, it's much wiser to know the key foundations and not just blindly follow these posts.
I think bootstrap is good for POC, MVP, prototypes for amateurs amd newbies.Thats where it may survive.
If you need more control, just use HTML with vanilla JS and CSS. I use bootstrap BTW
Is this like a 2 year old script? Tailwind is also popular among beginners and soon you'll end up with a bloated pit as the amount of classes you write on a single div grows enormously over time. And Bootstrap DOES have component-driven design support. This video showed up just after I integrated Bootstrap into React a couple of hours back lmao.
well, still working on $10k project with bootstrap and jquery :D .... yep i'm old ...of course i would force new kids to learn newer tech ...just like the old days when we had to learn mootols, jquery or prototype
It was for people who can't write CSS and backend developers - PERIOD!
Whats the point then? Didnt we want to focus more on the feature rather than having more control on the design?
Bootstrap is so inconvenient to use with modern frameworks, and when you need to customize the component - you have all those css overrides. It brings more headache than solution. The reality is it's not a framework-first library - at least it doesn't position itself as.
In the times when SaaS projects are thriving, and all component libraries are "showcasing" their components in the "Dashboard" example, bootstrap's dashboard is example is like from 2000s. Maybe that's why it's not hot anymore?
We got rid of Bootstrap in favor of….writing CSS again. After a while you will stop being a front-end developer and become a Bootstrap developer, they aren’t the same thing. We will not be using Bootstrap, Tailwind or Foundation. We’re instead just going to be developers.
I gave up on bootstrap and all others a long time ago. My own and personal framework is 1/10 in weight and complexity of any of these solutions and quickly and totally customizable, all with scss and no js.
Same, I built my own but included a few JavaScript methods for simple menus and things.
The narrator is AI
Underrated 😮
holy shit yeah... if you're reading this, link this somewhere, everywhere.. @CodeSource, longer title on this one, capture more keywords
Bro what is this video. Bootstrap has its use cases still.
It’s like PHP to me. It might become niche, but it won’t die completely.
Navbars and 12 column grid system made me switch in late 2012.
make more videos, including IT starts up
Bootstrap had its golden era, but now its time for Tailwind CSS
100%
I honestly find tailwind css so… meh. Might as well write inline css at that point.
Fomo
@ssergium.4520 agreed lol. Tailwind is hot garbage.
@@LongJourneys like sure, you don’t have to think of values because someone else thought of them and created a set that you can use, but you still need to know css pretty well to build anything AND tailwind only offer a small array of predefined things like cards, buttons, alerts etc for free. If I’m building some simple application and I don’t care that much about the design, then I might as well use bootstrap and not worry about design issues. If I care about design, then I’ll make my own decisions on everything.
If you feel Bootstrap restricts you, I fail to see how Tailwind is any better. You could, you know, just use css and do exactly whatever you want, but
I guess that would require more effort than most modern devs can be bothered to exert.
Once you start using tailwindcss, it’s difficult to go back to bootstrap
Good video, but there’s a really weird audio artefact throughout the video in the bass. It’s a little creepy… it sounds like lots of quick deep woofs or growls.
Shout out to Bootstrap ❤
Some of the best API i used still have jQuery mobile as their interface. The framework does not matter at all cos customers dont care
As long as there is update never die
Truth is html evolved so much it now supports natively most of the functionnalities that lead to the creation of bootstrap.
It still is a great fwk, but one day they should just display something like moment.js on their homepage "do you still need bootstrap today"
Tailwind also has cons. Sometimes dom elements can have very big class names. With code editor extensions you can just collapse class attribute value but anyway you just should understand each style which is applied inline which is inconvinient I think. I am afraid that very soon we come to a conclusion that writing ur own css is better approach for readability and performance 😅 I think bootatrap can gain popularity again if they use tailwind's approach of removing ghost selectors and modulize javascript to use only needed features.
When you use bootstrap enough and see how much unused CSS it has,and if performance is critical,you know you won't used it.
Great developers use none of them.
When using bootstrap or tailwind your HTML will look so verbose you'll get tired just by watching it. Nowadays css is super powerful, there are tons of Great new features you don't need Bootstrap nor Tailwind.
This feels kind of biased though. You can't say that Bootstrap is dying while it's still the most widely used CSS framework out there.
There are right tools for the right job and new tools will always make existing tools less used. This applies to all things. Nothing wrong with having more tools.
The notion that experienced developers only choose Tailwind is concerning. Why should it be an issue if an experienced developer prefers Bootstrap? Personally, I find Tailwind’s class-heavy approach cluttered, whereas Bootstrap keeps my code clean and speeds up development. Instead of making generalized statements, shouldn’t we let developers choose the tools that work best for them? If one developer feels comfortable with Bootstrap, they should use it. Others might prefer Tailwind or a different framework-and that’s okay. Developers should be empowered to work with the tools they know and enjoy.
Bootstrap is still widely used and not dead
Bootstrap and jQuery had their backs broken from holding up the entire Internet for more than a decade.
Tailwind with reactjs is the best.
Can someone explain to me the advantage of writing class="p4" vs. writing style="padding: 4px"?
Edit, padding: 16 (4*4)
You write less in exchange for super duper long classes
Bootstrap dying? Are you kidding, right? Finally we got a html/css framework mature enough... i right want more options out there, but say Bootstrap is dying sounds so naive 😅.
Ok I don't profess to being a web developer rather I tend to have focussed elsewhere. I did use bootstrap on my site and it really helped get it desktop/mobile ready. Listening to what you say about the different versions of bootstrap, it seems new versions come along with support for newer browsers capabilities and that's great, but is bootstrap really surviving or is it just the name that lives on?
Boostrap really tried!.
It dominated for years. Other frameworks could not shake it until Tailwindcss came into the picture.
Bootstrap - enabling speedy prototyping and backend developers to concentrate on functionality while maintaining an adequate user interface
Tailwind - enabling front-end developers to remain relevant
What's with the wooshing sound on every single animation?
It’s dying because it is easier to copy and paste now than it was 10 years ago.
I used to customize my own bootstrap utility classes, just import some of bootstrap sass files, and make own variables.scss, but then tailwindcss comes in, so say goodbye
Ah! This is Frontend Development! Give it 5 seconds! 😊
Trust me, it wont die
Oh I thought it’s only me who has observed that BS is waning. I thought it’s because of TW and JS frameworks. I always thought that BS should have versions for at least the big 3 JS frameworks. Third party ports for me are lacking and I would use only if it’s BS team itself would develop it.
Now, let's get rid of Tailwind and its nasty code pollution.
Nice video for no updates like me... -DreamweaverUser
all these frameworks coming and going, let's just stick normal css..?