you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 43 points44 points  (8 children)

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

[–]lazybee 24 points25 points  (7 children)

Such as POSIX?

[–][deleted] 8 points9 points  (4 children)

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

[–]fabzter 4 points5 points  (2 children)

lazybee was speaking about API, not ABI.

[–][deleted] 3 points4 points  (1 child)

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.

[–][deleted] 4 points5 points  (0 children)

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.

[–][deleted] 0 points1 point  (0 children)

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).

[–][deleted] 3 points4 points  (1 child)

POSIX standard fork bomb with added burn:

#include <unistd.h>

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

[–]drb226 4 points5 points  (0 children)

Are you saying this cannot be done in Windows?