arstechnica.com — The Mono project, which builds a cross-platform open-source implementation of Microsoft's .NET framework, has announced the availability of version 2.0. This milestone release delivers compatibility with .NET 2.0 and C# 3.0 on a broad range of platforms and architectures.
Oct 7, 2008 View in Crawl 4
santasingOct 8, 2008
Bulls**t. We don't need mono.As I said, its just another bullet point on Novell's brochure right next to the one that says MS will sue you if you don't buy from us.Mono is slow, its not 100% compatible, the components are not cross platform. Why the hell is Novell and party pushing it down everyone's throats?
flashxOct 8, 2008
For those of you who thinks .NET can take over the enterprise platform is insane. Although Mono has made great strides, it's not going to replace Java in the short run. I have done development in both and although .NET has better GUI tools for drag and drop, I have experienced alot more unsolvable deployment issues on the production .NET servers. Causing hours of downtime. Java is more verbose and most JavaEE servers have great debugging mode making it viable to create solid applications. After all, no corporation is going to risk putting .NET applications on Mono. Java is the only language that actually closest to being portable to multi-platforms. This allows business the flexibility to switch platforms or use cheaper alternatives like Linux or OpenBSD. But I must say, if you are making a quick prototype with GUI, .NET is fantastic for that purpose. Also for people who wants to start learning about programming, it's easy enough to keep someone interested.
netantOct 10, 2008
C is 2030's COBOL. You'll see...Then again, today's "real men" will be neanderthals 20 years from now.But here's to real programmers and real languages.=====But wouldn't it be cool if you could code in C and not have to worry about memory management? Sure its slower, but so is parameter passing. Yeah, I bet you think pass by reference is wussy...Wouldn't it be nice to do Windows development with ease, like scripting? Well, if you know C, and can adapt your approach to C#, that'll save a lot of new language grief, no?
topher06Oct 13, 2008
A for loop is a for loop in any mutha f*cking language buddy.
topher06Oct 13, 2008
Microsoft's whole line of next gen Live apps are going WPF, its the future. There is no forcing of WPF on anybody, but if you want to use antiquated MFC/ATL/Win32 libraries what were poorly implemented in the first place, then go right ahead. WPF, C# and .Net is the first good thing Microsoft has done for application development in their entire history.