CSS 'frameworks' are missing the point (2008)
stackoverflow.com
CSS 'frameworks' are missing the point (2008)
1–10 of 44 posts
Re: CSS 'frameworks' are missing the point (2008)
#2Stackoverflow had sense enough to close it as flamebait.
Re: CSS 'frameworks' are missing the point (2008)
#3When paired with less/sass, css frameworks can be used to build up your site without inserting non-semantic classes into your html (by using mixins/functions).
Re: CSS 'frameworks' are missing the point (2008)
#4Completely invalid advice in 2014. LESS and SASS now provide everything that CSS "can't do" in this answer.
Re: CSS 'frameworks' are missing the point (2008)
#5And the lie detector determined that was a lie.
Re: CSS 'frameworks' are missing the point (2008)
#6Completely invalid advice in 2014. LESS and SASS now provide everything that CSS "can't do" in this answer.
LESS/SASS are not what the post is referring to.
Re: CSS 'frameworks' are missing the point (2008)
#7IMHO, the only ones that are "useless" at least for me, are the one that force design decisions on my project, that why i end up using my own rules or just use inuit.css if a feel lazy.
Re: CSS 'frameworks' are missing the point (2008)
#8Re: CSS 'frameworks' are missing the point (2008)
#9Completely invalid advice in 2014. LESS and SASS now provide everything that CSS "can't do" in this answer.
This has nothing to do with transpilers.
Re: CSS 'frameworks' are missing the point (2008)
#10Completely invalid advice in 2014. LESS and SASS now provide everything that CSS "can't do" in this answer.
I assume it's been posted here to show how much the thinking has changed since 2008.
Not just with the precompilers - LESS/SASS/Stylus - but with the overwhelming amount of web apps being developed with modern CSS frameworks like Bootstrap and Zurb Foundation.