On Tuesday 20 March 2007 11:43 pm, James Mansion wrote:
> Shuttleworth has illustrated how much value there is in
> strong mangement and leadership, and my concern is
> that by trying to join the 'developer lead' ranks of
> 'just show me the code' cowboys Solaris will lose.

You don't give Solaris any merit on it's technical value and stability, huh? 
What about some of the state of the art technology, like DTrace, or ZFS, for 
instance? I mean it should be easy for folks to copy a 128-bit filesystem, 
Sun even put the code out there, so it shouldn't be hard to reverse engineer, 
you can look at the code. Adding some probes can't be that hard to a bunch of 
libraries, can it? Well, look at System T(r)ap, and how long as the Linux 
community been working on that?

> Linux development in the first of these has tended
> towards professional now, by companies with vested
> interests.  Some of the companies doing this are
> Sun's competitors and won't contribute to Solaris on
> any basis because of brand association.

Really??? Like which companies? The interest I see is quite amazing, companies 
that some folks would have never dreamed would take an interest in 
Solaris/OpenSolaris seem to be showing it.

> Yes, practical people.  Make sure that Solaris is very
> directly aligned with their needs.

It is aligned with the current user base, most of them seem content to run 
Solaris. Many of the new users of Solaris are now seeing enough change that 
we see them changing to use Solaris. In fact, there are quite a few cases 
where people migrate from Linux to Solaris due to stability problems and/or 
binary compatibility.

> Be careful - do you really mean to imply that my expectation
> of an open source product should be lower than it would be
> otherwise?  Is that what Open Solaris is about?

No, I think you missed the point.

-- 

Alan DuBoff - Solaris x86 Engineering - IHV/OEM Group
Advocate of insourcing at Sun - hire people that care about our company!


_______________________________________________
opensolaris-discuss mailing list
[email protected]

Reply via email to