Why should I code?

Tell me 10 reasons I should learn to code in C

>>80
No one in this thread was talking about personal computers exclusively, until you came around. Now, please excuse us while we countinue our discussion about C in general.

☣ Please try to ignore troll posts! ☣

http://dis.4chan.org/read/prog/1231209853/10

>>1
If you care about learning lower level stuff about programming/computing, then it is good to learn C in conjunction with your CPU's opcodes. Some practical reasons why you would want a lower level understanding include: tuning software code to perform optimally to a given architecture; directly programming computer hardware; creating/understanding/modifying language compilers; be able to read the massive quantity of code written in C. If all you care about is writing programs, then there are other higher level languages that abstract a whole lot of programming bookkeeping.

>>80
yes, they are. now please go back to /pr/.

>>85
http://en.wiktionary.org/wiki/personal_computer
"A small computer, built around a microprocessor, for use by one person at a time."

>>78
>These architectures were displaced by PC because they are just tiny incompatible domains with "approved" hardware(just like Macs) while PC is an open standard.

WHAT?
Most of those CPUs have fully open specs if you plan to develop on them, you can download the documentation freely from the manufacturers website (and other support sites), just like you can do for Intel CPUs. And in a lot of cases, these CPUs are available for those wanting to design their own platforms/devices or code for a specific platform.

Some specific platforms, such as consoles/handhelds may have specific libraries which are not available except under a NDA, and you may need a debug device to actually write code for that platform, but the actual CPU specs and usage tends to be as open as it gets. Take this in another way: let's say you have private OS(ex. modified version of Windows) for which you're given no documentation which runs on your console(ex. Xbox), however the console's CPU and hardware are known(slightly modifed x86 P3). The same logic could be aplied to the DS or PS3 and other consoles/devices, as the actual CPUs which are used in those platforms are incredibly well documented( think thousands of pages of freely available documentation ).

Oh and Macs are x86 and you can run the software on a standard PC as long as the Mac has drivers for whatever peripherals you have.

Why the fuck am I even bothering answering to your posts,  you've repeatedly proven incapable of understanding such simple concepts.

RAEG IHBT

>>87
Personal computers 10-20 years ago were very lucky if they had that kind of resources, go back more further and that DS will look like a supercomputer.

erm make that 20+

(1) C is for experts
(2) EXPERT PROGRAMMERS
(3) I AM AN EXPERT PROGRAMMER
(4) THIS IS /PROG/ YOU DO NOT DEMAND 10 REASONS WHY TO PROGRAM IN C, DONT HELP HIM!!!!!!!
(4) Read SICP.

>>92
EXPERT COUNTER

>>88
☣ Please try to ignore troll posts! ☣

http://dis.4chan.org/read/prog/1231209853/10

>>93
Uploaded it to userscripts.org^[1] for people who can't be bothered to copy paste that script. I wonder why so many people haven't done so yet, it greatly improves the /prog/ user experience.

__________________________
http://userscripts.org/scripts/show/40415

>>96
Make sure you upload this one too.
// ==UserScript==
// @name           FVCloak
// @description    Renders your posts invisble to FrozenVoid
// @namespace      http://dis.4chan.org/prog/
// @include        http://dis.4chan.org/*;
// @version        1.?
// ==/UserScript==

for each (var input in document.getElementsByTagName('textarea')) {
   if (input.name == 'com') input.value = '[spoiler]troll LISP SICP[/spoiler]\n'
}

>>91
The actual clock speed is only a part of the equation, the other part is the actual design of the architecture(RISC vs CISC and so on) and how many clocks each instruction takes. If you believe that those CPUs are equivalent, I dare you to try running some DS games with the same speed on your 486.
You won't be able to, even with a decent dynarec engine
Also, compare the power consumption of a 486+said RAM vs the DS's hardware.

>>99
YHBT

Task: Copy 4 words in your RAM (if you thought of strings now, you are probably wrong here) to a different location using an ARM or a x86-based CPU.

x86:
- set pointer to ram adress
- move value of ram adress into your accumulator(register)
- set pointer to ram adress 2
- move value of accumulator to ram adress
- repeat 4 times.
ARM:
- set pointer to ram adress
- copy 4 values into 4 registers
- set pointer
- copy to new adress

ARM is more effiencent for those things.

Also, FaggotVoid, if you say your processor needs to run windows, to be called a proper CPU, take a look at Pocket PCs.
They can run Windows^[1]. And they run ARM processors^[2].

_____________

^{References:
1: http://en.wikipedia.org/wiki/Windows_CE
2: http://en.wikipedia.org/wiki/Pocketpc#Definition}

>>101
YHBTE

>>101
You can't win an argument against a troll. You should know better.

>>1
you shouldn't learn to code. your way to retarded.

^

your

and

to

*facepalm*

>>101
Y u dont using spesal copi 4 wrdz 2 diff loczion op???

>>106
probably because 486 didn't have as many extensions as modern x86 CPUs

>>107
MOVS already existed in the 8086, you dolt.

>>107
He could have used a string operation, though.

>>108
>>109
(rep) movsd would work indeed, but depending on what he plans to do with the data, some SIMD extensions might be a better idea

>>106
It would still require more processing cycles, since you have insufficient registers to do it all at once.
You can also store more values in the internal registers of an ARM, which makes processing data there a lot faster than always getting it from your RAM/cache.

C and C++ are the language's of the gods.

>>112
What about the language's other stuff?

>>112
languages of shitty gods

The Functionally Dead Ddog.

Bookkeeping?