11–17 of 17 posts
Why can't Java people do something like this? I really like what C# people are doing and the language starts to sound really good but unfortunately my work is done with java and *nix so C# is not an option.
Upd: just found an interesting discussion on the topic: http://www.artima.com/forums/flat.jsp?forum=106&thread=1...
Earlier quoted context omitted.
It's actually possible to write slightly less verbose code with C# 3.0. For example: //... char[] someChars = {'A', 'B', 'C'}; var moreChars = new [] {'D', 'E', 'F'}; SomeMethod(new[] { 'G', 'H', 'I' }); //... I do, however, agree with your sentiment. The language still has some aspects that are quite verbose when compared with dynamically typed languages. You are also right in pointing out that these new features ar…
new [] {'D', 'E', 'F'} I thought it was impossible at least in 2.x, is this something added in 3.0?
Cool. Now, if only ASP.NET was "cleaner" and didn't have all that "event-driven" ugliness. More widespread usage on Linux would help too. Mono just hasn't taken off in terms of mainstream production use.
+1. I quite like C#, but it's not enough incentive for me to switch to Windows.
Why must corporate development be so cumbersome? And more importantly, why doesn't this hinder C# where it seems to keep Java so far behind?
Earlier quoted context omitted.
+1. I quite like C#, but it's not enough incentive for me to switch to Windows.
http://www.mono-project.com/Main_Page
That said, I have little experience with Microsoft .NET and Mono so these are the observations of someone only casually acquainted with either project. Can anyone here share any experiences with Mono?
Earlier quoted context omitted.
http://www.mono-project.com/Main_Page
The article is covering features in C# 3.0. Mono is perpetually playing catch up to Microsoft's implementation and according to the Mono site the "Mono API today is somewhere in between .NET 2.0 and .NET 3.5". Besides the fact that the language implementation is behind, developers also have to deal with the fact that the standard library isn't 100% compatible either. It seems pretty clear that C# developers that are…