Re: WHY

From: Harlan Grove (hrlngrv_at_aol.com)
Date: 12/24/04 

Date: Fri, 24 Dec 2004 00:07:54 -0800

<aaron_kempf@hotmail.com> wrote...
>VBA and VB isn't just for 'novice developers'
>
>the .net framework evened the playing field; and anyone that tells you
>different is a C geek and needs to be put out of thier misery LoL
...

Do you know what the .Net framework is? It's a virtual machine that executes
virtual machine code. That does mean that VB.Net code should be able to run
as fast as comparable C# or Perl.Net or whatever other .Net language you
choose to use. It doesn't mean that .Net code will run as fast as native
hardware machine code. It also doesn't mean .Net code can make use of third
party libraries compiled into native hardware machine code.

That leaves the syntactic and semantic aspects of the languages. On an
aesthetic level I don't like VB. I find it too verbose, and substring
operations are klunky. C (dunno about C#) and Perl have better control
structures. Perl has more built-in data structures. Nearly all other
languages are available on other OSs. VB is Windows only. I realize that
doesn't matter to you, but you're so short-sighted about software your
opinion doesn't really count.

Relevant Pages

  • Re: WHY
    ... > hardware machine code. ... > That leaves the syntactic and semantic aspects of the languages. ... Perl has more built-in data structures. ...
    (microsoft.public.excel)
  • Re: Copy protection for a .NET application
    ... >> You can skip MSIL and compile directly to machine code if you want. ... You don't have to release your program in MSIL. ... I can't say I'd recommend going that route though - while I haven't ... the .NET framework will clearly have ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Copy protection for a .NET application
    ... >> You can skip MSIL and compile directly to machine code if you want. ... You don't have to release your program in MSIL. ... I can't say I'd recommend going that route though - while I haven't ... the .NET framework will clearly have ...
    (microsoft.public.dotnet.framework)
  • Re: Copy protection for a .NET application
    ... >> You can skip MSIL and compile directly to machine code if you want. ... You don't have to release your program in MSIL. ... I can't say I'd recommend going that route though - while I haven't ... the .NET framework will clearly have ...
    (microsoft.public.dotnet.general)
  • Re: Copy protection for a .NET application
    ... Use the NGEN utility that comes with the .Net Framework. ... Robby ... >> You can skip MSIL and compile directly to machine code if you want. ... You don't have to release your program in MSIL. ...
    (microsoft.public.dotnet.framework)