Re: vb6 -v- Net!
- From: "Robert Morley" <rmorley@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 29 Mar 2007 12:09:46 -0400
I have to disagree with you there. While I will grant that .NET is no
revolution. It definitely moving art of programming forward.
Oh, no argument...it's moving the *art* of programming forward by leaps and
bounds, and the *science* of programming back to the Dark Ages. I don't
want my code to be pretty, I want it to work.
But it is more
particularly in the areas of graphics and database style access.
Ah, yes, we've moved from the ability to migrate from one database
environment to another with minimal tweaking (ADO) to an environment where
moving from one database environment to another requires a major re-write
(ADO.NET for SQL Server vs. ADO.NET for Jet, etc.). As I understand it, you
can write more generic code in ADO.NET, but then you lose much of the more
advanced functionality of the specific environment. You're right, it is
"more"...more WORK.
Plus the language has evolved to point were it truly does take less
code to do the same tasks. However again it is an evolutionary
improvement. The only dramatic improvement I can point is the use of
generics and inheritance to consolidate boilerplate code like the one
used for strong typed collections.
Here, at least, we agree completely. The language does have its
improvements, and I won't deny that in any way.
The problems of .NET are NOT because its sucks. The problem of .NET is
that the entire range of backwards compatibility has been broken.
I think that that's an oversimplification. I consider the biggest problem
of .NET to be the lack of speed in the managed languages; the backwards
compatibility issues are secondary to me.
If the #1 software company decided to trash their #1 programming
environment. Are they really a sane company. Are small time developers
even their customers anymore?
Plus with the debut of Vista and the Windows Presentation Framework
versus WinForm Framework. There are signs that Microsoft still doesn't
"get" it.
Your VB Classic sites sums it up the best. It is an issue of trust
Agreed on all counts!
The only way they can restore my trust is to create a
VB6 complier that works with .NET.
We can only hope.
Rob
.
- References:
- Re: vb6 -v- Net!
- From: Paul Clement
- Re: vb6 -v- Net!
- From: Stefan Berglund
- Re: vb6 -v- Net!
- From: Paul Clement
- Re: vb6 -v- Net!
- From: Stefan Berglund
- Re: vb6 -v- Net!
- From: Paul Clement
- Re: vb6 -v- Net!
- From: Stefan Berglund
- Re: vb6 -v- Net!
- From: Paul Clement
- Re: vb6 -v- Net!
- From: Stefan Berglund
- Re: vb6 -v- Net!
- From: Paul Clement
- Re: vb6 -v- Net!
- From: Robert Morley
- Re: vb6 -v- Net!
- From: Paul Clement
- Re: vb6 -v- Net!
- From: Robert Morley
- Re: vb6 -v- Net!
- From: Karl E. Peterson
- Re: vb6 -v- Net!
- From: Robert Conley
- Re: vb6 -v- Net!
- Prev by Date: Open Excel file
- Next by Date: Re: Vista Installations
- Previous by thread: Re: vb6 -v- Net!
- Next by thread: Re: vb6 -v- Net!
- Index(es):
Relevant Pages
|