3 ms·
8 months ago, building my first web app, I grabbed bootstrap and got to coding. For the same reasons as you. Cleaning up my code last week I decided to remove
by welanes 10y ago
8 months ago, building my first web app, I grabbed bootstrap and got to coding. For the same reasons as you.
Cleaning up my code last week I decided to remove it from my source folder to see what would happen. Gulp did its thing, I hit refresh and my app looked exactly the same.
The CSS I added on top of Bootstrap removed the need for 160ish kb of styling rules and gave me full control of the look of my app. No more "col-sm-6 col-md-5 col-md-offset-2 col-lg-6 col-lg-offset-0" nonsense and no more wrestling with the framework.
A day learning CSS basics, Flexbox, Psuedo-elements and best practice brings big returns. And more importantly, gives you design control over whatever you're building which makes prototyping super easy.
- Roboprog 10y agoThank you. Hearing I'm not the only one who feels that way makes me feel better about not including Bootstrap in the app rewrite we are doing at work (taking a decade old, 500K+ LOC, Struts app into the rich web client / Angular 1 era). In general, I have been happy with making a little style file that grew up to 300 (I think) lines or so over that last almost a year. This approach (not using a mystery CSS file) also paid off when we had to make a custom page with alternate styling for embedding within another app. Now if only CSS selectors were as full featured as XPath :-)