Microsoft would rather see you reboot than exit all instances of one of their products! Look at MS Office for another example...
After all, which is easier? CTRL-Q or that big shiny RESET button?
When I took computer science, we learend Pascal, and a little bit of the art of structured, procedure-driven programming. Unfortunely, in high school 'ADT' only meant an alarm company.
Then in college, we learned C. Again more procedure driven stuff. Sometime before I graduated, a teacher taught us C++.
Needless to say, our programs weren't very object oriented, nor were they required to be so.
The algorithms class we took (also in C), was also extremely lacking, and 'ADT' only became a fuzzy word for doing a lot of extra typing that didn't make sense.
Unlike most of my classmates, I knew assembly language for several platforms already.
This being said, if you start out, introducing people to programming with assembly language, most people will quit and become liberal arts majors.
The few that do continue, may be able to make the jump to a procedure oriented language AND be able to trust what the compiler does behind their back. Those that don't even think about the compiler's affairs are highly suspect...
They are really going to be baffled by object-oriented programming. Transistioning from the world of goto's, subroutines, and jump tables to virtual methods and multiple inheritance.
This being said, what should be done is to teach assembly language in parallel with something like C. That way, people get a feel for the timing of things -- why floating point arithmetic is slower than integer arithemetic, why sequentially reading arrays is faster than linked-lists, etc.
More emphasis also needs to be put on the operation of the memory and disk caches (for data structures), operating system scheduling (multi-threaded apps), and overhead of system calls.
Imagine the horrors that someone would produce if they transistioned directly from assembly language to an object-oriented language! -- one class, one method, one program!
WTF? I try to give a decent warning to the public and I get modded as flamebait?
Either the moderators don't click on the links, or we have some real sickos here....
If slashdot is going to promote the kind of material that his link is pointing to, then I'm going back to M$ Windows and using PC World as my source of tech information.
If I were to say that his link contained material of an 'extremely sick' nature, it would only be an understatement!
Slashdot Mirror
Microsoft would rather see you reboot than exit all instances of one of their products! Look at MS Office for another example... After all, which is easier? CTRL-Q or that big shiny RESET button?
1) Write a virus with a cool name.
2) Sell it to the anti-virus companies.
3) ?????
4) PROFIT!!!
Virus-writers don't get to name their viruses, the anti-virus companies do that.
Well you seem to be making one mistake....
The virus writers ARE the anti-virus companies!
Then they must also hate Los Angeles...
Let's just hope they don't use airport runways for guidance!
Ah, dihydrogen monoxide...
When I took computer science, we learend Pascal, and a little bit of the art of structured, procedure-driven programming. Unfortunely, in high school 'ADT' only meant an alarm company. Then in college, we learned C. Again more procedure driven stuff. Sometime before I graduated, a teacher taught us C++. Needless to say, our programs weren't very object oriented, nor were they required to be so. The algorithms class we took (also in C), was also extremely lacking, and 'ADT' only became a fuzzy word for doing a lot of extra typing that didn't make sense. Unlike most of my classmates, I knew assembly language for several platforms already. This being said, if you start out, introducing people to programming with assembly language, most people will quit and become liberal arts majors. The few that do continue, may be able to make the jump to a procedure oriented language AND be able to trust what the compiler does behind their back. Those that don't even think about the compiler's affairs are highly suspect... They are really going to be baffled by object-oriented programming. Transistioning from the world of goto's, subroutines, and jump tables to virtual methods and multiple inheritance. This being said, what should be done is to teach assembly language in parallel with something like C. That way, people get a feel for the timing of things -- why floating point arithmetic is slower than integer arithemetic, why sequentially reading arrays is faster than linked-lists, etc. More emphasis also needs to be put on the operation of the memory and disk caches (for data structures), operating system scheduling (multi-threaded apps), and overhead of system calls. Imagine the horrors that someone would produce if they transistioned directly from assembly language to an object-oriented language! -- one class, one method, one program!
WTF? I try to give a decent warning to the public and I get modded as flamebait? Either the moderators don't click on the links, or we have some real sickos here....
If slashdot is going to promote the kind of material that his link is pointing to, then I'm going back to M$ Windows and using PC World as my source of tech information. If I were to say that his link contained material of an 'extremely sick' nature, it would only be an understatement!
double-clicking your mouse! Gee, just when you thought we ran out of uses for mice, someone comes along and find another...
The collar is not the place for a computer... Computers and sweaty areas of the body don't mix well.
Now an ankle computer would be a great innovation. Besides looking hip, it could function as an exercise weight, and maybe be powered by walking!
The true freaks will those be running Seti@Home on their ankles -- and consequently never be allowed to stand still!
Imagine -- a Riverdance team wearing ankle computers -- a human powered beowulf cluster!
Ah Crap, Shazbot!
Welcome to our new ankle-computer overloads!
Where the hell is Morpheus when we need him?