I'm coming into this thread kind of late... I just started using the new Gmail "Priority Inbox" and it told me that this wasn't an important thread, so I believed it.
Based on what I've read so far though, I don't see where simply documenting and providing some examples of how to use Nate's .m5 feature doesn't basically address the issue. Regardless of the mechanism we come up with, we're going to have to document it anyway, and a complex mechanism that has documentation with a few concrete examples of how to do the few basic things that most people want to do (that people can copy and paste and edit) doesn't seem harder on end users than a simple mechanism with that same level of documentation. Thus for the same net effort it seems more worthwhile to take the existing powerful but more complex mechanism and put the effort into minor cleanup and documentation than to implement a new mechanism which (unless we put in *more* total effort) will lead to us having two poorly documented mechanisms, with the only advantage being that one of them is supposedly simple enough that the lack of documentation doesn't matter as much. I'm probably mischaracterizing the debate somewhat given my relatively quick read over the thread, but that's my gut reaction. Steve
_______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
