Re: Newbie scratching his head



As a complete Newbie myself only a few months back (although I had done some
machine code back in Amiga days and some before that) I decided to try the
VS2005 betas and VS2003 just to see the differences. As a result, thinking I
should actually try to do some serious study at last, I bought books on C++,
VB and C# - all the .net versions I guess.

Based on my almost total lack of knowledge of all 3 languages I figured that
C# is the most likely to advance the quickest, and thus be adopted more
while VB kinda fades out. I remain convinced that OOP is a myth, brought
about by aliens who intend to nullify our technological advancement by
creating confusion and placing the entire human race inside curly brackets,
but if we're going to let them get away with it we may as well go the
easiest route :)

Actually even Quickbasic can be more "Powerful" than it ever got credit for,
but I don't necessarily think that "Power" means the same to all people. In
terms of getting to the hardware, and speed, I maintain that machine code
(Well assembler of course) is the only "Powerful" language, but to use it
these days and see any benefit you'd have to reinvent so many wheels it
would be a lifetime's work to get to what most users expect to see. I mean
there's not much point in writing super efficient code and still having to
call Windows routines written in C++ to show the results :)

Frankly I never liked Visual Basic, to me it was neither Visual nor Basic,
so I am kinda biased against it despite recognizing that the current
versions are vastly superior, but I think my hurdle is getting to grips with
OOP rather than C#, so I can only suggest you go with what seems to sink in
best with you.

On a totally different topic I would add that some months ago I acquired by
accident a spare PCI video card so for the hell of it installed it to see
what happened. Since then I have to wonder how one manages with just a
single monitor and desktop - since you can drag any help off to one side and
or test you code while still looking through it. It's like a cordless drill,
you wonder how the heck we ever managed before they were invented :) Perhaps
some of the hardened old "Pros" will laugh but I do seriously think it is a
very useful addition while learning.

Good luck, I figure I'm probably quite old for a newbie but there ya go...

Charlie



"BPB" <BPB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7DA33E03-283B-45C0-8D3E-8A1787E221FD@xxxxxxxxxxxxxxxx
> I've been a designer for years, never getting into development since I
> would
> just hire others to do the heavy lifting. For various reasons I have
> decided
> to do development myself. However, I would like to learn one language
> first
> then move on to others. What would you recommend I start out with? Visual
> Basic looks like it's easiest to learn, but I've read that C# is much more
> powerful. I haven't really found any articles to explain the differences
> between the 2 languages. Does anyone have any information?
> Thanks
> --
> BPB


.



Relevant Pages

  • Re: Overview Of New Intel Core i7(Nehalem) Processor
    ... people settled down and started doing more disciplined design. ... apps will still need mathematical, disciplined, unambiguous languages. ... See, tha tis wha tI mean, yo udo not knwo C, and yet yo uhave more opinions ... I wrote my first EPROM programmer with zeros and ones in machine code, ...
    (sci.electronics.design)
  • Re: OT computer languages Re: low sugar - spotty vision
    ... Like assembly languages, all high-level languages must first be translated ... into machine code before they can be run by a computer. ... assemblers, linkers, and debuggers, which help them translate high-level ...
    (alt.support.diabetes)
  • Re: Has microsoft given up on .NET for performance-critical applications?
    ... If I remember it was a research compiler chain on which they were working ... compared to e.g. the machine code generated by the java hotspot JIT. ... It seems that microsoft has given up on the CLR as far as high ... languages and not as core languages. ...
    (microsoft.public.dotnet.framework)
  • Re: 32 bit FORTH ??? Different tack!
    ... over time portions were 're-coded/ written' in forth, then the NEW iteration (x86 code) would only require the writing of an x86 kernal. ... Particularly because versions written in these 'other' languages, will have 'quirks' in their code that are a result of the 'quirks' of those languages. ... The 'larger' the 'piece of machine code' the Less Likely' that it was Forth code to start with. ... Andy Valencia, Astrobe, Rod Pemberton, Rickman, are ones whose postings I had marked. ...
    (comp.lang.forth)
  • Re: OT computer languages Re: low sugar - spotty vision
    ... Like assembly languages, all high-level languages must first be translated ... into machine code before they can be run by a computer. ... assemblers, linkers, and debuggers, which help them translate high-level ...
    (alt.support.diabetes)

Loading