> Consistent with what? URIs? or DNS, which is what SGI apparently did?
Consistent with the commonly accepted notation: Product.Subproduct.Fileset AIX does it. HP-UX does it. IRIX did it. Why would Solaris have to invent something new in that regard? > http://en.wikipedia.org/wiki/Uniform_Resource_Identifier is an > interesting read > in this context. And so is the rule of least surprise: "Rule of Least Surprise: In interface design, always do the least surprising thing. The easiest programs to use are those that demand the least new learning from the user ? or, to put it another way, the easiest programs to use are those that most effectively connect to the user's pre-existing knowledge." And then it goes on to state, among other things: "Pay attention to your expected audience. They may be end users, they may be other programmers, or they may be system administrators. What is least surprising can differ among these groups." I would argue that your target group is primary system administrators. End users won't care, because for them, it will be different, no matter what you deliver. But for sysadmins, it will matter. A lot. If anything, it should lighten the adoption. And we know from experience, details are just as important as the big picture. What else must I do or present to convene my point and to convince? _________________________________________________________________ Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/desktop-discuss/attachments/20080402/7ac21ecf/attachment.html>
