Re: Back to VB6 and .NET
- From: Robert Conley <robertsconley@xxxxxxxxx>
- Date: Tue, 5 Feb 2008 06:01:51 -0800 (PST)
On Feb 4, 7:21 pm, Tom Shelton
<tom_shel...@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Only because they are catching it up to C#.
So what was missing between VB.NET and C#. We know C# has the ability
to run unsafe code but what other feature VB.NET didn't have that C#
did? The initial version didn't have unsigned integers but that has
been fixed. So whatever capabilities that VB.NET doesn't have via C#?
Basically the issue here is people aren't taking the time to
understand the technical issues of the .NET platform. This is a
problem because too many are complaining about non-existent problems
rather than focusing on the real problems notably BACKWARDS
COMPATIBILITY. It gives people justification to ignore the complainers
when they show they don't know what they are talking about.
Flailing about with adoption rate and market share is also a red
herring. When a vendor breaks compatibility people will investigate
alternatives. Windows got away with it via DOSut .NET isn't.
.
- Follow-Ups:
- Re: Back to VB6 and .NET
- From: Stefan Berglund
- Re: Back to VB6 and .NET
- From: Tom Shelton
- Re: Back to VB6 and .NET
- References:
- Re: Back to VB6 and .NET
- From: Harvey Triana
- Re: Back to VB6 and .NET
- From: Robert Conley
- Re: Back to VB6 and .NET
- From: Bob Butler
- Re: Back to VB6 and .NET
- From: Robert Conley
- Re: Back to VB6 and .NET
- From: Tom Shelton
- Re: Back to VB6 and .NET
- Prev by Date: Re: Pressing an "external" button
- Next by Date: Re: Life of VB6?
- Previous by thread: Re: Back to VB6 and .NET
- Next by thread: Re: Back to VB6 and .NET
- Index(es):