Goal: Programming

[josephmills]

What's the best language to start learning with?

start with bash then mv >> python and then C ?

I went
perl
lisp <~~ which I do not do that much of
bash
C
C++

Learning now
python



I wish that I learned python first. well bash then python then C

hope that this helps

Joseph

[CptPicard]

What's the best language to start learning with?

You know, this is probably "the" classic question on the forum. If you use the search feature, you'll find very, very long and intense exchanges on which language a beginner is best starting out with. I'll just skip the rhetoric as you can search for it (for example, "the high- vs. low-level language megathread".

IMO my pick would be Python -- it teaches you the most important ideas in programming with a very beneficial learning curve, plus you can get a lot of interesting, actual stuff done in the languge. There are even hints of the functional paradigm present in Python so you'll get some exposure to that as well.

[11jmb]

What's the best language to start learning with?

I don't think that this is a good enough question. Put some though into what domain interests you. An ideal first step differs for web, mobile, desktop, etc.

If you are truly unsure and your interest in programming comes from a general desire to tell a computer what to do, Python is an excellent starting point.

The only popular language I advise against starting with is C++.

[DaviesX]

I don't think that this is a good enough question. Put some though into what domain interests you. An ideal first step differs for web, mobile, desktop, etc.

If you are truly unsure and your interest in programming comes from a general desire to tell a computer what to do, Python is an excellent starting point.

The only popular language I advise against starting with is C++.

I start with C++ before, but I was pretty confused when the book began introducing Object-Oriented Programming

[11jmb]

My problem with C++ is that it tries to cover too many layers of abstraction at once. If you want to write low-level code, start with C.


OOP is a completely different problem, I think it's severely over-used, although it does have its place. Have you asked for help on this board? Link to a thread if you have, and I'll try to help.

[DaviesX]

I just gave up learning that, I feel really comfortable to write c for instance. And I intend to learn assembly for X86 too, Can you please give any suggestion about it ?

[lisati]

I just gave up learning that, I feel really comfortable to write c for instance. And I intend to learn assembly for X86 too, Can you please give any suggestion about it ?

You can ask some C compilers to produce a listing of the ASM equivalent of the code they output. This can sometimes provide insight into what x86 code looks like. It has been a while since I've done it, so someone else might need to refresh my memory on how it's done.

[josephmills]

Learn a scripting lang before you attempt a Compiled languages May scratch
You can learn Scratch in like a 5 hr

I say with every thing also look at where things came from and how they have gotten too where they are now.

Also look into

Flow Charts




Simple Sequence



if statments









Loops







Case Statements












Most langs also have*
arrays
functions*
variables
learn that stuff in any lang then you we see that they all start too run together but that is just my thoughts

[11jmb]

I just gave up learning that, I feel really comfortable to write c for instance. And I intend to learn assembly for X86 too, Can you please give any suggestion about it ?

I must ask what your reason is for wanting to learn assembly. 99 times out of 100, a good C compiler will produce as good (or sometimes better) assembly code than most engineers could write.

If your interest is purely academic, you might have a better learning experience with a RISC. I believe that most universities prefer to teach RISCs (Once upon a time, my architectures class was taught with MIPS) because you can cover all of the same concepts in a simpler context.

also, +1 lisati.

try compiling some basic programs with:

gcc -S myfile.c -o myfile.s

and looking at the assembly. you can assemble/link myfile.s in the same way that you would link an object file

gcc myfile.s main.c -o a.out

[DaviesX]

Thanks. Because I want to know how a program really run on a cpu and using inline assembly can generate faster code in some programs I guess.
I am currently making a graphics program, and the book suggests using SSE to parallelize the computation while I have no knowledge about assembly, So I decide to study this language