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
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.
@@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
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.
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 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
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.
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
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
"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.
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👍🏾
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
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
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 ;)
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
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.
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
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
Hi Kyle, I really enjoy your comments. Just a note: I am personally working on a Python/SQL/Javascript( with API) -80- page design. I first used BS and then changed my NAV bar to a Sidebar ( responsive) - it killed me because not just the base layout but ALL pages layout went to hell!!- because of BOOTSTRAP. So , for 1-10 page design, not an issue, but for larger AVOID BOOTSTRAP!!!! Great video Kyle, always a fan even though I’m much older than you - you make me look ancient
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.
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.
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.
also another thing is bootstrap makes your html look extremely crowded now i get that it adds a ton of functionality but it also makes it almost unreadable for newer programmers.
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
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?
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.
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.
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.