I was really hoping this was someone talking about making Ruby 1.9.3 compile with llvm-gcc. At home, I'm running ruby compiled with clang and I've noticed the occasional hiccup with some gems. But, unlike the author, I do use software installed with XCode (iOS dev kit) so uninstalling XCode isn't really an option.
For what it's worth, there are a ton of recommendations to do this same thing out there--and for many people it's just not a viable option. This isn't a success story so much as it's using a workaround. Not being part of either the Ruby or Apple dev teams, I won't say whose side this is on to fix: only that it needs to be fixed.
The "success story" works just as fine without uninstalling Xcode: that's just "the bonus" - you can uninstall it if you don't use it for anything else.
Comments
I was really hoping this was someone talking about making Ruby 1.9.3 compile with llvm-gcc. At home, I'm running ruby compiled with clang and I've noticed the occasional hiccup with some gems. But, unlike the author, I do use software installed with XCode (iOS dev kit) so uninstalling XCode isn't really an option.
For what it's worth, there are a ton of recommendations to do this same thing out there--and for many people it's just not a viable option. This isn't a success story so much as it's using a workaround. Not being part of either the Ruby or Apple dev teams, I won't say whose side this is on to fix: only that it needs to be fixed.
For what its worth, there is a 'semi-official' stance of the Ruby team on clang:
https://bugs.ruby-lang.org/issues/5883
In short: We'd like to support it, but sometimes clang still breaks. So there is no support.
The "success story" works just as fine without uninstalling Xcode: that's just "the bonus" - you can uninstall it if you don't use it for anything else.