On 5/17/07, James Carlson <[EMAIL PROTECTED]> wrote:
Ian Murdock writes:
> (And, once again, I'm not sure I see anything here that isn't fixed
> with a "Solaris classic" environment.)
Do we force future project teams to test in both environments?
I don't see why. If both environments are present, can't the application
pick which one it wants to use? Classic is the default, so that existing
apps don't break (the driving reason not to change things according to this
thread). Interactive sessions are applications in a sense, and the user
gets to decide which environment they want in that particular case.
What environment an app runs in is orthogonal (and likely transparent).
Yes, I'm no doubt oversimplifying, but this doesn't seem like an
intractable problem. The only incremental burden is testing the
interactive environments, i.e., the additional burden scales
linearly, no exponential complexity blowup. And by definition,
the classic environment doesn't change, so there's
really very little additional testing to be done there. Right?
-ian
--
Ian Murdock
650-331-9324
http://ianmurdock.com/
"Don't look back--something might be gaining on you." --Satchel Paige
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
