•
•
•
•
What is DaniWeb IT Discussion Community?
You're currently browsing the Assembly section within the Software Development category of DaniWeb, a massive community of 363,558 software developers, web developers, Internet marketers, and tech gurus who are all enthusiastic about making contacts, networking, and learning from each other. In fact, there are 3,940 IT professionals currently interacting right now! Registration is free, only takes a minute and lets you enjoy all of the interactive features of the site.
Please support our Assembly advertiser:
Views: 8639 | Replies: 13
![]() |
•
•
Join Date: Feb 2002
Location: Lawn Guylen, NY
Posts: 10,869
Reputation:
Rep Power: 32
Solved Threads: 109
After never looking at ASM before, I took a one semester course in it. The final project was creating a Space Invaders game in DOS (complete with color and sound), and I think mine came out pretty decent. So, relatively speaking, that's what I was able to accomplish in two months time
Dani the Computer Science Gal
Do you run a computer-related website? Feature it in our niche link directory!
Do you run a computer-related website? Feature it in our niche link directory!
I wouldn't recomment assembly as your first language. There's a different dialect for every architecture you program on, and even though the language is relatively small and simple, the problem is putting small and simple pieces together. It's easier to work with a language that doesn't require you to build all of your tools from scratch.
>assembler first and then unix because i am chaning from ms windows to linux next year
I don't entirely agree with that recommendation. When working with Linux as a power user, you'll end up using Perl and shell more than anything. If you work as a developer than expect to use C quite a bit.
My recommendation would be to start with Perl, then go to C. With a year to do it, you shouldn't have any problems getting a little comfortable with both languages. Once you actually switch to Linux, most of your effort will be made in getting comfortable with the interface. However, since Linux comes with full source code, and most of that source code is in C, you'll be better off in the trip to mastery if you can read it.
To summarize, Perl lets you take advantage of Linux's flexibility and C gives you inside knowledge into the operating system. The nice thing is that both Perl and C can be used in both Windows and Linux. The same can't be said about assembly language if Linux is run on a different architecture.
You should learn assembly eventually, mind you, just not as a first (or second) language.
>assembler first and then unix because i am chaning from ms windows to linux next year
I don't entirely agree with that recommendation. When working with Linux as a power user, you'll end up using Perl and shell more than anything. If you work as a developer than expect to use C quite a bit.
My recommendation would be to start with Perl, then go to C. With a year to do it, you shouldn't have any problems getting a little comfortable with both languages. Once you actually switch to Linux, most of your effort will be made in getting comfortable with the interface. However, since Linux comes with full source code, and most of that source code is in C, you'll be better off in the trip to mastery if you can read it.
To summarize, Perl lets you take advantage of Linux's flexibility and C gives you inside knowledge into the operating system. The nice thing is that both Perl and C can be used in both Windows and Linux. The same can't be said about assembly language if Linux is run on a different architecture.
You should learn assembly eventually, mind you, just not as a first (or second) language.
Member of: Beautiful Code Club.
thanks for your recommendations thaey are well appreciated. i told my uncle but he says linux is better and more safer to use. it may not be easy but it is for more professional computer users and takes more thinking and i like challenges.
•
•
•
•
Originally Posted by Narue
I wouldn't recomment assembly as your first language. There's a different dialect for every architecture you program on, and even though the language is relatively small and simple, the problem is putting small and simple pieces together. It's easier to work with a language that doesn't require you to build all of your tools from scratch.
>assembler first and then unix because i am chaning from ms windows to linux next year
I don't entirely agree with that recommendation. When working with Linux as a power user, you'll end up using Perl and shell more than anything. If you work as a developer than expect to use C quite a bit.
My recommendation would be to start with Perl, then go to C. With a year to do it, you shouldn't have any problems getting a little comfortable with both languages. Once you actually switch to Linux, most of your effort will be made in getting comfortable with the interface. However, since Linux comes with full source code, and most of that source code is in C, you'll be better off in the trip to mastery if you can read it.
To summarize, Perl lets you take advantage of Linux's flexibility and C gives you inside knowledge into the operating system. The nice thing is that both Perl and C can be used in both Windows and Linux. The same can't be said about assembly language if Linux is run on a different architecture.
You should learn assembly eventually, mind you, just not as a first (or second) language.
>i told my uncle but he says linux is better and more safer to use.
And Unix is even more stable than Linux, though language portability is a good thing, and whether Linux is better and safer doesn't effect my recommendation at all. The idea is to give you languages that you'll actually use a lot and can also learn both before and after you make the move to Linux.
>but it is for more professional computer users
I'm a professional developer, and a large portion of my work is done on the Windows platform. Though I do write code that needs to be run on both Windows and Unix, so limiting yourself to one platform only hurts you in the end.
>takes more thinking
Not necessarily. It may just seem that way because Linux encourages command line work and the command line appears more complicated.
>i like challenges.
That's the best reason you have to learn a new operating system and the programming languages that go with it.
>but what would be the assemblers for microprocessor
You're probably on an x86 architecture, so a quick google search for "x86 assembler" or "x86 assembly tutorial" should give you plenty to get started.
And Unix is even more stable than Linux, though language portability is a good thing, and whether Linux is better and safer doesn't effect my recommendation at all. The idea is to give you languages that you'll actually use a lot and can also learn both before and after you make the move to Linux.
>but it is for more professional computer users
I'm a professional developer, and a large portion of my work is done on the Windows platform. Though I do write code that needs to be run on both Windows and Unix, so limiting yourself to one platform only hurts you in the end.
>takes more thinking
Not necessarily. It may just seem that way because Linux encourages command line work and the command line appears more complicated.
>i like challenges.
That's the best reason you have to learn a new operating system and the programming languages that go with it.

>but what would be the assemblers for microprocessor
You're probably on an x86 architecture, so a quick google search for "x86 assembler" or "x86 assembly tutorial" should give you plenty to get started.
Member of: Beautiful Code Club.
Hello,
I thank GOD that Iowa State didn't make us program entire programs in assembly. That is what a compiler is for. Granted, I would never encourage someone to be ignorant and avoid learning something new, I have to wonder why some places still make programming difficult like that.
I agree with Narue that Assembly is not a good first language idea. I started with Pascal, went to C, then C++, and then got a semester of assembly where we took pre-assembled code and optimized it for more efficient execution.
Perl is a great language to get into. I wish I knew it along with awk and sed. Powerful Unix / Linux utilities. You might also want to learn about expect.
Enjoy coding,
Christian
I thank GOD that Iowa State didn't make us program entire programs in assembly. That is what a compiler is for. Granted, I would never encourage someone to be ignorant and avoid learning something new, I have to wonder why some places still make programming difficult like that.
I agree with Narue that Assembly is not a good first language idea. I started with Pascal, went to C, then C++, and then got a semester of assembly where we took pre-assembled code and optimized it for more efficient execution.
Perl is a great language to get into. I wish I knew it along with awk and sed. Powerful Unix / Linux utilities. You might also want to learn about expect.
Enjoy coding,
Christian
![]() |
•
•
•
•
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
•
•
•
•
•
•
•
•
DaniWeb Assembly Marketplace
Other Threads in the Assembly Forum
- Previous Thread: Some general assembly questions
- Next Thread: Just bought an assembly book and having problems with basic stuff.



Linear Mode