Thread: Wanna learn Assembly?

Why did this thread go into a debate between assembly and everything else?

>>> Ofcourse it is impossible to get away from C, since all OS's that I know of are written in C.<

Err...Menuet? If you think C is a requirement in OS development, you might want to brush up.

>> infact C is basically too low level for large scale projects. <<

C can do everything C++ can do. OOP is only for organization...

Yes, and asm can do everything c/c++ can do. But I think what he's saying is it's much easier and faster to write a large scale project in c++.

infact C is basically too low level for large scale projects.

Though C is still used a lot in very large scale projects. In embedded systems, C is still one of the most used languages, though C++ is coming up, since embedded software is growing and growing. Object orientation makes designing large systems easier. Design goals like re-use of software and maintainability are very well supported by object orientation. These and more reasons have lead to object oriented design methods being most used today. It is very well possible to implement object oriented designs in C or ASM, but more efficient is using a language which supports object orientation, like C++ or Java.

The best course of action in my opinion is to use the UML and a process in order to document all of the details including the user needs and the scope. A process assists construction, they are using an interative and incremental approach these days, much better than the waterfal methodology.

The purpose of a process is not to document all the details. Processes are defined to make clear how the project members should work, they can also be used to make the process measurable. A process also guarantees a certain quality of the product.

The real issue is learning ASM or C for the sake of planning software architectures.

A software architecture is language independent. It is a set of general rules and designs, software architectures are usually not developed for just one product, but they will be used as base for many products of the same kind. The software architecture and requirements are the base for the detailed design.

UML is only a modelling language. It is a tool for describing software models.

infact C is basically too low level for large scale projects.

Untrue. C is fine for any size project you care to write, large or small. The absurdity of your statement shows either your ignorance, your lack of experience, or your age. The problem with "today's generation" is they, like Al Gore, seem to think they invented everything.

As for 'asm' .v. 'C', there is no such issue at stake. Both are valid, right place, right time.

As for why it is good to know assembler, if you aren't smart enough to understand why it is a good thing, then you have no business developing code. Choose something else, so you're not wasting our time.

As for developing code in assembler-- it's no harder than any other method. Simply more tedious until you build up a library of code to draw from.

I am apologizing, in advance, but it's got to be said: STOP bickering over crap practically none of you understand! That has got to be the _*biggest*_ turnoff on this board.

The people who use C for large scale projects are doing so because OOP is too advanced, same case with going ahead writing a program without planning and documenting the requirements.

&nbsp;&nbsp;OK, here is my simple view. There is no need to argue about it or try to convince me I'm wrong or anything because it's only my view, I'm not trying to impose it.

&nbsp;&nbsp;I believe that ASM and C have different roles. ASM can be used to write fast and efficient code where C just couldn't cope or you don't trust the compiler. Similarly, it becomes too difficult to write complex programs (3D games, for example) entirely in ASM and so C/C++ is often the language of choice for this scenario, being the next lowest language in my opinion. Often, it is possible to write a bit of code in either C or ASM, in which case I would often choose ASM, unless it would prove to be very inconvenient.

&nbsp;&nbsp;What I really can't stand, though, is people that say that ASM is no longer of any use and has been superseded by higher-level programming languages. ASM will never become obsolete, simply because there will always be a need for a rock-bottom-level language!

Your gernation wrote poor quality programs. You are lucky that we don't come to your house and shoot you for all the junky tools that you left us to work with.

&nbsp;&nbsp;TK, who were you refering to? I'd be surprised if my generation has yet left anyone with any tools, I'm 16!

Mario, with all due respect, you are nothing more than a child. I was writing code, long before you were given life.

I helped build many of the Intel processors. I am intimately familiar with both the Motorola and Intel processor families, as well as a hundreds of other processors and eproms you know nothing about. I have been involved at every level of computing technology since its infancy. I know the whys, the wherefores, and the whatnots.

Unlike you, the computer is part of me. I understand it at a level only 6 or so other people on this board do. Unfortunately, most of them don't even post anymore, or are gone.

If my delivery of the truth is a little abrupt, well then tough. You are a child and that isn't going to change until you mature, and just perhaps learn something of what you talk about.

What erks me the most is that you 16 year-olds and such think you invented everything. You still don't even understand the relationship between C and C++. I know Bjarne. In my opinion, he is one of the laziest, poorest excuses for a developer that ever existed. His entire idea was driven by the concept of abstraction-- the requirement of a disorganized mind.

Ears open, mouth shut. Good advice for you, youngster.

>> Your gernation wrote poor quality programs. You are
>> lucky that we don't come to your house and shoot you
>> for all the junky tools

I suspect this is directed at me. Well, boy, understand that I am two or three generations removed, so I bear no responsibility. My generation put man on the moon with a PDP8. Your generation has done nothing but dump trash on Mars.

You wouldn't have a computer without the technology _my generation_ built. Still used today. What generation do you think developed TTL logic and assembler, and the concept of the compiler you use today?

Wake up.

seyah I see you have returned. It is always nice to have experienced people here.

i'll learn assembly next year at the school !!

LOL thats interesting?!


what are you arguing about guys???
the role of assembly language in modern programing OR your age?

Well my opinion is that assembly language will forever has its place in programing ...

and it is still developing ... its changing (someone even introduced the idea of OOP in it ... although it is macros based)

did someone remember 8-bit apples??
well look at their assemble !
it is full of instructions like
LDX LDY (Load in X Load in Y)
there is no MOV

also not invoke macro....

So ASM is still on the scene!