To view parent comment, click here.
To read all comments associated with this story, please click here.
No, but we can make sure people are aware of the risk so they make an informed decision.
everybody who is concerned is already aware of the issues. You have no influence
And yes, you will see this discussion come up in every mono-related article until Miguel or someone else at Novell addresses these issues.
And the mono flaming over the years has been a complete failure. Mono is used more than Java ever will be on Gnome. RedHat, Havoc, you, and the others have failed.
Mono adoption is growing, you are right. But why do you gloat over this fact? Seriously, please, tell me why I am wrong to be concerned over mono and the unresolved RAND licensing issues and I will be more than happy to use mono.
Really, mono and .net look fantastic and could do wonders for gnome development. However, as is, using mono is just not worth it.
Until you refute this, which you have not even tried to do (only call people zealots and tell them to shut up), you are very misguided for gloating over mono's successes and redhat's failures.
And, even though mono adoption has increased, it is still largely shunned:
Gnome officially does not allow mono in the core libs. Redhat and most other distros are also refusing to include it. Very few really nice apps have been done in mono. Monodevelop is junk. Sorry. Beagle just doesn't really work day in and day out. Smaller apps like Muine are nice but are hardly enabled by C#. They could have been easily done in another language and in fact there are still many many more new apps in languages other than mono than in mono.
Seriously people like you who dismiss legitimate arguments and concerns with mocking and insults and no actual rebuttal make me sick.
Really, no kidding, you are my definition of an ass hole.





Member since:
>you have no power to stop anybody from using or
>programming in Mono.
No, but we can make sure people are aware of the risk so they make an informed decision.
And yes, you will see this discussion come up in every mono-related article until Miguel or someone else at Novell addresses these issues.