Iritscen
Mr. Grumpikins
I'm writing a program that I may want to port to Windows at some point, only so I can get all those Windows geeks to see what I've done. I don't want to limit it to 5% of the market, yada yada.
So, right now I'm writing in Obj-C in Xcode. I am using as much custom code as possible, mostly just because I like to, but also because I should need to learn less about Windows to make my code work when I (possibly) port it. So, for instance, the GUI will probably be custom code, no Apple APIs, when I get around to making it; and I've written my own functions for reading/converting strings that are working nicely so I am not hamstrung by these blasted NSStrings.
Is there anything else I should be thinking about? Is there a better language than Obj-C for apps that will be getting ported? Should I be using something like Java/python/ruby? The little technical crap in Obj-C is really ticking me off and hampering development. I should be spending most of my time working on things like path-finding and predictive AI, and instead I'm stuck nursing finicky NSObjects.
So, right now I'm writing in Obj-C in Xcode. I am using as much custom code as possible, mostly just because I like to, but also because I should need to learn less about Windows to make my code work when I (possibly) port it. So, for instance, the GUI will probably be custom code, no Apple APIs, when I get around to making it; and I've written my own functions for reading/converting strings that are working nicely so I am not hamstrung by these blasted NSStrings.
Is there anything else I should be thinking about? Is there a better language than Obj-C for apps that will be getting ported? Should I be using something like Java/python/ruby? The little technical crap in Obj-C is really ticking me off and hampering development. I should be spending most of my time working on things like path-finding and predictive AI, and instead I'm stuck nursing finicky NSObjects.