> The former is much easier if (and when) there's > nobody left who > understands or cares about that custom code.
What happened to the quality documentation and self-documenting code interspersed with useful comments? > Of course, you're always free to start you _own_ > installer project and > dedicate it to Saving The Bits. If there are others > who agree with > this view, perhaps you'll have some help. It's really not about "saving the bits", honest. I do however care about efficiency and elegance. > It sounds like you've never had to maintain this sort > of cruft over > time. No, I haven't. I document everything religiously; apart from a quick PoC prototyping, I don't start anything without having written a formal specification first. And this is for my private stuff at home, not work! I did just fix someone else's prototype code for instantiating zones, that wasn't shall we say, 'optimal'. Does that count? Not only did I fix it, I also wrote a clean version of it and delivered that along with the fixed one. Does that count? > Please do. Complaining from the sidelines because > you feel your needs > aren't being addressed -- worse, doing so on an > unrelated mailing list > -- is rarely effective. Ultimately, no matter how you put it, how you slice it and how you dice it, it's always going to boil down to one thing: am I giving my customers what they want, the way they want it? And indeed, OpenSolaris would be wise to bear that goal in mind at all times. The most successful projects and products are successful because they give their customers what they want, how they want it. This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list [email protected]
