hahAHAHAHAHAAAA... have you actually tried this with the latest version of c# and vb.net orca... have you done any of this testing yourself...
that article that you quoted from is how many years old... not to mention that both the language and their respective compilers are wayyy past that beta stage that the test results represented in those articles refer to...
stop googling about and do some tests yourself... the stuff you've just shown me is old news... known by anyone who was beta testing the languages... you may find that the current compiler is a bit different...
as far as your reference to pointers being an advantage... well...
a quote from DNJ Online...
plus...
finally... still quoting from DNJ Online...
ya gotta stop reading all these googled up articles though... get some real hands on experience and background in both c# and vb.net... it shows that you actually don't have this O...
... and a lil background in the old vb and c++ wouldn't hurt either to give you some perspective.
no putdown here, it's just that your statements show that the depth of understanding is very shallow... there are reasons for the move away from pointers in the 'new order' that is .net... and the JIT feature of the compiler is really not so much about optimizing as it is about other things that .net is all about.
--Mike
that article that you quoted from is how many years old... not to mention that both the language and their respective compilers are wayyy past that beta stage that the test results represented in those articles refer to...
stop googling about and do some tests yourself... the stuff you've just shown me is old news... known by anyone who was beta testing the languages... you may find that the current compiler is a bit different...
as far as your reference to pointers being an advantage... well...
More significantly, C# gives programmers the option of using pointers. Pointers are variables which refer or ‘point’ to specific locations in memory. They are so widely used in C and C++ that many programmers may find it difficult to conceive of programming without them.
The trouble with pointers is that they are inherently unsafe. They make it easy to corrupt memory, overwrite data and crash your applications. C# discourages the use of pointers but does permit their use within blocks of code marked with the unsafe directive.
The trouble with pointers is that they are inherently unsafe. They make it easy to corrupt memory, overwrite data and crash your applications. C# discourages the use of pointers but does permit their use within blocks of code marked with the unsafe directive.
a quote from DNJ Online...
plus...
Even so, it is not quite true to say that pointers can never be used. VB.NET provides access to pointers using the IntPtr type. This allows a limited range of pointer operations. For example, an IntPtr variable can be used to store a handle to a file or a window.
If you prefer to program in VB.NET but have an occasional need to use pointers, you can, of course, add a C# or even a C++ project to your solution in order to do all the ‘dirty work’.
If you prefer to program in VB.NET but have an occasional need to use pointers, you can, of course, add a C# or even a C++ project to your solution in order to do all the ‘dirty work’.
finally... still quoting from DNJ Online...
Making the choice
In summary, when evaluating programming languages for .NET, the choice between C# and VB.NET is largely a matter of personal preference. In the past, VB may have been looked down upon by some developers who considered it to be inherently less powerful than other general purpose languages. But VB.NET is altogether a different beast from VB6. It is every bit as powerful as C#, it has full access to the .NET Framework and its compiled applications should generally be just as fast and efficient as similar applications written in C#.
In summary, when evaluating programming languages for .NET, the choice between C# and VB.NET is largely a matter of personal preference. In the past, VB may have been looked down upon by some developers who considered it to be inherently less powerful than other general purpose languages. But VB.NET is altogether a different beast from VB6. It is every bit as powerful as C#, it has full access to the .NET Framework and its compiled applications should generally be just as fast and efficient as similar applications written in C#.
ya gotta stop reading all these googled up articles though... get some real hands on experience and background in both c# and vb.net... it shows that you actually don't have this O...
... and a lil background in the old vb and c++ wouldn't hurt either to give you some perspective.
no putdown here, it's just that your statements show that the depth of understanding is very shallow... there are reasons for the move away from pointers in the 'new order' that is .net... and the JIT feature of the compiler is really not so much about optimizing as it is about other things that .net is all about.
--Mike