Hacker News new | past | comments | ask | show | jobs | submit login

This was an easy decision for me a while back. As a non-designer, Bootstrap just gives me way more stuff out of the box. I wouldn't know where to start without it. Even if you use all of Foundation (2)'s add-ons, it still doesn't even compare with core Bootstrap, not counting Bootstrap's add-ons. With bootstrap's popularity, it's really easy to find an article explaining how to integrate it with your framework of choice. I feel for most non-designers this is the deciding factor.

Of course since f3 is almost the same as bootstrap now, I think it's more about personal taste.




As a non-designer that's not really an issue for me. There are so many cheap or FOSS design templates, snippets, icons, etc available these days that it's not a huge problem to put together a package of them for Foundation.

I use Bootstrap when

1. the default Bootstrap theme or a third party theme are sufficient

2. I don't need Foundation's better grid system

3. I'm using something other than Ruby (which for me is most of the time)

Foundation for:

1. There's a specific problem that their better grid system solves. I haven't come across this yet, but am aware of it for when/if I do.

2. Client wants a highly customized Ruby-based site with no hint of the Bootstrap look

As someone mentioned above, you can use Foundation and borrow design and/or javascript elements from Bootstrap and elsewhere if you need to go that route.


Could be just preference or even skills (my front end skills aren't that great), but I find many generic design templates to be not that great visually or a lot of work to adapt to a css framework like foundation. Time is expensive.

I like stuff with batteries included. Given bootstrap's momentum, it even has a plethora of design templates as well so you won't have a generic bootstrap looking site.


Not to pick on you—or anyone else here—but there's a funny idea going floating in the high in this submission and some of the comments.

If I have a large family, I wouldn't really reason with myself saying "You know, it was an easy decision to go with a van as a coupé just doesn't really have enough space." Somewhat different purposes though one can see the overlap, which there is.


I'm not sure if your analogy is fair.

1) Comparing two similar CSS frameworks is different from comparing two very different classes of automobiles that are visually different enough to figure out in less than a second.

2) Not many non-designers look at, let alone even experiment, with enough CSS frameworks for this to be a simple and trivial choice.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: