Isn't anyone paying attention. C# and the.NET platform is "NOT" related to DCOM, activex etc. It does "NOT" implement COM. It can use it, but believe it or not, it's not native.
Well, let's see, assuming your talking about current VB (5 or 6)
-compile to byte code - wrong answer
VB currently compiles to P-code or native, C# will use IL.
-reuire VM - wrong again
Runtime is the answer you were looking for, big difference
-garbage collected - wrong again
Current versions of VB are not "garbage collected" Objects are supposed to fall out of scope and get cleaned up, but if any competent VB coder relies on this, theyare fighting memory leak bugs.
-need COM to do anything - wrong again
Current VB is definately COM based. C# doesn't use COM at all. It is NOT COM++ or COM2 etc etc etc. It can use COM, but is not dependent in any way.
I'll give you the rest, although a couple could be argued on technicalities, but I believe we've seen enough here. Next time get the facts.
And if you were paying any kind of attention at all, Microsoft is saying the same thing. That's why the change. The way it was explained to me is that Microsoft is going to make as much of the.net arch open as it can, but it is not going to develop a runtime for use on another os. It will help that other company develop the runtime, but they are not going to do the work. BTW, there was a demo of an ASP making a call to some code running on Solaris. I do debug distributed app, and it's a real pain in the ass, so I am looking forward to using a single ide, and it does work post mortem. Please do a little homework before spouting the anti MS propoganda.
This guy just needs to get a life. This is the most significant thing that Microsoft has done in years. I really feel that all of those Penguin huggers out there should be a little concerned that you OS will go back to being a hobby like it should be. I am really getting tired of hearing MS bashing. I was at PDC. This technology is going to make an impact. It is the real thing. I have been waiting for tools like this for years. I work in a corprate environment. To me speed of development is real high on the list. To be able to have several different languages call functionality from each other, and to be able to debug all of them at the same time in the same ide is a huge home run for me. The flexibility the can offer is huge. You all can give me this C++ is for real programmers crap all you want. I am in the business of delivery working polished products in as little time as possible. I use C++ when it makes sense to use it (which isn't very often). I have 7000 users that I need to get solutions to. The ability to drop code on the machine and run it (no more registry nightmares, no more DLL hell) is a dream come true. Anders Hejlsberg made it quite clear that the.net runtime can be implemented on most any os, and Microsoft will support the effort. Well I say let's challenge IBM to get up and running on AIX. How about OS390? I can run Java code there, why not C#.
I can figure out C++ and the one thing that I have figured out about it is that it takes 4-5 times as long to get anything out the door as it does with VB. Yes there are a lot of so called developers that are using VB and producing a lot of crap code. But that's not the tools fault. I have several production apps up and running that have been done in VB. They are stable, used by as many as 7000 users daily, and have been up and running for as long as 4 years. I have a process that runs every day on a an NT server, runs as a service, written in VB, yes VB as a service. The server has not been rebooted in 3 mths. The idea that real programmers use C++ is about 2 years to old. Maybe it's time you wake up and smell the money. While your trying to figure out where that last memory leak is, I'll be cashoing the check for the last delivered functional WORKING application.
The reasson that the goods weren't delivered is not because of the tool. It was because there are a lot of VB developers out there that can't code their way out of a wet paper bag. The problem with a tool like VB and even Delphi is that it is easy to get an app up and running. And it's also easy to do it with a very bad design and implementation. I spend a great deal of my time not writing new VB code, but fixing and redesigning current VB code (and am paid very well for it). If the design is solid, and you can get someone you can write solid VB code, that app can and will be as solid as anything else out there.
Slashdot Mirror
Isn't anyone paying attention. C# and the .NET platform is "NOT" related to DCOM, activex etc. It does "NOT" implement COM. It can use it, but believe it or not, it's not native.
Well, let's see, assuming your talking about current VB (5 or 6) -compile to byte code - wrong answer VB currently compiles to P-code or native, C# will use IL. -reuire VM - wrong again Runtime is the answer you were looking for, big difference -garbage collected - wrong again Current versions of VB are not "garbage collected" Objects are supposed to fall out of scope and get cleaned up, but if any competent VB coder relies on this, theyare fighting memory leak bugs. -need COM to do anything - wrong again Current VB is definately COM based. C# doesn't use COM at all. It is NOT COM++ or COM2 etc etc etc. It can use COM, but is not dependent in any way. I'll give you the rest, although a couple could be argued on technicalities, but I believe we've seen enough here. Next time get the facts.
Yeah, but who cares...
And if you were paying any kind of attention at all, Microsoft is saying the same thing. That's why the change. The way it was explained to me is that Microsoft is going to make as much of the .net arch open as it can, but it is not going to develop a runtime for use on another os. It will help that other company develop the runtime, but they are not going to do the work. BTW, there was a demo of an ASP making a call to some code running on Solaris. I do debug distributed app, and it's a real pain in the ass, so I am looking forward to using a single ide, and it does work post mortem. Please do a little homework before spouting the anti MS propoganda.
This guy just needs to get a life. This is the most significant thing that Microsoft has done in years. I really feel that all of those Penguin huggers out there should be a little concerned that you OS will go back to being a hobby like it should be. I am really getting tired of hearing MS bashing. I was at PDC. This technology is going to make an impact. It is the real thing. I have been waiting for tools like this for years. I work in a corprate environment. To me speed of development is real high on the list. To be able to have several different languages call functionality from each other, and to be able to debug all of them at the same time in the same ide is a huge home run for me. The flexibility the can offer is huge. You all can give me this C++ is for real programmers crap all you want. I am in the business of delivery working polished products in as little time as possible. I use C++ when it makes sense to use it (which isn't very often). I have 7000 users that I need to get solutions to. The ability to drop code on the machine and run it (no more registry nightmares, no more DLL hell) is a dream come true. Anders Hejlsberg made it quite clear that the .net runtime can be implemented on most any os, and Microsoft will support the effort. Well I say let's challenge IBM to get up and running on AIX. How about OS390? I can run Java code there, why not C#.
I can figure out C++ and the one thing that I have figured out about it is that it takes 4-5 times as long to get anything out the door as it does with VB. Yes there are a lot of so called developers that are using VB and producing a lot of crap code. But that's not the tools fault. I have several production apps up and running that have been done in VB. They are stable, used by as many as 7000 users daily, and have been up and running for as long as 4 years. I have a process that runs every day on a an NT server, runs as a service, written in VB, yes VB as a service. The server has not been rebooted in 3 mths. The idea that real programmers use C++ is about 2 years to old. Maybe it's time you wake up and smell the money. While your trying to figure out where that last memory leak is, I'll be cashoing the check for the last delivered functional WORKING application.
I can earn 6 figures writing Windows software. Nuff said!
The reasson that the goods weren't delivered is not because of the tool. It was because there are a lot of VB developers out there that can't code their way out of a wet paper bag. The problem with a tool like VB and even Delphi is that it is easy to get an app up and running. And it's also easy to do it with a very bad design and implementation. I spend a great deal of my time not writing new VB code, but fixing and redesigning current VB code (and am paid very well for it). If the design is solid, and you can get someone you can write solid VB code, that app can and will be as solid as anything else out there.