Why attempting systems programming on OS X is a waste of your time
Do you enjoy piles of unintelligible code written without any regard to consistent style? Do you like documentation that's worse than non-existent? Do you like worthless samples that you can't compile because Apple hasn't thrown all the headers and/or libraries and/or tools over the wall that are needed to actually build them? Do you like the idea of a second-system effect poster boy for interacting with hardware that manages to be even more hideous than ioctl? Do you like the idea of a decrepit kernel trailing both Windows and Linux in most regards based on technology proven to have failed in 1990 and kept around for mostly political reasons? Do you like having nobody from which to get help because most every other Mac developer is a clueless wanker writing insultingly simple applications and selling them for $25+? If so, you may enjoy OS X systems programming!
Stay tuned for "Why attempting applications programming on OS X is also a waste of your time," featuring yet more private APIs, lousy documentation, and a general experience that makes raw Win32 look like a good time.
Stay tuned for "Why attempting applications programming on OS X is also a waste of your time," featuring yet more private APIs, lousy documentation, and a general experience that makes raw Win32 look like a good time.