Hacker News new | ask | show | jobs
by sounds 3879 days ago
Working through the Ogre issues on OS X is like a rite of passage, I thought?

I tried multiple times to contribute OS X fixes to the Ogre code base. They're not hard things --

1. Use SDL not OIS.

2. The symlinking is broken.

3. Link the frameworks properly.

There was one more thing, I think. Just minor issues that probably have crept into the codebase because no one is able to contribute the fixes.

It's Ogre. It's not OS X.
1 comments
jokoon 3876 days ago
Thought too. But in my opinion, an OS has larger responsibilities when it comes to improve inter compatibility, instead of breaking things to have developers who stay loyal and ending up with apple-exclusive software. I really wonder about the value objective C brings, especially since NextStep did not work as a project. You can't always put the fault on library devs.

What boggles my mind, is that OSX is an unix underneath, so I don't understand why it would do anything different and force developers to learn new habits. That's not how you attract devs. Apple has made an habit to break backward compatibility, something neither linux nor windows tend to do.

I think it's not so much to think that OS manufacturers should not to be different than their competition by separating even how their development tools work. The only objective of that is to have developers who stay loyal to apple because they can't have their app running on both windows and mac. Not to mention I had to re do everthing at each new XCode version.

So in the end, having my project run on both XCode and MSVC, was too much time lost, so I just sold that aging laptop. Apple is just so special, and I guess I was not good enough for that.

link