4 ms·

Another shity CSS framework that doesn't do anything better than adding code overhead to your project. Go ahead people use Bootstrap everywhere then wonder why

Another shity CSS framework that doesn't do anything better than adding code overhead to your project. Go ahead people use Bootstrap everywhere then wonder why your product fails in the market. It's better to write some clean, yet minimal CSS than use any kind of framework for CSS. Do you need responsive designs? Just use @media at the end of your CSS file to restyle some of the elements for different screen widths or just hide them. That's all you have to do!

LeafStorm 14y ago
I have been using Bootstrap for this entire year on various projects at work. Nobody complained because I was using Bootstrap. In fact, I actually got a lot of compliments about how well the projects looked. The fact is, outside Hacker News, nobody cares if you're using Bootstrap. They care if your project doesn't look horrible, and more importantly, they care if your project works. Now sure, I could learn CSS and do all the stuff you put in the last four sentences. But designing a good-looking style with all the components I needed - grids, buttons, navbars, modal dialogs - would take far longer than unzipping Bootstrap, dropping it in my assets folder, and actually writing the bloody code. Especially since I walked out of the office Friday after emailing my supervisor a two-and-a-half page list of stuff I wanted to get done this year but couldn't.
- TallboyOne 14y ago
  You do care about overhead though, right? Bootstrap adds so much unnecessary code you will never use... which is fine for prototyping and bootstrapping, but not for production apps.
  - paranoiacblack 14y ago
    That's fine, but then you do pruning of the elements you don't need. It's a lot easier to prune than to create every single time. I think the overhead added by Bootstrap is easily covered in the amount of boilerplate coding you get to skip.
    - TallboyOne 14y ago
      So you're going to add something only to prune out 85%? It's not likely youre going to keep any of the same styling, button styling, modal styling, etc... I like the approach of just using one of the numerous form boilerplates to make your forms pretty (most time-consuming task I think), and roll the rest from scratch. You can make an entire site responsive in not much CSS at all.
danneu 14y ago
Lots of wisdom here, people. Did your app fail in the market? It's your CSS framework. Write your CSS by hand and win over the hearts and respect of your users. Reminds me of that time my app failed on the market because I left `// Generated by CoffeeScript` in my JS source files and became publicly scorned by my customers for taking shortcuts. I'd write a post-mortem but I'm too busy porting my Rails app to Rack to escape framework overhead like an adult.

LeafStorm 14y ago

I have been using Bootstrap for this entire year on various projects at work. Nobody complained because I was using Bootstrap. In fact, I actually got a lot of compliments about how well the projects looked. The fact is, outside Hacker News, nobody cares if you're using Bootstrap. They care if your project doesn't look horrible, and more importantly, they care if your project works. Now sure, I could learn CSS and do all the stuff you put in the last four sentences. But designing a good-looking style with all the components I needed - grids, buttons, navbars, modal dialogs - would take far longer than unzipping Bootstrap, dropping it in my assets folder, and actually writing the bloody code. Especially since I walked out of the office Friday after emailing my supervisor a two-and-a-half page list of stuff I wanted to get done this year but couldn't.

TallboyOne 14y ago
You do care about overhead though, right? Bootstrap adds so much unnecessary code you will never use... which is fine for prototyping and bootstrapping, but not for production apps.
- paranoiacblack 14y ago
  That's fine, but then you do pruning of the elements you don't need. It's a lot easier to prune than to create every single time. I think the overhead added by Bootstrap is easily covered in the amount of boilerplate coding you get to skip.
  - TallboyOne 14y ago
    So you're going to add something only to prune out 85%? It's not likely youre going to keep any of the same styling, button styling, modal styling, etc... I like the approach of just using one of the numerous form boilerplates to make your forms pretty (most time-consuming task I think), and roll the rest from scratch. You can make an entire site responsive in not much CSS at all.

danneu 14y ago

Lots of wisdom here, people. Did your app fail in the market? It's your CSS framework. Write your CSS by hand and win over the hearts and respect of your users. Reminds me of that time my app failed on the market because I left `// Generated by CoffeeScript` in my JS source files and became publicly scorned by my customers for taking shortcuts. I'd write a post-mortem but I'm too busy porting my Rails app to Rack to escape framework overhead like an adult.