Why .NET?
-
atleast they named it "C"#. somewhat encouraging to look at. BTW, why not you add a "C#" to your skill set?? you are not going to forget those sweet memories of Win32,C++ by learning C#. and C# is more supportive to C++ developers than VB programmmers. and learning dot net is as simple as that. huhhh you know this is how i'm trying to make up my mind, damn, when i took up VB as my main skillset(without knowing what the hell was that) during my college days, people were talking high about VC ... and due to attraction ,I jumped into VC,(and ultimately fell in love with) and crapped VB totaly. now VB is taking its revenge on me, every dumb VB programmers (my old colleagues) have just suffixed a ".net" to their VB. and they are looking at me like. "are you still working with VC.6 ?? MS has stopped supporting it. dont you know that??:-O:->:-O"... sh*t, i'm saving my face with the VC7 compiler.:sigh:, atleast MS managed to include it in the VS2003. now i'm planning to learn C# :(
VuNic
Yep, but you sure can tell when a naive VB programmer is writing in .NET.. Ryan
"Michael Moore and Mel Gibson are the same person, except for a few sit-ups. Moore thought his cheesy political blooper reel was going to tell people how to vote. Mel thought that his little gay SM movie about his imaginary friend was going to help him get to heaven." - Penn Jillette
-
Look at the bright side. At least you're not alone. :~ Jeremy Falcon
-
I wrote:
Why doesn't Microsoft do that? [Why don't they create a really good framework in native code?]
Ryan Binns wrote:
What language would you do it for? Whichever one they chose, they would have developers in the other languages screaming for blood. The way they have done it, they make the framework available to everyone.
Well:
Ryan Binns wrote:
They know that there are classes of applications that will see no (or little) benefit from moving to a .NET platform.
What languages are those classes of applications written in? My guess is 98% C++ (and 80% of those use MFC). Ergo: the language would be C++. Why not give us something like MFC but 1000% better. I'd say all other languages are much easier to replace with the .NET framework. But being a C++ developer I don't know for sure (oh I'm so humble :rolleyes:). /Simon This is not a signature.
Simon Hofverberg wrote:
Why not give us something like MFC but 1000% better.
Because it already exists. Look at VCF or wxWidgets for example - and they are both cross-platform. The number of VB developers is far greater than the number of C++ developers for Windows. Simple economics (of which Microsoft is the master) dictate that that is the market to target the most. They support VB for the majority of programmers, created C# for those who like Java or C++ developers who don't mind using the best tool for the job (yes, slightly tongue in cheek, I know), and have left in C++ support for those that want/need it. Personally, I think they made a good decision. I have used .NET very little and probably will very little in the future, but it's good for what it is.
Ryan
"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
-
norm.net wrote:
If you writing an Stock Inventory System .net/C# is the man.
And yet nobody said that about Java or classic VB. Both of which were capable of delivering products faster. Jeremy Falcon
-
Yep, but you sure can tell when a naive VB programmer is writing in .NET.. Ryan
"Michael Moore and Mel Gibson are the same person, except for a few sit-ups. Moore thought his cheesy political blooper reel was going to tell people how to vote. Mel thought that his little gay SM movie about his imaginary friend was going to help him get to heaven." - Penn Jillette
-
norm.net wrote:
mission critical
I woul dget rid of Windows if that was the case. No, perhaps NT4 sp6a tightened up to Military spec might do, but then again, didnt that US Frigate drift around the ocean for a few days while they worked out how to bring the NT system that ran the whole boat bacj up? Perhaps I would just get rid of Windows. Anyway, if you want fast, then C is better than C++, but, dont forget the compiler, if you have a bad one you are better off in assembler. Nunc est bibendum
fat_boy wrote:
No, perhaps NT4 sp6a tightened up to Military spec might do, but then again, didnt that US Frigate drift around the ocean for a few days while they worked out how to bring the NT system that ran the whole boat bacj up? Perhaps I would just get rid of Windows.
Wow! There goes your pay cheque. Blogless
-
Jeremy Falcon wrote:
And yet nobody said that about Java or classic VB. Both of which were capable of delivering products faster
Both equally shite as languages ;P Blogless
norm.net wrote:
Both equally shite as languages
One could argue the same thing of .NET. :) Jeremy Falcon
-
Yep, but you sure can tell when a naive VB programmer is writing in .NET.. Ryan
"Michael Moore and Mel Gibson are the same person, except for a few sit-ups. Moore thought his cheesy political blooper reel was going to tell people how to vote. Mel thought that his little gay SM movie about his imaginary friend was going to help him get to heaven." - Penn Jillette
That's one thing I always found odd. Most classic VB teachings never really discussed design principles/patterns, and well, it shows. :) Jeremy Falcon
-
norm.net wrote:
Both equally shite as languages
One could argue the same thing of .NET. :) Jeremy Falcon
-
I posted this in the General discussion forum, but it didn't quite stir up the flame war I expected. After seeing Vista and .NET and Microsoft's Response to Vista and .NET I figured this is the place to go. So ... I use MFC (though I don't particularly like it) and VC++ 6.0 (which I like very very much). I've spent a lot of time trying to figure out why Microsoft (and a whole lot of people affiliated or not affiliated with them) think that everyone should switch from native Win32 C++ development to .NET Framework-based development ... and I just can't figure out why. Things I know: Yes - the .NET framework has a load of nifty classes that I would have access to. Yes - it's quite possible to write native code mixed with .NET code in various ways. Yes - .NET code is/will be portable to other platforms. Yes - I understand fully that .NET is the way to go for a large range of applications (if I hear "web" or "business" bells start ringing). Things I don't know: But - why must Microsoft push it as the future for ALL applications? But - why should everyone be writing VM (Virtual Machine) code? It's quite possible to write a very good framework (platform independent even) that doesn't use a VM. Why doesn't Microsoft do that? And: And - I'm aware of the benefits of VMs. It's just that I'm also aware of the benefits of non-VM code - and to be honest I must admit that I really prefer non-VM code. /Simon This is not a signature.
I repeat, there isn't a language good for all. Obviously you cannot write drivers in .NET. Always use the best language and platform for each purpose. .NET is very good for many applications (or part of them), C++ will be always good for OSs, drivers, and so on. For example I have to write and test a complex algorithm in C before porting it to the target platform (it will be run on an embedded device). I'll implement the IO functions in .NET and run the algorithm as a wrapped native DLL to keep the focus on important aspect of the development. If I had to write all the IO functions (anyway they would be thrown away after the testing), I would waste lots of time, without bringing benefits to the projects. ___________________________________ Tozzi is right: Gaia is getting rid of us. My Blog [ITA]
-
fat_boy wrote:
No, perhaps NT4 sp6a tightened up to Military spec might do, but then again, didnt that US Frigate drift around the ocean for a few days while they worked out how to bring the NT system that ran the whole boat bacj up? Perhaps I would just get rid of Windows.
Wow! There goes your pay cheque. Blogless
-
I repeat, there isn't a language good for all. Obviously you cannot write drivers in .NET. Always use the best language and platform for each purpose. .NET is very good for many applications (or part of them), C++ will be always good for OSs, drivers, and so on. For example I have to write and test a complex algorithm in C before porting it to the target platform (it will be run on an embedded device). I'll implement the IO functions in .NET and run the algorithm as a wrapped native DLL to keep the focus on important aspect of the development. If I had to write all the IO functions (anyway they would be thrown away after the testing), I would waste lots of time, without bringing benefits to the projects. ___________________________________ Tozzi is right: Gaia is getting rid of us. My Blog [ITA]
.Net is good for web based swervices. PERIOD. Just like J2EE. Client side it has no benefit over C++ and one draw back. It is damn slow. BTW, C++ for drivers is a bad idea. It can be done, but there are so maany pitfalls that C is the officially suppported language.
Dario Solera wrote:
embedded device
What embedded devices support .Net? Nunc est bibendum
-
I posted this in the General discussion forum, but it didn't quite stir up the flame war I expected. After seeing Vista and .NET and Microsoft's Response to Vista and .NET I figured this is the place to go. So ... I use MFC (though I don't particularly like it) and VC++ 6.0 (which I like very very much). I've spent a lot of time trying to figure out why Microsoft (and a whole lot of people affiliated or not affiliated with them) think that everyone should switch from native Win32 C++ development to .NET Framework-based development ... and I just can't figure out why. Things I know: Yes - the .NET framework has a load of nifty classes that I would have access to. Yes - it's quite possible to write native code mixed with .NET code in various ways. Yes - .NET code is/will be portable to other platforms. Yes - I understand fully that .NET is the way to go for a large range of applications (if I hear "web" or "business" bells start ringing). Things I don't know: But - why must Microsoft push it as the future for ALL applications? But - why should everyone be writing VM (Virtual Machine) code? It's quite possible to write a very good framework (platform independent even) that doesn't use a VM. Why doesn't Microsoft do that? And: And - I'm aware of the benefits of VMs. It's just that I'm also aware of the benefits of non-VM code - and to be honest I must admit that I really prefer non-VM code. /Simon This is not a signature.
It's a tool, not a religion. Use the tool you feel appropriate for the job, but know how to use all the tools in your toolchest. Marc Pensieve Functional Entanglement vs. Code Entanglement Static Classes Make For Rigid Architectures
-
I posted this in the General discussion forum, but it didn't quite stir up the flame war I expected. After seeing Vista and .NET and Microsoft's Response to Vista and .NET I figured this is the place to go. So ... I use MFC (though I don't particularly like it) and VC++ 6.0 (which I like very very much). I've spent a lot of time trying to figure out why Microsoft (and a whole lot of people affiliated or not affiliated with them) think that everyone should switch from native Win32 C++ development to .NET Framework-based development ... and I just can't figure out why. Things I know: Yes - the .NET framework has a load of nifty classes that I would have access to. Yes - it's quite possible to write native code mixed with .NET code in various ways. Yes - .NET code is/will be portable to other platforms. Yes - I understand fully that .NET is the way to go for a large range of applications (if I hear "web" or "business" bells start ringing). Things I don't know: But - why must Microsoft push it as the future for ALL applications? But - why should everyone be writing VM (Virtual Machine) code? It's quite possible to write a very good framework (platform independent even) that doesn't use a VM. Why doesn't Microsoft do that? And: And - I'm aware of the benefits of VMs. It's just that I'm also aware of the benefits of non-VM code - and to be honest I must admit that I really prefer non-VM code. /Simon This is not a signature.
Isn't the idea behind a virtual machine to decouple from the physical hardware so the two can change (evolve) independently? '--8<------------------------ Ex Datis: Duncan Jones Merrion Computing Ltd
-
.Net is good for web based swervices. PERIOD. Just like J2EE. Client side it has no benefit over C++ and one draw back. It is damn slow. BTW, C++ for drivers is a bad idea. It can be done, but there are so maany pitfalls that C is the officially suppported language.
Dario Solera wrote:
embedded device
What embedded devices support .Net? Nunc est bibendum
fat_boy wrote:
Client side it has no benefit over C++ and one draw back. It is damn slow.
You really need to look into declarative programming. C# is a perfect language for that. The .NET class libraries for XML handling, Databinding, ADO.NET are also far superior to anything in the MFC/C++/WTL world. I've written a lot of desktop business apps that use C#. And I'm far more productive with it, than I ever was in MFC. Michael CP Blog [^] Development Blog [^]
-
.Net is good for web based swervices. PERIOD. Just like J2EE. Client side it has no benefit over C++ and one draw back. It is damn slow. BTW, C++ for drivers is a bad idea. It can be done, but there are so maany pitfalls that C is the officially suppported language.
Dario Solera wrote:
embedded device
What embedded devices support .Net? Nunc est bibendum
fat_boy wrote:
.Net is good for web based swervices. PERIOD. Just like J2EE. Client side it has no benefit over C++ and one draw back. It is damn slow.
I think you're a little wrong. .NET is good for many other things, anyway it's not that slow, IMHO.
fat_boy wrote:
BTW, C++ for drivers is a bad idea. It can be done, but there are so maany pitfalls that C is the officially suppported language.
Never developed a driver... so I take your statement as correct. :)
fat_boy wrote:
What embedded devices support .Net?
No one, I think. In fact the device I'm working on supports only C/C++ and Assembler (Atmel Diopsis 740, ARM RISC processor + DSP). I use .NET only to "simulate" the IO ports on the PC: on the PC the Input will be a Wave file and the Output a MP3 file, but on the device the Input is an array of bytes from 2 ADC and the Output is a stream of bytes (containing mp3 frames) sent to the USB port output buffer. ___________________________________ Tozzi is right: Gaia is getting rid of us. My Blog [ITA]
-
norm.net wrote:
Wow! There goes your pay cheque
For mission critical I would never considder windows, would you? Nunc est bibendum
-
It's a tool, not a religion. Use the tool you feel appropriate for the job, but know how to use all the tools in your toolchest. Marc Pensieve Functional Entanglement vs. Code Entanglement Static Classes Make For Rigid Architectures
Exactly what I think. ;) ___________________________________ Tozzi is right: Gaia is getting rid of us. My Blog [ITA]
-
fat_boy wrote:
.Net is good for web based swervices. PERIOD. Just like J2EE. Client side it has no benefit over C++ and one draw back. It is damn slow.
I think you're a little wrong. .NET is good for many other things, anyway it's not that slow, IMHO.
fat_boy wrote:
BTW, C++ for drivers is a bad idea. It can be done, but there are so maany pitfalls that C is the officially suppported language.
Never developed a driver... so I take your statement as correct. :)
fat_boy wrote:
What embedded devices support .Net?
No one, I think. In fact the device I'm working on supports only C/C++ and Assembler (Atmel Diopsis 740, ARM RISC processor + DSP). I use .NET only to "simulate" the IO ports on the PC: on the PC the Input will be a Wave file and the Output a MP3 file, but on the device the Input is an array of bytes from 2 ADC and the Output is a stream of bytes (containing mp3 frames) sent to the USB port output buffer. ___________________________________ Tozzi is right: Gaia is getting rid of us. My Blog [ITA]
Dario Solera wrote:
I think you're a little wrong. .NET is good for many other things, anyway it's not that slow, IMHO
They probably have improved, added support for things like DBs etc, so I conceede there could be some benefit over MFC. I am generalising. Regarding Embedded, I was wondering if you were running NT or XP embedded on a device. Nunc est bibendum
-
fat_boy wrote:
Client side it has no benefit over C++ and one draw back. It is damn slow.
You really need to look into declarative programming. C# is a perfect language for that. The .NET class libraries for XML handling, Databinding, ADO.NET are also far superior to anything in the MFC/C++/WTL world. I've written a lot of desktop business apps that use C#. And I'm far more productive with it, than I ever was in MFC. Michael CP Blog [^] Development Blog [^]