|
| Stay with Borland and Win! |  
|
|---|
| why you don't need now the .NET | Product: Delphi all versions | Category: Others | Skill Level:
 | Scoring:  | Last Update: 08/24/2001 | Search Keys: delphi delphi3000 article borland vcl code-snippet net framework, microsoft, Visual Studio NET, | Times Scored: 30 | Visits: 4359 | Uploader: Romeo Lefter Company: Rombest Software | Reference: N/A | | | Question/Problem/Abstract:
Is Net Framework a really new concept. Do I need to migrate to new Microsoft Visual Studio Net? | Answer:
For the start, I want to specify that I'm not employed to Borland in any way. All opinions contained in this article are my opinions and are based on my observations.
Because of agressive Micro$oft marketing some people knows that the actual .Net initiative of mr. Bill Gates is a real revolution. All sounds great: multiplatphorm programming, languages interoperability and many many other thinks. All my friends knows that I'm Delphi programmer and, starting with many month ago, they looks at me like at a dinosaur. All of them works now with beta2 of VisualStudio Net and every time when we meet they discuss about how cool is this new Gates programming environment.
Let's look in detail. For mr. Gates, the multiplatphorm programming means just the following OS-es: Win95, 98, Me, NT, 2k and (offff) XP. I'm shure that next year, mr.Gates will present the future Windows "XXP or XXXP" (I don't know how M$ will name there future "experience" operating system). Really, sond strange. For Mr.Gates, the multiplatphorm means just the Windows family! Can you belive that? For me is inaceptable.
Another trick used by Microsoft Marketing Team is language independence and inter-operability. Oh, that's great! There are many programmers that loves this facility. But what that really means? This interoperability is a really stupid thinks because, under Net framework all languages looks the same. There are just minor diferences between .net languages. In fact, if you want to use perl under .Net, you will have to use Microsoft Perl (I know, ActiveState) not the real Perl. This perl is really a strange hybrid. The actual Visual Basic is a new one. Is pure OO and for a real VB programmer this is a nightmare. "Where is my goto" will say a VB veteran.
Now let's understand how a program works under .Net framework. When you want to distribute it, you must know that this program will not work if the user haven't the .Net framework installed. And I really don't know how many people will install this! But let's forget this and let's look in detail: after you compile a program, the generated exe file will contain an "intermediate language" code. This code will be translated by a JIT compiler in real machine code on the user computer. I know that you know that is the "old java trick". Microsoft has copy the idea and transformed it in a MS invention. This is MS problem, but in my tests the IL code generated by Visual Studio Net works really slow. Compare this with the speed of Delphi generated code and you will have the results. I know that this is a big problem for Microsoft and because this is a real problem Microsoft wants to transform all Windows platphorm in a Net related platphorm.
There are many other thinks about this Microsoft invention, but I want to stop here in describing new MS Visual Studio. Now let's return at Borland and let's learn how to win!
The actual version of Delphi is fantastic. You have all you want to create from simple applications to multi-tier applications or complex web services. All is clear, is cool and easy. My opinion is this is a real cool programming environment. Also, you can create CLX applications that will work also on Linux. You can create Apache modules for your web applications. Also, you can create CGI's, ISAPI/NSAPI modules. In fact, you can create all you want easy and fast.
And about Net? Belive me, it will be suported by Borland. And not like others said as a plugin for Visual Studio! Will be suported in Borland way (don't you know what is Borland way? Is File|New|.Net Application). But actually you don't need that! The Net Framework is just a beta and a very agressive marketing campain.
In the final I want to say that I will don't migrate to Net framework because when a customer contact me he wants a solution, not a NET framework experiment. Belive me, this is the true, the pure true!
|
|