Hi David, The first thing that i should say is: please put that coffee mug on your table sloowwly. Okey, are you feeling better? Now listen; being a person related to software development, me and many guys like me follow this list. My condition at the moment requires that i should use both .NET and Java. If i find myself in a situation that makes me feel like mono is the best choice, than i use it. If you can calm down for about 2 minutes or something like that, you can see that i did not say that everyone else should be marching toward novell building with grenades. I just said that in my position mono is not usable. In future, you may consider discussing about a subject without considering everything else your opinion as FUD, and believe me it is a much better way to share your thoughts. There are pieces of comments in your message that I feel like discussing, but I don't need any more of this... I am sorry that i am contributing to an unnecessary conversation, and I appologize from everyone else but I felt that I should reply to clarify this issue. Unless anyone else has opinions to share on this topic which does not envolve blaming other people for commenting on a piece of technology, this topic is also over for me. Seref David P. Bowler wrote:
Its quite simple... If multi-platform development is of vital importance to you, why are you wasting time on a dotNet list? Java gives you what you want. Don't have the time or resources to retrain your organization on Java but still need to explore other platforms? Then you'd better see whether what YOU do in dotNet is ready on Mono. Sitting on this list and trying to convince people that Mono is the wrong answer because it didn't work for YOU AND THE SPECIFICS OF YOUR SITUATION is wasting everyone's time. If you don't care about ever moving to another platform? Great! dotNet solves all of your problems by itself. I envy you. MS-Only shop but curious about whether Mono might be helpful to you or open new opportunities never available before? Then check it out for yourself. For every BAD thing said about Mono here, I could dig up a successful story of ports. Some of which are MINE and seen/typed firsthand. Mono will not solve everyone's problems. But it will certainly solve many of them. I read people complaining about whether EnterpriseServices have been ported... Does everyone USE them? Is anyone here suggesting Mono REPLACE dotNet in your shop? If they did, I must have lost that message. If dotNet works for you and your needs, then you are set. If your needs GROW, or you wish to investigate new opportunities, then Mono is there and getting better every day. In an earlier exchange, someone stated some "fact" about Mono that was later admitted to be based upon 2 year old knowledge. I find that "pattern" typical in these debates. I'd encourage every technician here to check it out FOR THEMSELVES as to whether its appropriate for their needs. I'd likewise say that if you have no need for other platforms and no plans to pursue them, then dotNet and its development tools are superior. REPLACING dotNet with Mono on the windows platform is, IMO, silly, but again, don't take my word for it, check for yourself. I do not WANT to be a Mono advocate here. But, I will not let FUD get dumped around without response. This notion that its dotNet vs. Mono is silly to me. Mono ENHANCES dotNet. Mono is a testament to MS's wise decision to create open standards for their development platform. If there is ANY "versus", I only see dotNet/Mono vs. Java... But, again, read for yourselves. Just don't buy into the FUD here. I am done with this topic. =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
-- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.1/354 - Release Date: 01.06.2006 =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
