This is @dhg (creator of Skeleton)and just wanted to say I was pumped to see it on Hacker News. All feedback is well received and I'm actually in the process of releasing an update that will remedy the text-resize issue when font-size is bumped up or down, along with some other small bug fixes.
In terms of fluid vs. fixed I chose to have a set number of fixed resolutions because it allows for a bit more control at those sizes and has a set of associated media query sizes . It also allows for a nested grid which is not really achievable with a fluid grid.
Thanks for the feedback again everyone. I just started a new job that is keeping me busy (in an awesome way), but am going to try to get out an update next weekend.
I prefer the ones that use a mobile first approach, which is more future-proof and is supported on more devices.
Also, another thing to consider is fluid-width vs fixed-width. Fluid width layouts are harder, but much more future proof. The mobile device landscape changes fast, and there are lots of sizes to design for. A fluid-width website would be much better in this case.
Some of these are Gridless, HTML5 Boilerplate and 320 and Up.
320andup takes the best parts from Boilerplate, Mobile Boilerplate as well as the Less Framework for it's grid design and typography. It's fluid and mobile first. To get going with it's grid system however, is actually a pain as it's not pre-defined for you. You'll have to perform some calculations for each media query to get a proper grid going.
Take a look at http://isit2013.org/ to see what I'm talking about, a page I made last year (it uses media queries, but not Skeleton). I'm open to any ideas on improving this site.
@dhg (the creator) seems quite nice and responsive to people tweeting him about it as well, which is a definite plus.
Edit: That is, of course, unless it's something like YAML or SASS or LESS which completely redefine how to write the code.
Isn't the appeal that Skeleton and its ilk simply do the pixel-figuring for you? I similarly have the skillset to make a CSS grid, but I chose to wrap Nicole Sullivan's 20-line grid code in a gem just so I can brainlessly include grid functionality without even touching a CSS file.
It's projects like these that help expose people like me to bare-bones implementations upon which to build.
In particular, this reacts quite badly to zooming, either in a desktop browser (chrome/linux): http://imgur.com/r1z9W or in a mobile browser (android): http://imgur.com/7aP39 .
In the desktop case, the font size doesn't change even if I zoom in the entire page. This isn't the default behavior, so the author must have gone to some lengths to break this functionality. I'm sure s/he had reasons for doing that, but I'm not sure what they were.
In the mobile case, zooming is constrained to a very limited range, and even when allowed, the text doesn't reflow, so it's hard to read lines because of all of the horizontal scrolling required. This behavior is quite common for fixed width, "grid" layouts.
In general, I'm all for frameworks that solve common layout problems, but this particular framework seems to have gotten the basics wrong. I would recommend against using it as it stands.
By "love the scaling", I guess I meant "I love media queries."
EDIT: I was referring to Skeleton, btw