Testing Mono's compatibility

[Joshua Zeidner]

> >   Microsoft makes sure that it is far too costly to
> > straddle that
> > technological rift.  Making sure there is little or
> > no skills or code
> > overlap is one way of making sure that people don't
> > think twice about
> > using their platform.  Mono may work well right now,
> > and broad
> > compliance will be maintained until:
> >
> >   1) Microsoft gains a majority share in this market
> > at which point
> > they will then try to incentivize the adoption of
> > their other
> > technologies by offering selective compatibility.
> >   2) Microsoft deems Mono+ASP.NET to be
> > unprofitable.
> >
>
> With all respect, MONO is not an MS project. It is
> open source and sponsored by Novell (who I don't think
> of as MS fans.)

  Does it matter who is 'sponsoring' Mono?  The entire project is
entirely dependent on the edicts of Microsoft Inc.

>
> I'm not offended, but I don't agree that .Net requries
> no skill.

  Who is making this claim?

  I've been through this one on the AZIPA list,  we can have a 'look
what I can do!' conversation and start going through all the great
things that technology X does compared to technology Y,  but I am
discussing long term costs and manageability here.  In the long term
Mono is going to be a monster.  And that is how MS wants it, they want
you to adopt and then eventually switch and completely commit to the
MS platform.  Why would they want anything else?

  In my view keeping your basis OSS results in more market options,
better technological choices, and enhanced competitively for your
business, and that is what I aim give my customers and partners.

 -jmz

-- 
.0000. communication.
.0001. development.
.0010. strategy.
.0100. appeal.

JOSHUA M. ZEIDNER
IT Consultant

++power; ++perspective; ++possibilities;
( 602 ) 490 8006
jjzeidner at gmail.com