Cor Ligthert said:
Herfried,
I asked you what the Fort T sample has to do with VBCom. Jim has almost
taken no time to study VBNet
Not true, Cor. I have implemented .Net at three corporations that had never
used the technology (including an app developed for Qwest Communications
that scaled from the projected 5 users to over 2500 simultaneous users with
no problem). I have read most of my 54 book collection on VB.Net and I have
used VB.Net 2003 extensively.
The thing I have not finished evaluating (and will not continue to do so
until it is released) is VB.Net 2005.
because I get the idea that he will only use RealBasic in future for his
new developments.
I will use REALbasic where appropriate. If other technologies are more
appropriate, I will use them.
I am not a language or platform zealot. I will use what is best for my
clients. Right now, I am not sure that it is best for my clients to
continue to be drug around by the scruff of the neck by Microsoft.
As a responsible developer (responsible to my clients) I am looking into
Microsoft alternatives. Linux/REALbasic has some definite advantages and I
think any serious developer should take a look. It's still rough around the
edges, but its getting there.
I gave the sample to show him be on time.
I use the Ford T sample often, however because you are involved in this,
have I as far as I remember me, with the exception that I referenced
somebody who used that, not taken that sample in the VBCom subject,
however probably sail ships and steam ships or to say it better the
transport sample.
Those all are general economic samples by the way so I don't see why I
should not use those.
Because they are not representative of the nature of the change that
Microsoft has in store.
If you insist on using an automobile analogy.....think of classic Visual
Basic as a car factory, and your applications as cars that you create. With
the advent of .Net, Microsoft is changing the roads (the OS on which your
programs run) from smooth asphalt & concrete to new lightwieght plastic
roadways.
The new lightweight plastic roadways will allow for higher highways, longer
bridges and less environmental damage.....all good things. Unfortunately,
your old cars are too heavy to drive on the new plastic roadways. Now, your
classic VB cars will run fine on the old roads, but Microsoft is only
producing the new lightweight roads, will no longer fix any new potholes or
dangerous sections of the older roads and your classic VB factory cannot
make your classic VB cars safe for the new lightweight roads.
At the same time that all of this is happening, Microsoft decides to update
the C++ car factories with big, fat soft tires and a lightweight chassis
that allow C++ cars to continue to run on the new lightweight plastic
highways. They even move the C++ car factory into the new C# factory (where
the new lightweight cars are produced) to allow the C++ cars to continue to
be produced with the fat tires and light chassis needed to extend their
lives while being able to take advantage of the new tools in the C# factory.
When you ask Microsoft to make some room in the C# factory for the classic
Visual Basic factory and to help you make fat tires and a light chassis for
your classic VB cars (to extend their lives also) they simply provide you
with a list of reasons that your classic Visual Basic cars won't run on the
new lightweight roads and a list of all the hurdles to making fat tires and
a light chassis for the classic VB cars.
This doesn't really make sense though.....there are more classic VB cars on
the road than C++ cars. So, why is Microsoft abandoning the classic VB cars
but assisting the C++ car factories in upgrading their vehicles and even
pulling the C++ factory into the new fancy C# factory that will build cars
especially for the new lightweight roads?
A quick look over the fence of the Microsoft parking lot reveals the
answer.....the folks at Microsoft mostly drive C++ cars. That's why they
are assisting the C++ factories and not the classic VB factories.
Sad but true.
Nevermind the fact that millions of classic VB car owners will have to
either do major work to lighten their cars enough to run on the new
lightweight highways or buy a new car. And, the classic VB factories are
being forced to shut down and buy the new VB.Net factories to mass produce
the replacements for the classic VB cars.
This causes great hardship for millions of small businesses and individuals
that depended in their classic VB cars to get to work, and play and take the
kids to school.
But, as long as it helps Microsoft make more money.....it's all
good......right?
I really don't understand what you all connect to VBCom, this is a thread
about Realbasic.
They are both valid alternative to the hell Microsoft has created for the
classic Visual Basic developers.
Jim Hubbard
