What Do Programmers Like About .NET?

prostoalex writes "Software Development Times did a special report asking the .NET developers what they liked about the platform, since it's been 18 months since the .NET introduction by Microsoft. While the positive responses generally acclaimed Microsoft on integrating C++/C# logic development and VB GUI generation into one environment, some complaints are out there as well. From the article: "When Mark Lindley, manager of development services at Cimco, was working with .NET version 1.0 in September 2002, he needed to implement SSL transactions over TCP/IP. 'It took a long time to figure out that this functionality hadn't been implemented in .NET yet,' recalled Lindley." The article also mentions Honeywell Automated Control Systems, a .NET/J2EE software operation, considering moving their operations to .NET platform."

Comments

i like .NET

[sumho]

it sure beats writing windows programs in win32. the only thing i miss(being a java programmer) is javadocs. i mean come on now, if you're going to clone a language, at least do the whole thing, or you're just going to leave people confused. overall though, .net is a nice thing to use. i do wish it did something better, but you can't have everything.

What I like about .NET

[Inoshiro]

It lets me take most of what I've learned with Java, and leverage it with a faster VM and better environment integration. While applications like MP3 players can get away with looking totally weird, I prefer my applications to be consistent.

Plus, the GUI programming is ultra easy with the model for messages that .NET uses with C# applications. I found it much easier than working with SWING applications.

Too bad that there's not any handy C# environment for Linux that's complete that I know of. I'd really like to be able to write more C# applications, since the language and GUI libraries are such a breeeze to work with.

Re:What I like about .NET

[DevilM]

BTW, the reason for this is that Apple got off their but and made sure Java works like a chap on Mac OS X. They implemented the Aqua LAF using their native widgets, so there is no difference between Java and native applications. The same could have been true for Windows, but obviously Microsoft felt different.

The IDE

[vandel405]

My experience is that C# is pretty good, on par with java. and C++ is C++, MS bastardizes it a little but it isn't that bad. But the major selling point of VS.NET isn't the .NET part, its the VS part.

The IDE kicks ass. it's just that simple. I know you may be able to code like a pro with emacs if you know all of the key combos, but the combo boxes that pop up when you type giving you on the fly documentation and revealing the classes/functions available to you is a god send.

VS is just an awesome IDE that makes up for any short coming of .NET, which i haven't found many.

Re:The IDE

[innosent]

Good point, and you're right. The only other IDE I know of that is IMHO as good as VS is Anjuta. Automatic word completion and pop-up class heirarchies are the most productive thing in an IDE ever created. I can fly through sets of code used on an object in less than half the time, because I only need to type 10 letters on an average line. Things like param = cmd.Parameters.Add("@username", SqlDbType.Char, 15), can be typed in with cmd.P.A("@username", [down 3], 15).

Do that a hundred times or so for different strings or objects, and you'll appreciate it. Don't get me wrong, I type very fast, but why should I have to? Especially on repetitive things like that.

The only complaints I have are in VB, where a lot of things have been removed, and only about half of them are implemented in .NET. Try opening a com port in VB.NET (hint: you'll be using the C APIs the entire time). And no, I don't like VB/C#/VC++, but I do like paychecks.

I totally agree

[GCP]

I've programmed for Mac, Unix, Win32, and Java, and I've never experienced an easier platform for writing GUI apps than the combo of C#, .Net, and Visual Studio. (Now for writing algorithmically challenging apps, nothing beats Lisp, but....)

I think the C# language is a big improvement over Java (the language). So many lessons from years of Java experience have been incorporated into C#, that it's absurd to dismiss it as a Java "knockoff". It's Java done over again with the benefit of hindsight and a lack of legacy baggage combined with the ease of GUI building that made VB so popular (but without any trace of Basic).

Of course, the fact that it's realistically only for Windows (so far) is a huge drawback (for me). With Java, you can hop from platform to platform and from tool vendor to tool vendor (incl. open source) as they come and go, and there's a lot of security in that. (I seem to change Java IDEs every 18 months or so, and I like that I can do that.)

If both C# and Java were equally cross-platform and there were good C# tools from vendors other than MS, I'd choose C# over Java in a heartbeat for the language improvements alone. If I'm assured that the client wants Windows only, I'll use C# for sure. When I don't have that assurance, I'll stick with Java for safety. (Of course, if it's not a GUI app, and I don't need the type of safety you get by using a mainstream language, I think some form of Lisp or ML would be my first choice.)

Re:So it's just a VB replacement?

[hoggy]

I don't really like C# because it just seems to be an inferior Java clone.

Looking at the upcoming 1.5 release of Java, it seems to me that Java is copying features from C#. From a Sun article on what's new in Java 1.5:

Do you want to give us a simple take-home message for each of the six areas of improvement?

I'll give it a whirl...

Generics - Provides compile-time type safety for collections and eliminates the drudgery of casting.

Enhanced for loop - Eliminates the drudgery and error-proneness of iterators.

Autoboxing/unboxing - Eliminates the drudgery of manual conversion between primitive types (such as int) and wrapper types (such as Integer).

Typesafe enums - Provides all the well-known benefits of the Typesafe Enum pattern (Effective Java, Item 21) without the verbosity and the error-proneness.

Static import - Lets you avoid qualifying static members with class names, without the shortcomings of the Constant Interface antipattern (Effective Java, Item 17).

Metadata - Lets you avoid writing boilerplate code, by enabling tools to generate it from annotations in the source code. This leads to a "declarative" programming style where the programmer says what should be done and tools emit the code to do it.

Besides generics (due in the next C# release) and static imports, enhanced for loop, autoboxing, enums, and metadata are all features of C#.NET. Frankly, I think the .NET metadata system is substantially better. I also like delegates far better than anonymous inner classes, which I consider to be a sledgehammer to crack a very small design pattern.

Exactly what do you find to be inferior?

Your tools provider is a business partner.

[Futurepower(R)]

"The articles you linked to are simply irrelevant to the .NET discussion."

Your tools provider is a business partner. You should definitely worry about the reputation of your business partners. They will not treat you better than they treat everyone else.