Linked by Thom Holwerda on Sun 9th Sep 2012 22:58 UTC
Mac OS X "A little more than an year ago I wrote my rant post The Linux Desktop Experience is Killing Linux on the Desktop and for the first time in 8 years I wasn't a desktop Linux user anymore. I spent about a month wrestling with Windows 7, but let's face it - Windows is ill suited for professional Ruby programmers like me (and it's ill suited for most programmers, except maybe Java & .Net I guess). Anyways, it was never my intention to stick with Windows - I was just doing my Mac due diligence. Now with 1+ year of OSX usage I'd like to share a few things about my experience thus far with you."
Permalink for comment 535112
To read all comments associated with this story, please click here.
RE[5]: Windows is ill suited...
by boldingd on Fri 14th Sep 2012 21:22 UTC in reply to "RE[4]: Windows is ill suited..."
boldingd
Member since:
2009-02-19

It would help if people would write portable code to start with, instead of trying to run POSIX everywhere.


And what system interface should we write this portable code against? A lot of the APIs present in POSIX are pretty lean and pretty basic; the POSIX file API has, what, eleven major entry points*? You're either saying that people shouldn't open files, handle strings or allocate memory in "portable code", or you're saying that there's some smaller, simpler, more portable API than POSIX that we should be using.



* fopen, fclose, fread, fwrite, fprintf, fscanf, fgets, fgetc, fputc, ftell, fseek; yes, there are obviously more, but those eleven will cover most of your common desktop use-cases.

Edit: I is not can kount.

Edited 2012-09-14 21:23 UTC

Reply Parent Score: 2