.NET is evil.

[Robby]

Originally posted by Heiko
.NET is slow.

I can not recall to ever have worked with an IDE that needs to contemplate 10 seconds over simple cut & paste questions.

Apart from that ... it*s ok

There must be something wrong with your system.

I find that 2002 has better intellisense (VB) then 2003. The Find/Repplace also.

 

[cyclonebri]

bri189a said

Yes C# is the ultimate language for me. Low-level enough to do cool things and keep the idiots out, but high level enough that you dont spend a day just get the objects on your window to show up, much less work correctly. Now C++ (and Assembly for that matter - yes I fiddled in that a little bit for fun) are something I play with as a hobby. C# is what I moonlight with.

I couldnt agree more with the comments on C#. I have also switched from VB to C#, for almost exactly the same reasons. I am glad to get the power of C and the RAD of the .Net IDE. It has been nice. Now if Microsoft would just quit coming out with new Studios every year...

 

[Nerseus]

Now if Microsoft would just quit coming out with new Studios every year...

As long as they keep fixing them and making them better (there are still a number of troublesome bugs), let them come out every year (or sooner)!

Anyone remember VB4? By the time my company ran through the first phase of conversion from a VB3 project, they were already up to VB5. That was a whole new, major release (using version number as a "major" release). I believe it was a little under a year for that one, too.

.NET evil? Maybe. I think its fun, as do most of you - or else we wouldnt be here talking about it

-Nerseus

 

[cyclonebri]

As long as they keep fixing them and making them better (there are still a number of troublesome bugs), let them come out every year (or sooner)!

Dont forget offering them at substantial upgrade discounts, like the 30 dollar deal that was going on earlier...or better yet, something that is free like webmatrix, only as powerful and complete as VS.nets IDE.

 

[wyrd]

Both Java and C++ have the keyword this.

 

[cyclonebri]

C#.net also includes the this keyword, instead of the me keyword which is used in vb.net.

 

[hog]

I love .NET. I love Microsoft. I love all the help files that keep me from polluting this board with all but the more difficult questions (wish others had that mentality).

Sometimes it is far quicker to ask the forum than to drudge through the help. I do look through the help a lot but then again a lot of the times you get passed from pillar to post so many times you end up forgetting what it was you were originally looking for

I think .NET is fandabbydosey, yes it does make life so much easier and hey why not.....why reinvent the wheel if someone else has already done it....use it

Apart from ripping of games that is....comon Liu ya could have at least changed the splash screen or somthing

 

[Banjo]

Part of the trick to using the help system is to read the articles. They give you a lot of information about how things slot together, including practical examples.

 

[Darc]

I have a question... Ive used VB .NET for a while, and I have C++ .NET (I only really ever make Win32 apps with it though). Is it worthwile to go get C# .NET or to learn C++ .NET? VB .NET was my first language when I started a month ago, but it now seems a little slow for gaming uses. Input?

 

[AlexCode]

For gaming uses you shouldnt find any diference between VB.net and C#... Its basiclly a language option. Althogh if you want to play "out" of the framework C# gives you a small oportunity, giving you the ability to call "unsafe" code and C++, that putting it in a simple way, do whatever you want!

In my idea, choosing between them its just a matter of productivity.


Alex

 

[goodmorningsky]

Hi, all.
This thread is the most popular debate at the year when the .NET comes out.
There are lots of software engineers with .NET and against .NET.
I feel like that
those who work with Microsoft technologies like .NET but, others are against it.
Since, as you all heard, the architecture of .NET is tween of Java technology.
Because .NET was planned after MS was sued by SUN regarding that MS used Java as a core part for Biz component development, and MS paid several millions to SUN. Then MS started .NET to bit SUN.

If you guys interest about .NET features, its good to learn Java or read articles comparing .NET and Java..

You will see nothing in .NET is new to Java developers, but brand new to MS developers.

 

[Robby]

Ive done more than enough JAVA.

Perhaps reading this will shed some light, by the way its written by a JAVA guy and hes not a Microsoft patriot ....
http://www.exia.net/html/app/sitecontent/CGI Dot Net vs J2EE.pdf

 

[Divil]

Its interesting, that when Sun won their case against Microsoft, they effectively sealed Javas fate - at least on the client side. Being distributed with Windows is the best thing that can happen for a product, and thats not allowed any more.

 

[Derek Stone]

Sun has made a lot of poor decisions over the last few years. The fact that they still talk out of both sides of their mouth regarding Solaris and Linux is just one example.

 

[Tryster]

I think one ot the key things to bear in mind is that Longhorn is being build from the ground up around the .NET philosophy.

Indeed, if you believe the hype the .NET FW will eventually replace the Win32 layer. Just because currently MS has chosen to implement a lot of its classes on top of Win32 (probably for speed of development) does not mean they will continue to do so in the future. Essentially Win32 is a wrapper around calls into the kernel, so as new kernel calls are added in Longhorn and beyond, it makes sense that the associated .NET classes will make these calls direct to the kernel. As such I think well see (on the Windows platform at least) .NET performance getting better and better.

Additionally, with longhorn and beyond the framework will become part of the operating system, (much as Win32 is now) and we should see performance gains from this...