The people I'm working for/with decided to use bootstrap as a foundation to speed up development. As someone who mainly does "front-end" programming, I don't see much benefit from these "frameworks", especially since we are pretty much redesigning every element. Also, since we are using CSS3/LESS, instead of slicing a PSD I have to recreate every design element from scratch. I hate "designers".
Zurb Foundation vs. Twitter Bootstrap
31–40 of 51 posts
Re: Zurb Foundation vs. Twitter Bootstrap
#32I tried Bootstrap but the semantics are so horrible I couldn't stand using it for more than one project. I love the tools it has but the semantics of the class names are abominable. I've since settled on Foundation as it had the best tools available while maintaining some level of sanity in the class names and semantics.
Re: Zurb Foundation vs. Twitter Bootstrap
#33As someone that deals with markup for the majority of their day I've been bouncing between all of these for the past year or so. I've been using Skeleton for awhile and loved the simplicity. I tried Bootstrap but the semantics are so horrible I couldn't stand using it for more than one project. I love the tools it has but the semantics of the class names are abominable. I've since settled on Foundation as it had the…
Re: Zurb Foundation vs. Twitter Bootstrap
#34Has anyone got a decent solution for combining Foundation and RequireJS?
I can go into specifics if you give an example of the dependency structure you're trying to define. But the basic case I suppose would just be to shim foundation.min.js to depend on jquery.
Re: Zurb Foundation vs. Twitter Bootstrap
#35Re: Zurb Foundation vs. Twitter Bootstrap
#36As someone that deals with markup for the majority of their day I've been bouncing between all of these for the past year or so. I've been using Skeleton for awhile and loved the simplicity. I tried Bootstrap but the semantics are so horrible I couldn't stand using it for more than one project. I love the tools it has but the semantics of the class names are abominable. I've since settled on Foundation as it had the…
Hmm, could you give some examples of these 'abominable class names'?
Foundation: .one.column Skeleton: .one.column Bootstrap: .span1
Then there are various other non-semantic classes: .btn, .pull-left, etc. It seems to me very much a toolkit built with a developer's mind ... in mind.
I like crafting my css by hand, making it easy to read and understand and above all - easy for me to remember so I don't have to crawl through documentation trying to remember if this element is .span4 .span-4 .span_4 or some other permutation I can't remember. I can easily remember .one.column. Its a column and its one.
Re: Zurb Foundation vs. Twitter Bootstrap
#37Earlier quoted context omitted.
What was your conclusion? (Looking at the source code of the page, foundation?)
A few conclusions: * Foundation has the best responsive grid support * Bootstrap is the most expansive UI. For internal tools, that's great. For client sites, we end up fighting to override Bootstrap. * Skeleton is really light. If you're prototyping with Skeleton, you'll probably need to pair it with jQuery UI or something similar. FWIW, we're using both Bootstrap and Foundation for current projects.
Could you describe this more? I didn't really see much about it in your blog post.
Re: Zurb Foundation vs. Twitter Bootstrap
#38Zurb has one thing going for it that really makes a big difference, SASS. From the minute I saw SASS, I became a convert. Also, it's much less all encompassing.
Re: Zurb Foundation vs. Twitter Bootstrap
#39Earlier quoted context omitted.
A few conclusions: * Foundation has the best responsive grid support * Bootstrap is the most expansive UI. For internal tools, that's great. For client sites, we end up fighting to override Bootstrap. * Skeleton is really light. If you're prototyping with Skeleton, you'll probably need to pair it with jQuery UI or something similar. FWIW, we're using both Bootstrap and Foundation for current projects.
For client sites, we end up fighting to override Bootstrap. Could you describe this more? I didn't really see much about it in your blog post.
Bootstrap has a lot of great UI components - form styles, tabs, dropdowns, etc. It looks good, it's consistent, and easy to prototype. But our client work involves highly customized design. In those cases, we don't want the Bootstrap styles, just the functionality.
But overriding Bootstrap styles can be painful. Let's take a form input field. You start by overriding the base style. But you forgot about hover and focus states, so tack those overrides on too. Then add any media query specific overrides. Do the same for any Bootstrap component you used. Finally, make sure your overrides work cross browser.
Building multiple sites with Bootstrap (and likewise Foundation) has definitely made us more aware of costs associated with customizing styles.
Re: Zurb Foundation vs. Twitter Bootstrap
#40I'd have to go with Bootstrap because it just seems to offer more. I extensively use their buttons, warning styles, etc. and it's just better to have those already in the framework just in case. Also on the Foundation website I can't seem to find examples of their typography, buttons and other UI elements.
You didn't try very hard: http://foundation.zurb.com/docs