Re: Newbie scratching his head



When I took my first steps in this field, many years ago, I tried BASIC from
the assumption that it was easier. I absolutely didn't understand enough of
it to get over the initial hurdles. I had read that 'C' was not recommended
for beginners, but QuicC came out and was rather un-costly, so I bought it.
Actually, this was really easy - but, then I am a nuts and bolts kind of
guy, everything made complete sense to me from the very start - following up
on the algorithms and actually getting your stuff done, has not so much to
do with the language, if it is a difficult subject, it will be a difficult
job.

It all depends on the way you like to think about things, I agree with the
above - I don't like BASIC, but I like having some good books around, if you
are going to concentrate on something 'C -like' I recommend laying your
hands on the Petzold and the Prosise, they will end up being useful whatever
language you decide to use for Windows Programming.

Tony. . .


"Charlie Tame" <charlie@xxxxxxxxx> wrote in message
news:%23ozfQylFGHA.3532@xxxxxxxxxxxxxxxxxxxxxxx
> 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: How do I dig a memory value out?
    ... language hit the 'sweet spot' between a higher level ... > that would compile to machine code. ... > A friend of mine who was working with lasers, (and also had an Atari) ... Someone brought it into a user group meeting. ...
    (microsoft.public.vb.general.discussion)
  • Re: MSIL or Bytecode taught instead of ASM
    ... efforts of the "high level language" communities, ... spent learning any given assembler or assembly language. ... said IL (unlike the basic architecture). ... traditional VM (the high or low-levelness between bytecode and machine code ...
    (comp.programming)
  • Re: Is Procedural Paradigm a basis of OO Paradigm?
    ... Now a given language may allow for such, ... I don't know machine code so I cannot be sure. ... But it is saying that the a specific program under a specific mapping ... roman numerals equivalent to mathematical sentences written in arabic ...
    (comp.object)
  • Re: hide python code !
    ... in compiled languages when we compile a code to an executable file it ... There are disassemblers for machine code. ... Hiding source code is incompatible with Open Source software. ... Use another language. ...
    (comp.lang.python)
  • Re: method calls faster than a loop?
    ... When you start talking about machine code, you're no longer talking about just the programming language, but also the compiler and Virtual Machines as well. ... More specifically, there's theoretically no reason why you couldn't write a compiler that takes C source code and emits Java bytecode, or which takes Java source code and emits native Win32/x86 executables. ...
    (comp.lang.java.programmer)