Posted by: CWStevenson
If you read this as a pure technical wannabe - or, you think you're a
technical god already, then don't bother reading it. But if you are
interested the realities of life and how they apply to technology and the
economy and to the future of technology, I think the following could be of
interest to you.
Hype vs Reality --
When .NET was first announced, there were industry pundits and yes, many
members of these news groups that quickly forecasted the end of GUPTA
(please stop using Centura - it brings back so many bad memories). But .NET
has not put GUPTA out of business and it has in fact done just the opposite.
1). Microsoft will eventually get it right. But not usually until the third
The first release of .NET was, well, a pretty dismal failure as admitted by
MS insiders. But the second release is looking much better, but there is
still much ground to be covered before it is widely adopted. There is the
fact that MS still has not surfaced all the features and functionality to
third party vendors, GUPTA being one of them. Our .NET data provider has
some weaknesses in usability because MS has not made the libraries available
to anyone outside of MS. So you will see some SQLServer functionality
inside VS.NET that you won't see from other providers. MS is working to
address this issue, but the effort is massive, and it will take some time.
MS themselves have not fully converted all their applications to .NET for a
number of reasons, some simply have to do with time and effort, others have
to do with technical limitations and I think you will see the
interoperability between COM and .NET get much better since MS themselves
will have to use it as well.
Finally, .NET has to prove itself over-again. Many large corporate
organizations tested .NET and, invested heavily in some pilot projects -
only to run into numerous problems where .NET did not work as "stated" and,
the stability was very poor. One of the largest on-line retailers attempted
to get .NET to run a small portion of their business and could not get it to
run for more than about 50 minutes before it would crash.
Now, to be sure, these will all be fixed, and .NET will be a very cool place
to be when they are fixed. So, when will this be? Longhorn most likely and
that's why you've not seen GUPTA jump on .NET bandwagon just yet. My
approach is to let it settle down, let other find the issues of instability
and let MS address some of issues of easing migration before we take it for
Now, what about those Visual Basic programmers that were blind sighted by
.NET? After all, they have no choice but to become object oriented - and
many have chosen NOT to do the .NET dance. In fact, many have seen Team
Developer as an attractive alternative to being forced into .NET. And we
Welcome all VB programmers and will work to make their transition as
painless as possible. (A very interesting twist to be sure. But I like it.)
2). JAVA vs. .NET
.NET actually lost a lot of ground in large corporate users due in large
part to the comments above. JAVA has some severe weaknesses as well, in
particular an anemic GUI and, it still is not write once-deploy everywhere.
But, it has gained ground on the server-side processing and it will continue
to grow by leaps and bounds here until .NET can show some real programming
advantage over J2EE.
Bottom-line, most shops will have J2EE (Java) and .NET working together.
Why is it so different from just a few years ago?
Why it is different now than it was in 1998? It may be too obvious, but
business drives the need for technology - not the other way around. But in
the time period from late 1997 to about 2000, some people forgot this
fundamental law and, they started to let technology drive the need for
technology -- Never a good thing. Those days are long-gone and today, if a
technology does not significantly contribute to business objectives it is
irrelevant. And, it does not matter what the programmer that wants to use
it thinks. So a programmer may want to build up his or her CV/Resume by
using .NET, but if the management knows that the application would be better
built in GUPTA's Team Developer, well, Team Developer it should be.
So, with Team Developers 3.1's many new features, and, the improved speed
and stability since the 2.1 release, you really can develop applications
much faster than you can on .NET or other tools. And, if you want a
low-cost, low-risk path to .NET, stay with GUPTA for the Team Developer.NET
Really, it comes down to common sense. GUPTA continues today because we add
significant value to businesses that develop and deploy applications based
on GUPTA technology. Otherwise, we would have gone out of business a long
time ago. We are now entering a time when there is resurgence in interest
in GUPTA as an independent software vendor that provides tools to rapidly
develop applications and, to safely and easily move to .NET.