If you like designing and work in a team where design is done separately u should write vanilla css. For a full stack developer more on backend bootstrap is a life saver
I don't get it though. Can't you do both? I mean, can't you just include bootstrap but only use it where you don't care much about customization. The rest you can still do vanilla
@@LongBoy.0 Hey, I'm using this SASS mixins all the time in enterprise projects... They are really handfull, wanted to share :). github.com/PawFV/SASS-mixins-for-all-projects
Amazing comparison between Bootstrap and plain CSS. I really like that you bring up examples and talk about different scenarios. The best is that you don't want to sell Bootstrap as some people do in other videos but you stay objective explaining what Bootstrap is really useful for. It's a real help, thank you!
I'm glad you enjoyed my explanation. I generally prefer doing custom CSS but there are so many cases where having a library like Bootstrap is so useful. A lot of my recent backend projects are Bootstrap projects.
Bootstrap is a really life savier. As a developer I must say It save me so much time and it so pratical that I have zero complainings about using bootstrap. Also, if you want to customize something really differnt to the framework, just don't use the classes, just make it yourself as usual. And the documentation is also awesome. Cheers to all webdevelopers!!!
In my job I have to make a lot of quick sites for impatient clients so yeah, Bootstrap is great. I save my vanilla CSS skills to more personalized projects.
Bootstrap has my most favorite documentation ever, it's clear, concise and very visual, and it avoids overwhelming you with extra details, it's so approachable even for non fluent English speakers
I totally agreed with him!! I've learnt so much from cracking every little single details in styling myself and mostly from this guy here! If you want to learn and be good at something, do it and do it from scratch!! But yeah if you're so good at it now and want to save a bit of time then use bootstrap.
I mean, if you like backend, learning bootstrap is better. Fullstack developers more on the backend side are still benefited by using bootstrap. The only exception would be a frontend developer.
I completely agree. I wish my employer understood that. They seem to think that because it's popular that means it's better for every use case. I recently got put in a situation where I had to write a moderately complex UI and I just couldn't have done it if I used Bootstrap. So, instead of asking permission, I asked for forgiveness (I'm not endorsing that approach but I had to accomplish the goal) And my code reviewer completely understood when he saw what I did. The HTML was much easier to read and it's much more maintainable in the end.
"You don't need to know CSS" You actually do - whilst you can get by without knowing it, to really utilise the power of frameworks, you need to know CSS. "Bootstrap is best for projects that don't change much" Seriously, this comes down to knowing CSS and knowing how to manipulate a framework. It's the biggest mistake detractors of frameworks make. They view the framework as a whole, instead of a series of components! Sure, if you use the entire bootstrap framework and spend hours overriding styles and struggling to make your site look like a design? You are doing it so wrong. You can take *any* part of a well written CSS framework and lift it out of the framework, into your own. Like the grid? Heck, just lift it - stick it in your own project. Don't feel like recreating all the form styles? Then just pick the forms part of a framework. This is where you *have* to know css and scss. Why would you do this though? Well, it's simple. Bootstrap and frameworks like it, have had thousands of eyes on the code, hundreds of contributors. They've gone through all of the gruntwork, the pain barriers of getting things working in different browsers. They've gone through the optimisation, the modularisation of the code that makes up a framework. Why would you re-invent it? Ultimately, you will just end up creating your own framework - and I can bet, at the end of it, it will be a bit like bootstrap, but not as good. So, why wouldn't you use it? Well, there's lots of reasons. You may be looking for the cutting edge of CSS - frameworks are always going to be behind the curve. The bottom line here is very much one of experience. Those with a lot of experience will either recognise bootstrap as being a high quality starting point, or a place to get ideas or will hate it. Hating it is pointless. Use it as a reference if you must - it will improve your CSS, it will improve your understanding of modularity, of semantics. It will give you ideas about patterns - when you start extending bootstrap, you will suddenly understand just how clever it is. If you don't understand what Bootstrap is doing, you really shouldn't be trying to make your own framework in the first instance. And if you are working on a big project and are NOT using a framework - either by developing your own, or using a third party one, or a combination of the two (the best option) - you really don't know what you are doing at all. Your CSS, in a few months to years, will end up becoming an unmaintainable mess. The clue is in the name - it's a FRAMEWORK - that doesn't mean you need to use all of it. That doesn't mean you can't extend it. You need to understand that MANY of the problems you may face when crafting your own CSS, have been resolved in frameworks. Yep, you can find those same resolutions all over the web - in stackoverflow comments, or articles or whatever. OR, you can look to popular frameworks and magpie code. THAT is how frameworks are used properly.
@@trappedcat3615 Yep, true, but if you want to modify, then you at least need know how to change the variables and recompile - that's about all you can do. This is perfectly fine for some use cases - notably, back-end developers wanting a framework or even for basic prototyping - css frameworks can excel at that. However, the moment you start needing to do more, you have to get your hands dirty and dive into the code.
I use bootstrap just for the grid sytem and for navbar because this saves my time from writing my own media quries and css grid Except this is use custom css
I just started learning web development a couple months ago and I can’t tell you how much I NEEDED to hear this. I’ve been asking myself this question so much after discovering bootstrap, and this answered it in such a practical way
Since I started very recently to learn coding CSS and HTML, never been attracted by Bootstrap. I decided to investigate it, as some people talk amazing things about it. "Simple, fast, and you do not need to know to code", they say. I thought sure, when you don't know JS for some staff as nav bar it can be useful, but after seeing your video, I got it clear. I love design, I find buts almost every time as things don't look as I had imagine. So bootstrap it's not for me. Thanks for your explanation.
it does not have to be either all or nothing with bootstrap. you can use SASS with bootstrap to only import the needed parts of the bootstrap CSS. also, you can customize the look and feel of bootstrap and it can look quite different compared to the standard bootstrap look and feel. regarding the frontend frameworks like React. you can actually find libraries that implement the bootstrap for you and they take care of the JS code so you don't have to worry about JQuery. for example "reactstrap" is one such library
Thank you so much this is really helpful...I have been look for videos like this for the past days, but I never had a clear satisfaction on what to decide on...thanks a lot bro
Thank you I'm learn Front-end and was confused when I saw bootstrap thinking it will be good but in my back of my mind I didn't want to use bootstrap and this video cleared my doubt
Yep, I took bs just for the column system but I was ignoring the full power of flex!!.. Now I'll have to extract it from my last project, as you said it's a pain in the neck having to override most of it.
Thank you. I’m going to learn React shortly and that info you gave about it not working well with Bootstrap (cuz of Jquery) helped me avoid wasting time on trying to learn it👍🏾
If you want to customize a Boostrap website, it's more easy to work with SASS. When you know SASS, you understand how Boostrap works, and it's more interresting in my opinion. Thanks for your vid, I suscribe ;)
Thank you so much Kyle. I used to use bootstrap before my I was goot at vanilla JS but lately I've been building small components like the carousel, responsive nav using vanilla JS and CSS, and I can tell you, I don't think I need it any more. For my friends that love bootstrap I'd suggest you learn vanilla JS to it's roots. You won't need bootstrap anymore.
You say the right things. You could do one video on css bem (block-element-modifier), and also other frameworks, like bulma, foundation or the even better minimalist frameworks like milligram or purecss. Anyway nowadays with css flex, grid, variables, counters, transitions/animations, well, I'd use stylus max. but that too only for the lack of semicolons and curly brackets. and probably postcss.
Currently using it on a school project and it's very useful since I don't have time to learn a bunch of CSS, and I prefer working on backend stuff anyway
Toan- - use NO Bootstrap when: 1:50 -2:39, 1. when you use CSS, learn front-end, want to make beautiful front-end. do a heavy front-end work (like with ReactJs, because ReactJs not work well with Jquery, some of which is embedded in Bootstrap) 2, when you only need make grid or some layout, you can make it with only some css. 3. when you dont want to working around bootstrap, trying to make it look exactly to what you hope for. - use Bootstrap when font-end is not really important, and if you focus on backend
FYI: You can pick whatever you want from bootstrap. It's not all-or-nothing like you claim in this video. Version 3 lets you pick each component individually and version 4 provides a few bundles with different features inside. You can also pack your own according to your needs. I personally haven't had the chance to work with bootstrap 4, but I never had any issues with bootstrap 3. Overwriting styles to your needs is easy.
You can pick and choose, but usually when people use Bootstrap they use it all. Also for simple things overrides are easy, but I find as the complexity of my app grows it becomes a real pain to constantly overwrite bootstrap.
Yeah me and most of the people i work with are like this, BS4 has some really good stuff, but we normally just import it JS, or just link it and pick some things...Personally i like the pre made boxes and what not but i push with Grid over the standard BS grid But i can't agree with the Author of this video most of US don't use it all, we mix it around...BS is becoming outdated and fast with the new Grid setup and react
This is really helpful. I already have basic knowledge about html and css, and I'm still learning more everyday. But i think I'm good enough to move forward and start learning bootstrap next. Thanks for giving me (as a beginner) an idea on which scenarios where bootstrap is the best option.
I couldn't have said it better. The learning curve is quite steep and "mentally" locks you in to Bootstrap - however nice it is as long as you do not care about its size. Better invest in learning "modern" CSS. You can sill borrow some of the Bootstrap ideas and concept but it will make your site or app looks less "Bootstrappy" then a lot of other sites.
As a marketer with minimal HTML/CSS knowledge, stuff like Bootstrap is a godsend for launching minimum viable websites quickly. If it works aka makes money, then sure, redo it properly with optimized pure code at some point.
Honestly, at first at thought that it would always be better to do the styling yourself from scratch. In university, I had to make a website for a project. CSS was a nightmare, I had like 700+ lines of CSS code and it still isn't perfect. I thought having more control equals better, however for some reason, I had to constantly clear the browser cache in order to reload the websites and load the new styles.
I would not recommend anyone to jump directly on bootstrap without knowing CSS or without having good grip on CSS. Bootstrap is just a framework and the basic work of any framework is to make your work easy and add more functionality that's it nothing more nothing less
I only learned CSS after screwing up a big project with Bootstrap. I thought it would save time, but it wound up adding unnecessary complexity, and we wound up doing a lot of all nighter sessions to get it out the door.
No mention of ARIA? For a more well rounded explanation, this needs to be mentioned. What I learned from using Bootstrap is how to do the accessibility stuff. Other than that, anything called framework has it's drawbacks. No matter what framework, it takes away a developers freedom. Another thing, the next version (in development, can be tested to be prepared for whenever it is released) runs without jQuery.
This might just be asking the same question, but what about for a job skill? What if you want to be a frontend developer and you want to learn Bootstrap, or another css framework as a job skill? Is it worth learning Bootstrap in that situation? Or is it better to just learn it on the job when you need it?
Totally agree that bootstrap is not for everyone and every use case. i can use css quite well but the only reason why I'm picking up bootstrap is because many local jobs have it as requirement.
If you trying to stand out and create your own style, stay away from bootstrap, I would say depending on your experience with the front end development you can wrap up a good looking website using just CSS, HTML, and javascript, as he said in the video you going to spend more time going against bootstrap style to make your site look the way you want it to look
Web Dev Simplified I don’t know why people think they have to learn every frameworks in order for them to be a good developer, the people who created bootstrap had to learn core css, bootstrap is nothing but core css put together to create what we now known as bootstrap, me I built my own mini framework very basic, when I start a new project I just go from there, the problem with new developers they spend to much time worrying about the outcome instead of spending time understanding the code Let’s take an if statement for example, I’ve seen so many people struggle to understand the meaning of an if statement and it’s so simple If the door is open { ENTER THE ROOM } else { What can you do if the door isn’t open ? #1 either stay outside or go home, simple } I don’t care how good a framework is if you don’t know the fundamentals of the language the framework was built on you always going to hit a break wall at the end
Hey. I'm new at this, and as I'm learning Bootstrap, I felt kind of trapped in B.S. styles, so I reached to you to clarify this. "Is there something I don't know about bootstrap, that I should, in order to make it look at least a little bit original?" was my main concern. So yeah, strong points you made about it. You saved me a lot of struggle, or, as you say "fighting against bootstrap". Thanks for that
Bootstrap is OK, but Material Design Bootstrap is much better. The best thing about it is to design fast. I can even prototype in bootstrap (Material Design) because how fast it is to throw markup. I can bring any wireframe to life even faster than in XD. Also, it feels just like vanilla CSS. I add whatever I want and override whatever I want. It's about starting on square 15 instead on square one. So the answer is very easy: yes. Always use it.
It is just another option to add and by no means and end all.. What you said at 2:15 I am gonna disagree there where who doesn't want a really nice looking front end? That is the whole purpose for Bootstrap while not spending a lot of time on front end.
You don't have to download the entire Bootstrap CSS library. You can cut out any code from it you don't want or need on the website. I have used the grids from Bootstrap multiple times, and just deleted all the other unnecessary code from the CSS before uploading it to my server.
I write back office business apps. Vue.js and bootstrap are critical to the work I do. Bootstrap does a great job matching colors. The spacing on the page is excellent. It is awesome that tables and grids are pretty much reactive right out of the box. The fonts and controls look much better than default HTML. Yes, not good that I have not learned CSS grid. And a problem for public facing sites because of the bootstrap bundle size.
Programming with Peter honestly it depends on your experience with CSS and HTML, I myself can code a fully functional website in one day, I'm talking about multiple pages, cool effects, responsive and everything, I think most ppl just copy and paste and don't really understand how the code works
Programming with Peter it would be faster because you have a problem remembering all the crazy names bootstrap has, for example in my little framework for margin-top I simply name it (my-10, my-20, my-5) of (nm) for no margin and you not left with a bunch of code you aren't using
Main aim of the video is - If you wanna just create project for client its ok to use bootstrap - if you wanna learn front-end just learn css completely first and then move on
Bootstrap is only ok for programmer-only jobs (no web designer, and the dev has little UI/UX capability) and, even then, only if it's a very simple responsive site. Otherwise it's even more limiting than plain HTML. I got added in 2018 to a project that uses it at a popular rocket company, where I had mainly programmed the flight software. After a few weeks, I told them "the CARD is not supposed to be an ARCHITECTURAL ELEMENT." But, um, there were many more serious problems, too, as you could have guessed.
The only guy who really knew what explanations I needed.
If you like designing and work in a team where design is done separately u should write vanilla css. For a full stack developer more on backend bootstrap is a life saver
Tanzim Ibthesam I agree
That's what he said.
I don't get it though. Can't you do both? I mean, can't you just include bootstrap but only use it where you don't care much about customization. The rest you can still do vanilla
@@nvmffs You can do everything with css why just use it for responsiveness rather use Tailwind
Agreed
I recommend a lot SASS, it's a preprocessor but it makes it A LOT easier to write and organize CSS. You can also create your "own" framework with it.
@Nikola Kretschmer I'm pretty sure the curly braces are in the same place on the mac. Have you looked there?
Plus, modular SASS in react is amazing
@@LongBoy.0 Hey, I'm using this SASS mixins all the time in enterprise projects... They are really handfull, wanted to share :).
github.com/PawFV/SASS-mixins-for-all-projects
SASS is amazing. Started using it like 3 days ago. Absolutely incredible stuff.
@@paujoan401 Thanks for sharing! I actually use Bulma for a lot of my work and it comes with quite a bit of these.
Amazing comparison between Bootstrap and plain CSS. I really like that you bring up examples and talk about different scenarios. The best is that you don't want to sell Bootstrap as some people do in other videos but you stay objective explaining what Bootstrap is really useful for. It's a real help, thank you!
I'm glad you enjoyed my explanation. I generally prefer doing custom CSS but there are so many cases where having a library like Bootstrap is so useful. A lot of my recent backend projects are Bootstrap projects.
Bootstrap is a really life savier. As a developer I must say It save me so much time and it so pratical that I have zero complainings about using bootstrap. Also, if you want to customize something really differnt to the framework, just don't use the classes, just make it yourself as usual. And the documentation is also awesome.
Cheers to all webdevelopers!!!
Yes. Bootstrap helps me a lot to save my time.
In my job I have to make a lot of quick sites for impatient clients so yeah, Bootstrap is great. I save my vanilla CSS skills to more personalized projects.
Bootstrap has my most favorite documentation ever, it's clear, concise and very visual, and it avoids overwhelming you with extra details, it's so approachable even for non fluent English speakers
I totally agreed with him!! I've learnt so much from cracking every little single details in styling myself and mostly from this guy here! If you want to learn and be good at something, do it and do it from scratch!! But yeah if you're so good at it now and want to save a bit of time then use bootstrap.
I mean, if you like backend, learning bootstrap is better. Fullstack developers more on the backend side are still benefited by using bootstrap. The only exception would be a frontend developer.
This is a very logical and well put together explanation on the pros and cons of using Bootstrap. Thanks for taking the time to make the video!
I completely agree. I wish my employer understood that. They seem to think that because it's popular that means it's better for every use case. I recently got put in a situation where I had to write a moderately complex UI and I just couldn't have done it if I used Bootstrap. So, instead of asking permission, I asked for forgiveness (I'm not endorsing that approach but I had to accomplish the goal) And my code reviewer completely understood when he saw what I did. The HTML was much easier to read and it's much more maintainable in the end.
"You don't need to know CSS"
You actually do - whilst you can get by without knowing it, to really utilise the power of frameworks, you need to know CSS.
"Bootstrap is best for projects that don't change much"
Seriously, this comes down to knowing CSS and knowing how to manipulate a framework.
It's the biggest mistake detractors of frameworks make.
They view the framework as a whole, instead of a series of components!
Sure, if you use the entire bootstrap framework and spend hours overriding styles and struggling to make your site look like a design?
You are doing it so wrong.
You can take *any* part of a well written CSS framework and lift it out of the framework, into your own.
Like the grid? Heck, just lift it - stick it in your own project.
Don't feel like recreating all the form styles? Then just pick the forms part of a framework.
This is where you *have* to know css and scss.
Why would you do this though?
Well, it's simple. Bootstrap and frameworks like it, have had thousands of eyes on the code, hundreds of contributors.
They've gone through all of the gruntwork, the pain barriers of getting things working in different browsers.
They've gone through the optimisation, the modularisation of the code that makes up a framework.
Why would you re-invent it?
Ultimately, you will just end up creating your own framework - and I can bet, at the end of it, it will be a bit like bootstrap, but not as good.
So, why wouldn't you use it?
Well, there's lots of reasons. You may be looking for the cutting edge of CSS - frameworks are always going to be behind the curve.
The bottom line here is very much one of experience.
Those with a lot of experience will either recognise bootstrap as being a high quality starting point, or a place to get ideas or will hate it.
Hating it is pointless. Use it as a reference if you must - it will improve your CSS, it will improve your understanding of modularity, of semantics.
It will give you ideas about patterns - when you start extending bootstrap, you will suddenly understand just how clever it is.
If you don't understand what Bootstrap is doing, you really shouldn't be trying to make your own framework in the first instance.
And if you are working on a big project and are NOT using a framework - either by developing your own, or using a third party one, or a combination of the two (the best option) - you really don't know what you are doing at all. Your CSS, in a few months to years, will end up becoming an unmaintainable mess.
The clue is in the name - it's a FRAMEWORK - that doesn't mean you need to use all of it. That doesn't mean you can't extend it.
You need to understand that MANY of the problems you may face when crafting your own CSS, have been resolved in frameworks.
Yep, you can find those same resolutions all over the web - in stackoverflow comments, or articles or whatever.
OR, you can look to popular frameworks and magpie code.
THAT is how frameworks are used properly.
Here's the actual quote from the video -- "...you don't really need to know css in order to use these frameworks."
true
Thanks man.
@@trappedcat3615 Yep, true, but if you want to modify, then you at least need know how to change the variables and recompile - that's about all you can do.
This is perfectly fine for some use cases - notably, back-end developers wanting a framework or even for basic prototyping - css frameworks can excel at that.
However, the moment you start needing to do more, you have to get your hands dirty and dive into the code.
@@matthewtrow5698 true. Knowing CSS is essential in the real world.
Lol no
This man tels the truth i was just spend 3 mounths to learn CSS and you dont need any css Framework like bootstrap to make design
I use bootstrap just for the grid sytem and for navbar because this saves my time from writing my own media quries and css grid
Except this is use custom css
CSS grid is dead simple, and so are media queries, especially if you use SCSS or some other preprocessor.
the collapse though
@@rallokkcaz and CSS Grid + media queries are even more simple when you use grid-template-areas prop :)
Then you should consider using PurgeCss to get rid of all the unnecessary classes, or start using a lighter css framework like skeleton
@@YONS_or you could just import bootstrap's grid css file instead of the whole framework
I just started learning web development a couple months ago and I can’t tell you how much I NEEDED to hear this. I’ve been asking myself this question so much after discovering bootstrap, and this answered it in such a practical way
Same thing.
Thank you, Web Dev Simplified)
So... Are you using it or not?
Since I started very recently to learn coding CSS and HTML, never been attracted by Bootstrap. I decided to investigate it, as some people talk amazing things about it. "Simple, fast, and you do not need to know to code", they say. I thought sure, when you don't know JS for some staff as nav bar it can be useful, but after seeing your video, I got it clear. I love design, I find buts almost every time as things don't look as I had imagine. So bootstrap it's not for me. Thanks for your explanation.
same bootstrap is for learners who dont know designing in css i agrre with u
Do you deslike bootstrap because it doesn't give you the designs you want for your elements
Love the raw, no fuss style you have, bro. Unlike the majority of RUclips. Keep the lessons comg. Cheers
it does not have to be either all or nothing with bootstrap.
you can use SASS with bootstrap to only import the needed parts of the bootstrap CSS.
also, you can customize the look and feel of bootstrap and it can look quite different compared to the standard bootstrap look and feel.
regarding the frontend frameworks like React. you can actually find libraries that implement the bootstrap for you and they take care of the JS code so you don't have to worry about JQuery. for example "reactstrap" is one such library
Thank you! I’ve watched so many videos about Bootstrap, but you’ve explained it better in 3 minutes then a 20 minute video
Thank you so much this is really helpful...I have been look for videos like this for the past days, but I never had a clear satisfaction on what to decide on...thanks a lot bro
4:48
Thank you I'm learn Front-end and was confused when I saw bootstrap thinking it will be good but in my back of my mind I didn't want to use bootstrap and this video cleared my doubt
Yep, I took bs just for the column system but I was ignoring the full power of flex!!..
Now I'll have to extract it from my last project, as you said it's a pain in the neck having to override most of it.
I fell in love with bootstrap, scss and jquery
This makes a lot of sense. I have been in a scrum with bootstrap ever since I started to customize.
Me too. I think this has given me the confidence to dump it and plough my own furrow
Just discovered your channel and I am impressed! Perfectly explained and to the point. Keep up the great work!
I really appreciate it, you help me have a general view about yes or not bootstrap. So will you make a video "Should you use jQuery" like this?
Thank you. I’m going to learn React shortly and that info you gave about it not working well with Bootstrap (cuz of Jquery) helped me avoid wasting time on trying to learn it👍🏾
Same here
If you want to customize a Boostrap website, it's more easy to work with SASS. When you know SASS, you understand how Boostrap works, and it's more interresting in my opinion.
Thanks for your vid, I suscribe ;)
Thanks bro. I will learn sass later
If your a front end developer, use vanilla css. If your a full stack developer, use bootstrap css
i'm big fan of Mr.Robot and you very remind me the normal version of him, where he went to web instead of hacking xD
now I cant unsee it xD
Thank you so much Kyle. I used to use bootstrap before my I was goot at vanilla JS but lately I've been building small components like the carousel, responsive nav using vanilla JS and CSS, and I can tell you, I don't think I need it any more. For my friends that love bootstrap I'd suggest you learn vanilla JS to it's roots. You won't need bootstrap anymore.
Do u have any bookmarked vanilla js? Please share . Thanks!
share please
100% agree! I always felt like CSS frameworks were over-used.
Very well explained. Thanks!
Love your vids!
Thank you! I'm glad you liked it.
I do both, I use bootstrap for certain features, like the nav, cards, rows, cols, things like that, but not for any customized css.
Another top-shelf video kid! Keep up the great work :)
If you are focusing in front end definitely you need to learn CSS and make your own styling.. Some client nowadays are strictly in design.
You say the right things. You could do one video on css bem (block-element-modifier), and also other frameworks, like bulma, foundation or the even better minimalist frameworks like milligram or purecss. Anyway nowadays with css flex, grid, variables, counters, transitions/animations, well, I'd use stylus max. but that too only for the lack of semicolons and curly brackets. and probably postcss.
Beautifully explained. Thank you. Definitely subscribed.
Great to start the day with these tips. Thanks Kyle, again.
Currently using it on a school project and it's very useful since I don't have time to learn a bunch of CSS, and I prefer working on backend stuff anyway
Toan-
- use NO Bootstrap when: 1:50 -2:39,
1. when you use CSS, learn front-end, want to make beautiful front-end. do a heavy front-end work (like with ReactJs, because ReactJs not work well with Jquery, some of which is embedded in Bootstrap)
2, when you only need make grid or some layout, you can make it with only some css.
3. when you dont want to working around bootstrap, trying to make it look exactly to what you hope for.
- use Bootstrap when font-end is not really important, and if you focus on backend
FYI: You can pick whatever you want from bootstrap. It's not all-or-nothing like you claim in this video. Version 3 lets you pick each component individually and version 4 provides a few bundles with different features inside. You can also pack your own according to your needs.
I personally haven't had the chance to work with bootstrap 4, but I never had any issues with bootstrap 3. Overwriting styles to your needs is easy.
You can pick and choose, but usually when people use Bootstrap they use it all. Also for simple things overrides are easy, but I find as the complexity of my app grows it becomes a real pain to constantly overwrite bootstrap.
Yeah me and most of the people i work with are like this, BS4 has some really good stuff, but we normally just import it JS, or just link it and pick some things...Personally i like the pre made boxes and what not but i push with Grid over the standard BS grid
But i can't agree with the Author of this video most of US don't use it all, we mix it around...BS is becoming outdated and fast with the new Grid setup and react
This is exactly what I was looking for. Thank you Kyle.
Great explanation man, thanks, you save hours of training with bootstrap
This is very clear and useful. It confirms my thinking and adds extra detail I hadn't considered. Thank you
Really nice judgement bro. Thanks
This is really helpful. I already have basic knowledge about html and css, and I'm still learning more everyday. But i think I'm good enough to move forward and start learning bootstrap next. Thanks for giving me (as a beginner) an idea on which scenarios where bootstrap is the best option.
Your cute, can I take u out for lunch?
I couldn't have said it better. The learning curve is quite steep and "mentally" locks you in to Bootstrap - however nice it is as long as you do not care about its size.
Better invest in learning "modern" CSS. You can sill borrow some of the Bootstrap ideas and concept but it will make your site or app looks less "Bootstrappy" then a lot of other sites.
It is harder and harder to get clients willing to pay for the fancy stuff. I go for bootstrap 90% of the time
where you get clients???
job? freelance?
finally the video i wanted, 100% agree with this bro. smart
Thanks for simplifying you saved our time and clear our confusion
Thanks man! Good Info. All the best to you!
I only really use parts of bootstrap for the responsive navbars, navbars are a pain for me create
Kyle, would really appreciate a video on making websites mobile ready without bootstrap! Because that to me is one of the key advantages.
add media queries
Use CSS grid for the main layout of the site.
Thanks a lot man, this is really what I needed
As a marketer with minimal HTML/CSS knowledge, stuff like Bootstrap is a godsend for launching minimum viable websites quickly. If it works aka makes money, then sure, redo it properly with optimized pure code at some point.
Honestly, at first at thought that it would always be better to do the styling yourself from scratch.
In university, I had to make a website for a project. CSS was a nightmare, I had like 700+ lines of CSS code and it still isn't perfect. I thought having more control equals better, however for some reason, I had to constantly clear the browser cache in order to reload the websites and load the new styles.
Same fuckin thing...... Used to clear cache to load the website
Thanks for claryfying bro, great vid
Boostrap is one of the things that most help me as a developer. The responsiveness and templates save lot of time and create a good looking
You taught me much!!- I use Jquery/Java/Python/sql and Jquery doesn’t mix well with PHP!!- a killer to decipher!!
I would not recommend anyone to jump directly on bootstrap without knowing CSS or without having good grip on CSS. Bootstrap is just a framework and the basic work of any framework is to make your work easy and add more functionality that's it nothing more nothing less
Thanks a lot bro. This explanation really broke things down.
I only learned CSS after screwing up a big project with Bootstrap. I thought it would save time, but it wound up adding unnecessary complexity, and we wound up doing a lot of all nighter sessions to get it out the door.
No mention of ARIA? For a more well rounded explanation, this needs to be mentioned. What I learned from using Bootstrap is how to do the accessibility stuff. Other than that, anything called framework has it's drawbacks. No matter what framework, it takes away a developers freedom. Another thing, the next version (in development, can be tested to be prepared for whenever it is released) runs without jQuery.
MrHerbalite thank god they're getting rid of jQuery.
Very helpful video, thank you!
This might just be asking the same question, but what about for a job skill? What if you want to be a frontend developer and you want to learn Bootstrap, or another css framework as a job skill? Is it worth learning Bootstrap in that situation? Or is it better to just learn it on the job when you need it?
Totally agree that bootstrap is not for everyone and every use case. i can use css quite well but the only reason why I'm picking up bootstrap is because many local jobs have it as requirement.
Thank you. Very well explained. As always.
Totally agree with your opinion.
If you trying to stand out and create your own style, stay away from bootstrap, I would say depending on your experience with the front end development you can wrap up a good looking website using just CSS, HTML, and javascript, as he said in the video you going to spend more time going against bootstrap style to make your site look the way you want it to look
I couldn't agree more.
Web Dev Simplified I don’t know why people think they have to learn every frameworks in order for them to be a good developer, the people who created bootstrap had to learn core css, bootstrap is nothing but core css put together to create what we now known as bootstrap, me I built my own mini framework very basic, when I start a new project I just go from there, the problem with new developers they spend to much time worrying about the outcome instead of spending time understanding the code
Let’s take an if statement for example, I’ve seen so many people struggle to understand the meaning of an if statement and it’s so simple
If the door is open {
ENTER THE ROOM
} else {
What can you do if the door isn’t open ?
#1 either stay outside or go home, simple
}
I don’t care how good a framework is if you don’t know the fundamentals of the language the framework was built on you always going to hit a break wall at the end
I always use boostrap for browsers support considerations
Hey. I'm new at this, and as I'm learning Bootstrap, I felt kind of trapped in B.S. styles, so I reached to you to clarify this.
"Is there something I don't know about bootstrap, that I should, in order to make it look at least a little bit original?" was my main concern. So yeah, strong points you made about it. You saved me a lot of struggle, or, as you say "fighting against bootstrap".
Thanks for that
Bootstrap is OK, but Material Design Bootstrap is much better. The best thing about it is to design fast. I can even prototype in bootstrap (Material Design) because how fast it is to throw markup. I can bring any wireframe to life even faster than in XD. Also, it feels just like vanilla CSS. I add whatever I want and override whatever I want. It's about starting on square 15 instead on square one. So the answer is very easy: yes. Always use it.
Thanks man just what i was looking for ....
It is just another option to add and by no means and end all.. What you said at 2:15 I am gonna disagree there where who doesn't want a really nice looking front end? That is the whole purpose for Bootstrap while not spending a lot of time on front end.
You don't have to download the entire Bootstrap CSS library. You can cut out any code from it you don't want or need on the website. I have used the grids from Bootstrap multiple times, and just deleted all the other unnecessary code from the CSS before uploading it to my server.
Very nicely put. Thank you.
This vid game me a lot of realization thank you so much
Thanks for clearing this up for me :). I'm more of a front end dev, so I'll just continue with vanilla css
Kyle you Nailed it!!- DONT USE BOOTSTRAP except for btn(s)- TOTALLY AGREE!!!!!!!!!!
I write back office business apps. Vue.js and bootstrap are critical to the work I do. Bootstrap does a great job matching colors. The spacing on the page is excellent. It is awesome that tables and grids are pretty much reactive right out of the box. The fonts and controls look much better than default HTML. Yes, not good that I have not learned CSS grid. And a problem for public facing sites because of the bootstrap bundle size.
If you like the style of bootstrap, yes, writing raw css takes longer...
Programming with Peter honestly it depends on your experience with CSS and HTML, I myself can code a fully functional website in one day, I'm talking about multiple pages, cool effects, responsive and everything, I think most ppl just copy and paste and don't really understand how the code works
@@youngjojo3052 that's true too, but your skills + some help would be even faster right ?
Use SASS or LESS and create your own library with mixins and such, then you can write custom styles in no time.
@@Italiafani it's not no time, you have to maintain the library etc.. Obviously you cans tart your own library from another one, why not that?
Programming with Peter it would be faster because you have a problem remembering all the crazy names bootstrap has, for example in my little framework for margin-top I simply name it (my-10, my-20, my-5) of (nm) for no margin and you not left with a bunch of code you aren't using
Really clarifying! Thank you!
Main aim of the video is
- If you wanna just create project for client its ok to use bootstrap
- if you wanna learn front-end just learn css completely first and then move on
Thank You My brother you saved my life today
Thanks for this good advice!
I have watch both videos of you explaining Tailwind and Bootstrap and it goes without saying that you prefer tailwind.
I needed to hear this.
Thank you very much, you clear me a lot!
I'm glad about this video. I just started react. I won't use bootstraps
react-bootstrap is a thing and you can just import specific components, might not be a bad compromise
@@atlow2543 It's been eleven months. I switched to vuejs and i use bootrapvue. Vuejs is way simpler and easier than reactjs.
bootstrap 5 is no longer relying on JQuery. Javascript part is completely re-written in vanilla js.
Bootstrap is only ok for programmer-only jobs (no web designer, and the dev has little UI/UX capability) and, even then, only if it's a very simple responsive site. Otherwise it's even more limiting than plain HTML. I got added in 2018 to a project that uses it at a popular rocket company, where I had mainly programmed the flight software. After a few weeks, I told them "the CARD is not supposed to be an ARCHITECTURAL ELEMENT." But, um, there were many more serious problems, too, as you could have guessed.
Best reason to use bootstrap in my opinion: teamwork
Thanks, that was easy to understand & informative.
OK, now you made me change my mind about learning bootstrap .. :D
Which is better? Bootstrap or Tailwind blocks / Tailwind Components?
You have really spoken, much appreciated my man
Thanks for the valuable comment. You saved me from getting in the wrong direction.
I was in situation where I cant use flexbox or grid, but forced to use flexbox from bootstrap
Great, practical analysis, thanks.
I only use bootstrap because it makes your project responsive to all browsers and devices, sometimes I struggle so much with media queries
To the point! subscribed