4 ms·

I don't think this is particularly useful. The end result CSS is going to be bloated with large amounts of repeated styles. It also lacks reusable HTML componen

by necolas 15y ago

I don't think this is particularly useful. The end result CSS is going to be bloated with large amounts of repeated styles. It also lacks reusable HTML components. The article references Bootstrap, but Bootstrap still produces a grid that is based on using reusable HTML classes - a better approach. When you're looking at modifying the grid at different viewport dimensions, this grid system looks like it will require you to redeclare every selector that applied the `.column()` mixin.

JoelSutherland 15y ago
I agree. And not to jump on this framework, but you can't just hand-wave away the responsive problem. If you intend to have your site viewed on a phone, you probably don't want to send full-sized assets down the pipe only to have them sized at 25%.
- alanfalcon 15y ago
  I hate abhor mobile formatted sites that only send me an image reduced to 25% of the size. I can zoom in and see full detail on that full sized image when I want to, but only if you send it to me. At least allow me to tap a reduced image to grab the full asset on my phone. [This applies particularly to photos or any images with small text in them.]
  - Chris_Newton 15y ago
    I don't disagree with the case you described, but as a counter-argument in favour of sending customised resources by default, modern sites frequently use things like image carousels or video. In such cases, you are unlikely to benefit from downloading the full-size resource every time, and the difference in file sizes for reduced-resolution resources can make a big difference to costs and caps for both host and visitor (since mobile plans typically have much lower data transfer caps and/or bandwidth compared to fixed line broadband). Also, if whoever is rendering the original material can send you an intelligently customised low-res version, you can still have well-chosen, pixel-perfect presentation instead of relying on your phone to get the aliasing right when it scales an image down without context and showing the whole image at reduced resolution rather than perhaps clipping it more tightly but preseving some important detail.
pygy_ 15y ago
> The end result CSS is going to be bloated with large amounts of repeated styles... Which is why we use gzip over the line. > It also lacks reusable HTML components. I don't get what you mean. They may not be baked in, but it makes it easy to implement them, doesn't it?

by necolas 15y ago

JoelSutherland 15y ago

I agree. And not to jump on this framework, but you can't just hand-wave away the responsive problem. If you intend to have your site viewed on a phone, you probably don't want to send full-sized assets down the pipe only to have them sized at 25%.

alanfalcon 15y ago
I hate abhor mobile formatted sites that only send me an image reduced to 25% of the size. I can zoom in and see full detail on that full sized image when I want to, but only if you send it to me. At least allow me to tap a reduced image to grab the full asset on my phone. [This applies particularly to photos or any images with small text in them.]
- Chris_Newton 15y ago
  I don't disagree with the case you described, but as a counter-argument in favour of sending customised resources by default, modern sites frequently use things like image carousels or video. In such cases, you are unlikely to benefit from downloading the full-size resource every time, and the difference in file sizes for reduced-resolution resources can make a big difference to costs and caps for both host and visitor (since mobile plans typically have much lower data transfer caps and/or bandwidth compared to fixed line broadband). Also, if whoever is rendering the original material can send you an intelligently customised low-res version, you can still have well-chosen, pixel-perfect presentation instead of relying on your phone to get the aliasing right when it scales an image down without context and showing the whole image at reduced resolution rather than perhaps clipping it more tightly but preseving some important detail.

pygy_ 15y ago

> The end result CSS is going to be bloated with large amounts of repeated styles... Which is why we use gzip over the line. > It also lacks reusable HTML components. I don't get what you mean. They may not be baked in, but it makes it easy to implement them, doesn't it?