[Mono-list] Please include ASP.NET - Was "ETA to next packagedbuild"

[Simon Waite]

Still it's fair comment, many more people will have downloaded mono,
not got it to work (with their buggy Redhat compilers? etc etc etc)
and thing "bad monos cr*p etc.

However I belive 0.12 is a good place to start - it has some bugs - but
enough to run some simple tests that I've given it. The website didn't
give me any illusions of how mature the product was.

In fact the general advice of "getting the latest stuff from cvs" should
be enough to warn anyone that the product is still in heavy development
and caveat emptor.

Still I'm impressed greatly, and the friendly courteous replies to my mostly
annoyingly newbie question on irc by miguel, raciel, baulig, alp, duncan and
gonzalo (sorry if I've missed anyone out :-) has changed me from eyeing .NET
technology with suspicion, and thinking java will out-last it to someone who
is very close to activly advocating it. I can see my M$ friends saying "I
told
you so" too. - at least I've converted some of them to linux :-)

Excuse the spelling I think I'm coming down with something :(

Regards,

Simon

----- Original Message -----
From: "William Wise" <wwise@cellsignal.com>
To: "Paolo Molaro" <lupus@ximian.com>
Cc: "'Mono List'" <mono-list@ximian.com>
Sent: Thursday, July 25, 2002 11:41 AM
Subject: Re: [Mono-list] Please include ASP.NET - Was "ETA to next
packagedbuild"


> True, as long as the announcement is made on the go-mono home page, the
> release works with the latest runtime release, and good instructions on
> how to set everything up is included in the announcement and
> distribution.
>
> Basically, though, the easier you make things for the end-user the more
> likely they are to be successful quickly with the technology and be
> encouraged to continue their use/experimentation.  Many people have
> short attention spans when trying out new technology and once burned are
> even less likely to try the technology again later.
>
> (I know many potential Linux converts who tried it too soon and have
> set-in-stone opinions now about it's viability.  I know this doesn't
> reflect the general nature of those who inhabit the mono community but
> the more press exposure mono gets the more incumbent it is to make the
> technology easy to use.  People will start to visit the technology and
> if they find it a difficult proposition (compared to a setup.exe install
> on windows perhaps and some double-clickable samples) they may pass on
> it and, worse, share their negative experiences with their peers.  I've
> seen this in the real world especially in regards to desktop Linux and
> it's frustrating.  Mono will always be great for me but I'd sure love to
> see it succeed wildly in the mainstream and help boost Linux!)
>
> Sorry for the diatribe!  I'll go back to lurking on the list now...  :-)
>
> Will
>
>
> On Thu, 2002-07-25 at 13:43, Paolo Molaro wrote:
> > On 07/25/02 William Wise wrote:
> > > Even in an early form I'm inclined to believe that inclusion of the
> > > ASP.NET stuff would be of GREAT interest as even your comments re:
> the
> > > O'Reilly presentation seem to indicate.  Maybe adding a simple
> > > readme_asp.txt file in the root directory with instructions on how
> to
> > > use/test the xsp stuff and a disclaimer re: completeness of the
> > > implementation would be helpful to address the concerns you
> mentioned?
> >
> > The XSP package can be released separately from the rest of mono,
> there is
> > no reason to tie it to the runtime release.
> >
> > lupus
> >
> > --
> > -----------------------------------------------------------------
> > lupus@debian.org                                     debian/rules
> > lupus@ximian.com                             Monkeys do it better
> >
> > _______________________________________________
> > Mono-list maillist  -  Mono-list@ximian.com
> > http://lists.ximian.com/mailman/listinfo/mono-list
>
>
>
>
> _______________________________________________
> Mono-list maillist  -  Mono-list@ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list