I see no reason to use additional mechanism. Why not use upvote? I'm upvoting stories so I could see them later (as ColinWright noted), why not create a page I could see comments I liked?
Really, could anyone handle more than a few layers at the same time? It is sometimes useful to know how hardware (I'm looking at you, L2 cache!) works, but even then a bit simplified version can do the job.
And from time to time there comes another layer on top of everything else, and you wish you could forget the lowest layer you know, just to not start going insane. Or at least to slow it a bit :)
I agree, but this should have been from the start, or at least from UNIX-Internet marriage. My point was little tongue-in-cheek, but I believe that during the years UNIX has got things that are not truly with their initial idea. Or little more interfaces than necessary.
It exchanges one form of duplication for another, not eliminates it.
The real "problem" is that textual code is generally one-dimensional in nature, but we are interweaving two dimensions of option combos. It's allegedly a limit inherent to textual code, regardless of paradigm used to write the code.
I'm currently thinking of language with "code" laying in database of sort, and text is just a view of real data. Of course, there would be some text serialization, but it wouldn't be the "true way" for programming it...
Only one thing I would suggest really - width of linked Stypi page should have some reasonable maximum width, something close to 80 chars. Otherwise, it is really hard to see where all changes are made when browser is maximized.