|
-
Jun 16th, 2014, 04:33 PM
#11
Hyperactive Member
Re: VB6 is DEAD!
 Originally Posted by Shaggy Hiker
Ok, that's got some meat on it. So, why are you so opposed to .NET? It isn't an interpreted language when it is run, it is only an intermediate language at one point in the middle. If it were truly an interpreted language, the performance would be horrible, which it is not. The JIT compiler does take some time, which can make for a slow iniital startup, but once JIT compiled, .NET appears to generally run faster than VB6 more often than not. Though that's only on trivial comparisons like math functions, because even VB6 didn't run as fast as VB6 on larger things like database access where VB6 had at least three different mainstream options to choose from (DAO, RDO, and ADO) with different performance on each.
Slow initial startup? that's it? no, it isn't. I still remember the first ATI control panel made with .NET. It was simply scaring!! "what is this, what did I do wrong, and only clicked that button...?". But it wasn't me, it was .NET fault. In the first opportunity I switched to Nvidia , naturally.
.NET is newer than the "old" Win32, so maybe it relies on faster technology, but the principal factor is that .NET steals all the resources for itself (as does MS Office) what leads to the speed impression you might have, but it's completely artificial. Don't you think that, had Classic VB been evolved till now, it would be a lot faster now than back in 2000? and less resource hungry than .NET? Please be serious if you answer to this.
I can understand Java popularity as a way to develop multi-platform stuff, but .NET???
Don't know nothing about DAO or RDO, but I use ADO in my language (not within VB) to import data from legacy databases. Nothing bad to say about it.
I now use Olaf's SQLite wrapper, exclusively. I believe it will be extended to PostgreSQL in the future, and that's all I need. In fact I never used SQLServer or Access databases, and never will.
I'm aware of ADO.NET, and maybe it's better than legacy ADO, but again, how would be ADO by now had it's development didn't stop?
.NET was a mistake, a big one, and Windows is suffering a lot because of that wrong move. C'mon, admit it, as M$ already did.
Last edited by Carlos Rocha; Jun 16th, 2014 at 04:36 PM.
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|