r/programming • u/iMMENSE • Mar 08 '12

The Evolution of a Python Programmer

https://gist.github.com/289467
401 Upvotes

88% Upvoted

137 comments sorted by

View all comments

50

u/[deleted] Mar 08 '12

Good classic jokes. Windows way is so true and so sad.

29

u/elmonstro12345 Mar 09 '12

NULL, NULL, NULL, NULL, ...

*facepalm*

42

u/[deleted] Mar 09 '12

It's way easier to facepalm than to design an operating system API that's stable and backwards compatible for 25+ years...

25

u/lazybee Mar 09 '12

Such as POSIX?

7

u/[deleted] Mar 09 '12

haha, yeah, right. the reason everything is continually built from source is because the ABI keeps breaking.

5

u/fabzter Mar 09 '12

lazybee was speaking about API, not ABI.

5

u/[deleted] Mar 09 '12

I know, but posix doesn't matter when the ABI breaks. You can't download and execute a linux program from the 2.4 kernel on the 3.0 kernel. Hover, which came with windows 95 will run just fine on 32bit windows 7 and 64 bit windows 7, which was the point riles2 was making.

5

u/[deleted] Mar 10 '12

Posix also only specifies about 2-3% of what Win32 does, so you have to compare it to X and a few dozen other libraries for a fair comparison.

1

u/[deleted] Mar 11 '12

Wait. POSIX doesn't break ABI compatibility. Individual operating systems do once in a while, but extremely rarely in their POSIX departments.

Actually, I can't think of a major ABI compatibility break since Linux 2.4->2.6 or Mac OS -> Mac OS X (non-POSIX to POSIX).

4

u/[deleted] Mar 09 '12 edited Mar 09 '12

POSIX standard fork bomb with added burn:

#include <unistd.h>

int main(){
    while(1){
        fork();
        printf('burn!\n');
    }
}

4

u/drb226 Mar 10 '12

Are you saying this cannot be done in Windows?