• # April 5, 2013 at 7:25 pm

    So what is the general consensus with frameworks? Should we be using them?

    I admittedly haven’t played around with most of them but I find the ones I have used very interfering and add a lot of code that isn’t needed.


    # April 5, 2013 at 9:12 pm

    This reply has been reported for inappropriate content.

    Blueprint. Hands down.

    Download here:

    Cheat Sheet here:

    # April 5, 2013 at 9:13 pm

    This reply has been reported for inappropriate content.

    And yes, in my opinion, they’re better used than not. No matter how bad ass you are at writing CSS, it’s very unlikely that what you write is going to be as good as a tried and true, battle-tested opensource framework.

    Just my thoughts.

    # April 5, 2013 at 9:53 pm

    I completely, but respectfully, disagree with you tanner.

    # April 5, 2013 at 10:29 pm

    I agree with @wolfcry911. Absolutely hate them. I do, however, include normalize.

    I feel like the CSS that I write will be *infinitely* better than a framework.

    # April 5, 2013 at 11:56 pm

    Right there with @wolfcry911 and @TheDoc. I use normalize but I absolutely hate having to reverse engineer other people’s stuff or deal with the unnecessary bloat/crap classes that are present in many frameworks.

    # April 6, 2013 at 1:57 am

    This reply has been reported for inappropriate content.

    I’m crying right now.

    # April 6, 2013 at 6:37 am

    > I completely, but respectfully, disagree with you tanner.

    Same here.

    Sometimes you need them, but definitely not always. To be used when required, not systematically.

    # April 6, 2013 at 9:00 am

    This reply has been reported for inappropriate content.

    I get the feeling they are more for developers who lack decent design/css skills?

    # April 6, 2013 at 10:03 am

    No. There are situations where you better have a framework.

    # April 6, 2013 at 12:55 pm

    This reply has been reported for inappropriate content.

    @jshjohnson, HOW DARE YOU! :)

    # April 6, 2013 at 6:15 pm

    There is almost always some CSS you use in every project, if you make that easily reusable you only have to write that once, your own ‘framework’. That, and normalize (I remove the parts of normalize I overwrite in my own CSS though, saves a kB or two ;) )

    @tannercampbell, your comments here made me lol :P

    # April 6, 2013 at 8:50 pm

    @tannercampbell, I love frameworks too.

    I’m relatively new to web development (about 18-months now). My first live client site was launched last May. It was responsive and a custom WordPress theme, and IMHO surprisingly decent, thanks to Zurb’s Foundation and Themefortress’ Reverie theme.

    Each time a project winds down, I’m positive that the Foundation Framework allowed me to focus on some unique challenge (i.e. javascript, which I struggle with, or some unique piece such as the super-responsive homepage on vs. getting lost in creating everything from scratch. I made the jump over the holidays to Foundation’s SCSS/Compass gem, which is also very good, and helped get me up and running with SASS which I love.

    Undoubtedly, these sites are heavy with unused CSS. That is starting to bother me more, but not enough to stop using them. I’m trying out Skeleton for a new project which is all about being lean. But may go back to Foundation. Or I may check out Blueprint.

    I think Frameworks help a lot, and I’m grateful that Framework authors share their secret sauce and extensive experience.

    # April 6, 2013 at 9:05 pm

    I’ve never had to use one and probably never will. The one time I looked at several of them, it was a bloated mess with classes that didn’t make a lot of sense to me. I like to think I’m pretty good with CSS and I actually enjoy writing lean and efficient CSS on a per project basis. I don’t like grid systems because they class things with columns and things that aren’t true in a responsive layout. Just because its 5 columns or 30% at desktop size, doesn’t mean it’s the same proportions at mobile sizes. I rarely even uses classes and IDs because I can target most things with clean HTML selectors. Anyway, I’ve only ever worked on one corporate level site that used blueprint and it was a friggen nightmare. I really only ever work on small to medium sites, so writing only what’s needed suits me better. I do use a version of Eric Meyers reset that I modified, but that’s a pretty small chunk compared to Bootstrap or Foundation. Just my thoughts, but CSS is so fun to write… Why doesn’t everyone love writing it!

    # April 7, 2013 at 4:12 am

    I took normalize and the default style sheet from html5 boilerplate, stripped and edited a little and just use that as a starting point. It did have a grid system in it until a few a years ago but it’s pretty pointless now.

Viewing 15 posts - 1 through 15 (of 36 total)

You must be logged in to reply to this topic.