On Tue, May 24, 2011 at 6:50 PM, Richard L. Hamilton <[email protected]> wrote: > Presumably there's a balance with this, as with most things. > > But giving in is not without costs. Making the quarterly look good often > leaves one out of position for the long haul. > > Maybe one could do both. Use familiarity tools, but _only_ as a temporary > measure, while concurrently encouraging native familiarity. Encourage > standards (and the isolation of code that needs to use non-portable > features). Clean code costs less to maintain, gets a better reputation, and > is an insurance policy when the hot platform changes and porting is needed. > >
Having a nice "out-of-box experience" for developers does not necessarily mean providing the old tools. That was not my point. Just a clear, obvious, and guided path to apply existing knowledge and habits to the new environment. _______________________________________________ OpenIndiana-discuss mailing list [email protected] http://openindiana.org/mailman/listinfo/openindiana-discuss
