Hacker News Reader

Comment by sgdesign | Hacker News Reader

This is not a criticism of this project specifically, but I feel like when you come out with a framework like this you should have a big "Why you should use Framework XYZ instead of Boostrap" section somewhere, because this is the main question most people will have.

View on HN

>but I feel like when you come out with a framework like this you should have a big "Why you should use Framework XYZ instead of Boostrap" section somewhere

This is true for any product whatsoever, not just a framework.

Answer this question, and make it the headline of your landing page:

If I am your ideal prospect, why should I say yes to you rather than any of your competitors?

I think it's fairly obvious as to what the benefit is, considering how many times an app idea that's too "bootstrappy" gets railed on.

This seems like a decent alternative for out of the box design. Once/if this becomes popular then it too could become too standard- but for now, it's very different. That's good.

As far as design is concerned, I think more frameworks in the market is a good thing. The saturation could make the bad designers worse, but it gives good designers just more tools to explore with.

As with industry, competition most often leads to further innovation and drive to improve a product. ;)

Or, why not contribute to bootstrap instead?

more like instead of Foundation since it uses Compass+Sass.

I just glanced at it and it seems extremely close to Foundation, it even uses orbit. I like the tooltips and the forms, the documentation is actually better than the Foundation one. I don't particularly like the grid system as it works in ratio (feels like you have to do more math).

I use Foundation without Compass+Sass. I don't feel it's a vital part of the project.

What's really hard for new frameworks to overcome is the huge community that Bootstrap has created, checkout the big badass list of Bootstrap resources:

http://www.bootstraphero.com/the-big-badass-list-of-twitter-...

That is the first thing that crossed my mind after I bookmarked the site.

This uses Sass, Bootstrap uses Less.

Its pretty easy to switch that now https://github.com/thomas-mcdonald/bootstrap-sass

CMIIW, the project you mentioned is not really usable for customized bootstrap, it's all-or-nothing.

Since I want to include (customized) Bootstrap into Compass but don't use fancy stuff (variables etc), I simply rename bootstrap.css to bootstrap.scss and be done with it.

Is that really that big of a difference? Besides, I thought most people used Bootstrap without Less. At least I do.

Great point! I will work on drafting something to this effect. Thanks for the feedback! :)

May be we need a new layer: a lib to handle different frameworks! like Haxe but for HTML.

In our current project instead of putting the framework's html/css into our codebase I'm outputting as bare bones html as I can with semantic class names on everything and then mapping those classes to the framework using sass mixins/extends/includes.

To make a RWD site I'm having to rewrite a lot of the framework to be mixins instead of classes so that I can use them in @media as SASS doesn't allow @extend in @media any more[1]. What I'd find really useful would be a framework thats entirely built from mixins/partials and outputs no css until you create your own classes that use them.

[1]: https://github.com/nex3/sass/issues/154 Disallow @extend within directives

> What I'd find really useful would be a framework thats entirely built from mixins/partials and outputs no css until you create your own classes that use them.

Here's exactly what you're looking for:

* Bourbon: A mixin library for Sass (http://bourbon.io/docs/) * Neat: A semantic grid framework built on top of Sass and Bourbon (http://neat.bourbon.io/)

And, if you use LESS, you have these options:

* LESS Elements: Mixins library for LESS (http://lesselements.com/) * Semantic.gs: Semantic CSS grid system for LESS (http://semantic.gs/)

Thanks, I'd forgotten about bourbon/neat.

Have you seen sgf4js? (simple grid facade for javascript)

Why I should use Bootstrap?

the actual sensible question would be "..instead of this", and the answer is clearly "because it's been around much longer, many more people use it already".

Bootstrap is the incumbent so other similar frameworks _must_ explain why they are better, or it's the default choice.

Of course if you actually want to know why you should use a framework like bootstrap then you can just read bootstrap's site.

The javascript been written properly?

https://github.com/groundworkcss/groundwork/blob/master/js/g...

(joke, joke! Well, no smoke without fire...)

I'm really hoping the irony of linking to a CoffeeScript-generated JavaScript file and using it as an example of properly-written JavaScript was at least part of the joke here.

CoffeeScript is definitely my language of choice and compiled to highly accurate and optionally minified javascript.

Reply on news.ycombinator.com