[Mono-list] Suitability of Mono
stifu at free.fr
Fri May 20 08:29:26 EDT 2011
How about trying your .NET app with Mono? That'd be quite a good test.
Anyway, wouldn't trying to fix the performance issues of your app be a
priority over adding more features?
By the way, Mono is an open source project, and Attachmate can't do anything
about that. They only own the commercial Mono products. For the record,
Attachmate has fired the whole Mono team, which led to the creation of
Yogi Yang wrote:
> I am new to Mono. Not actually totally new but actually have never used
> Mono for developing any serious app.
> Just recently I was assigned to task to evaualte Mono for our up coming
> project which is a document management system for small enterprises.
> We have burnt our hands with .NET (we have developed a semi DMS using .NET
> 2 and firebird and/or MS SQL server as back end). I am saying burnt our
> hands, because under heavy user load the system just does not perform well
> and becomes sluggish.
> Now we want to update this semi DMS to a full featured DMS by adding many
> features like OCR (full and zonal), user rights, directory monitoring for
> new files, integrating with Open Office, etc. etc.
> I am told by my boss to evaluate Mono whether it will be suitable for such
> a complex system or not?
> But then while searching on net I read somewhere that Mono's future is not
> very clean now that Attachment has acquired it.
> I would like input from community on this.
> Is choosing Mono the best thing esp. when we want to develop a multi OS
> based software or not?
> Can someone please give unbiased opinion please?
View this message in context: http://mono.1490590.n4.nabble.com/Suitability-of-Mono-tp3538305p3538363.html
Sent from the Mono - General mailing list archive at Nabble.com.
More information about the Mono-list