Shame.css
csswizardry.com
Shame.css
1–10 of 57 posts
Re: Shame.css
#2Brilliant idea! Best thing I read on HN today.
Re: Shame.css
#3This is a really indirect and complicated alternative to putting FIXME comments into the source.
Re: Shame.css
#4Some of this can/should be done via a CSS system like SASS/Compass. If you're littering overflow:auto into a dozen rules, SASS/Compass would probably help you immensely. When you eventually decide IE6 support isn't needed, flip a single variable and poof--those rules disappear.
You could extend this to a _shame.sass file too, of course.
Re: Shame.css
#5There was a similar idea floated by Yehuda Katz by putting a "cruft" file in a source-code repository that lists all the crufty things that need to be taken care of.
Personally I like it, while some people like putting TODOS in the code (and I do it as well) having a specific cruft file (or shame.css) allows you to put in non-code related stuff and comments at a more over-arching level.
Re: Shame.css
#6This is a really indirect and complicated alternative to putting FIXME comments into the source.
I find that I rarely fix things marked with FIXME comments. I've had much better success with a 'throwaway.css' file. The idea that a client would load a file with that name on a finished product is distasteful enough for me to want to revisit those hacks.
Re: Shame.css
#7This is a really indirect and complicated alternative to putting FIXME comments into the source.
I don't think it's either indirect or complicated. It's just a file concentrating the FIXME instances that would otherwise be scattered and require a project-wide search.
Simple and elegant imho. That said, I wouldn't use something like that in a project without a build step that merge stylesheets together.
Re: Shame.css
#8There was a similar idea floated by Yehuda Katz by putting a "cruft" file in a source-code repository that lists all the crufty things that need to be taken care of. Personally I like it, while some people like putting TODOS in the code (and I do it as well) having a specific cruft file (or shame.css) allows you to put in non-code related stuff and comments at a more over-arching level.
Personally, I use an Org Mode file, which allows me to organize crufty stuff, design/architecture overview, and future goals all in one place.
Re: Shame.css
#9Pedantry: can we call it "guilt.css" instead? In psychological literature, guilt is defined as the "I did something bad" emotion, shame is the "I am bad" emotion. The crucial difference between them is that guilt can be fixed by making amends. That seems like exactly the mindset you want to encourage with this: guilt.css implies that you feel guilty about all the hacks you have and want to make amends, while shame.css implies that your codebase is a steaming pile of shit.
Re: Shame.css
#10Why is overflow hidden a hack?