The Mono Project: You Might Expect the Unexpected (Linux Journal)
The Mono Project: You Might Expect the Unexpected (Linux Journal)
Posted Oct 3, 2007 16:48 UTC (Wed) by k8to (guest, #15413)In reply to: The Mono Project: You Might Expect the Unexpected (Linux Journal) by tjw.org
Parent article: The Mono Project: You Might Expect the Unexpected (Linux Journal)
Portable.NET is a decent project if you like the whole C# world. Their major problems as compared to Mono are completeness and execution speed. That isn't to say the p.net is bad, or not progressing nicely but when you get into a moderate sized programming project you may find it doesn't have enough there.
I certainly learned C# on p.net, it was easier to get running than Mono, certainly for the gui stuff. The dev team was much more responsive, and it seemed like it had made many more sane fundamental choices. I did however encounter various pieces of simple functionality that did not work correctly, implementations of functions that no one could have ever tested. p.net seems more like "an assortment of people programming for fun" sort of effort, while Mono has very focused goals.
My experience with Mono was there was very rapid advancement in implementing the entire library, and many performance issues were being rapidly engaged (not that it was slow to begin with). But when reporting issues like "repeatedly making the same trivial soap call causes Mono's virtual memory allocation grow without bound" were ignored. I do not mean they rotted in a bug database, I mean the developers simply refused to believe this represented a problem. The point is that the project is very internally directed. They know what they need to do, they don't need (or want) your input. In this sense the project is closer to a traditional development model than a community project, although certainly in terms of the nuts and bolts it operates in a completely open way with many contributors.
Posted Oct 3, 2007 17:19 UTC (Wed)
by oak (guest, #2786)
[Link] (2 responses)
Do you have bug link, test-code and maybe also some memory usage graphs?
Posted Oct 5, 2007 5:45 UTC (Fri)
by k8to (guest, #15413)
[Link] (1 responses)
The issue was mitigated but only after the issue went up the food chain at the company I was consulting for and our VP called the Novell VP and etc. This only happened because the bug was blocking the development of a large product at the company I was consulting for. After around 3-4 months of this problem being ignored, after this rigamarole, it did get addressed. In the coporate world of software programming that is *very* responsive. In the free software world, not so much.
Posted Oct 5, 2007 6:19 UTC (Fri)
by k8to (guest, #15413)
[Link]
> But when reporting issues like "repeatedly making the same trivial soap The Mono Project: You Might Expect the Unexpected (Linux Journal)
call causes Mono's virtual memory allocation grow without bound" were
ignored.
It was filed. It had test code. I did not produce graphs. I only tested it until the 4gigs of real memory and 4 gigs of swap were entirely full, and the oom killer finally kicked in. I did produce logs.The Mono Project: You Might Expect the Unexpected (Linux Journal)
And let me add that I find the tendency to *disbelieve* honest problem reports offensive.The Mono Project: You Might Expect the Unexpected (Linux Journal)