Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

The REAL EXPERT PROGRAMMING manifesto

Name: Anonymous 2007-08-12 21:29 ID:fq6hVIZN

[code]
1. MONOSPACE OR GTFO
2. VI OR GTFO, RINSE, REPEAT
3. IF INPUT IS FROM UNTRUSTED SOURCE, CHECK THE SHIT FIRST.  CHECK ALL UNTRUSTED INPUT.  EVERY SINGLE ITEM.  BUFFER OVERFLOWS SHOULD HAVE NEVER HAPPENED
4. ONE STATEMENT PER LINE, BRACES ARE STATEMENTS
5. JAVA SUCKS
6. SLOW HASKELL IS SLOW
7. IF YOU SEGFAULT, YOU DIE FOR REAL
8. I WOULD PROGRAM IN ASM BUT I HAVE BETTER THINGS TO DO IN THE 20 YEARS IT WOULD TAKE ME TO WRITE A DECENT PROGRAM IN IT
9. UNIX NEVER DIES
10. GIVE IT AWAY, IT'LL BE CRACKED EVENTUALLY ANYWAY

Name: Anonymous 2007-08-24 7:56 ID:RFvB4ZQi

Commandlines were designed in the 70s when computers did not have GUI capability.  This is true.  Computers are pretty much the same way they were in the 70s, except more and faster.

When you strip away all layers of abstraction, CPUs are serial stream processors.  Everything is always: do { read, process, output } while !EOF.  Multicore/multi-CPUs can just handle multiple streams, but each individual stream is always handled serially.  Computers are serial in nature.  So is the commandline.  Until that basic aspect changes, the commandline will always be with us.


Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List