Bootstrap 3.1 released
41–50 of 138 posts
Re: Bootstrap 3.1 released
#42Love the Sass port. My one complaint with Bootstrap is that its grid system uses float instead of inline-block. Is it easy to use a different grid system with Bootstrap without breaking its other components?
Disclaimer: I helped write Pure
Re: Bootstrap 3.1 released
#43Bootstrap seemed a bit like overkill when I had to use it in my old job. The CSS and markup seemed excessive, and the strict JS was kind of a pain to deal with.
I know I can get something that looks half-decent up and running quickly with it, but if I'm not planning to take any visual design from it, is there much of an advantage? Is Bootstrap's grid so great in any way that I really should be using it?
Re: Bootstrap 3.1 released
#44Official Sass port. That's pretty big news.
The main reason I chose LESS was because of bootstrap support, I'm extremely happy with it and can't believe I didn't start with it before. I'll see how this port goes, but I've read some good stuff about SASS: http://css-tricks.com/sass-vs-less/ Any other points anyone can make for SASS against LESS?
Also, Compass[1] is awesome when working with sass, but I don't know if there is a less equivalent.
Re: Bootstrap 3.1 released
#45Re: Bootstrap 3.1 released
#46Question: If you were developing a large, content-driven site, would you bother with Bootstrap? Bootstrap seemed a bit like overkill when I had to use it in my old job. The CSS and markup seemed excessive, and the strict JS was kind of a pain to deal with. I know I can get something that looks half-decent up and running quickly with it, but if I'm not planning to take any visual design from it, is there much of an ad…
The grid in the Boostrap 3 is pretty useful if your requirements are for a responsive layout. It really makes it pretty simple to get things going, but does pollute your html with a lot of cruft as you sometimes need to define each size within a single class attribute.
One other thing I've found is that it makes the site more maintainable, as it's easier for others to understand your CSS and layouts. It's the equivalent to being able to hire a Java programmer that knows the Spring Framework (they're plentiful, and usually know enough to not break things). The same is the case for Bootstrap. By having a common and popular framework, you have more developers that can jump right into your front-end quickly.
Also, it's easy enough to customize[1] to get only what you need. If all you need is the grids, just remove everything else. No need for the js components.
Re: Bootstrap 3.1 released
#47Question: If you were developing a large, content-driven site, would you bother with Bootstrap? Bootstrap seemed a bit like overkill when I had to use it in my old job. The CSS and markup seemed excessive, and the strict JS was kind of a pain to deal with. I know I can get something that looks half-decent up and running quickly with it, but if I'm not planning to take any visual design from it, is there much of an ad…
Re: Bootstrap 3.1 released
#48Meanwhile: youmightnotneedbootstrap.com
Re: Bootstrap 3.1 released
#49Re: Bootstrap 3.1 released
#50Question: If you were developing a large, content-driven site, would you bother with Bootstrap? Bootstrap seemed a bit like overkill when I had to use it in my old job. The CSS and markup seemed excessive, and the strict JS was kind of a pain to deal with. I know I can get something that looks half-decent up and running quickly with it, but if I'm not planning to take any visual design from it, is there much of an ad…
Get normalize.css
If you really need grids, you can get a lighter framework.