Linked by Thom Holwerda on Fri 25th May 2012 14:55 UTC
Thread beginning with comment 519453
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
I wish "it just worked". For one thing, the switch from Mac OS to Mac OS X meant that all of a sudden, spaces in filenames became a real problem. Try it, create a folder with spaces in its filename, check out some sizable Unix OSS project and try to run the configure/make/etc command chain. Quite often you will get error messages. Since Xcode is just wrapping gcc/llvm, it suffers from similar problems.
Well.... the skill level required does go up when you are playing with the UNIX side of OSX. A mac user really does not have to touch that part of the mac for normal usage.




Member since:
2005-07-06
I wish "it just worked". For one thing, the switch from Mac OS to Mac OS X meant that all of a sudden, spaces in filenames became a real problem. Try it, create a folder with spaces in its filename, check out some sizable Unix OSS project and try to run the configure/make/etc command chain. Quite often you will get error messages. Since Xcode is just wrapping gcc/llvm, it suffers from similar problems.