I want to reply to all three of you, so I'm just gonna do it like that. sehugg kind of got a point, but I think there were really good cross-platform solutions

I want to reply to all three of you, so I'm just gonna do it like that. sehugg kind of got a point, but I think there were really good cross-platform solutions available back then. Just not the ones used today. Marmalade has been around for a quite while and it was/is used by a lot of big studios. The other two comments I don't agree with. > It's not that the picked the wrong tool for the job, it's that the job changed. If your tool can't adapt to new requirements an argument can be made that you did in fact pick the wrong tool in the first place. That's my point exactly. > That seems like a better option than over encumbering yourself to begin with by adding in effect a bunch of additional cross platform requirements. I think this is a bit of an exaggeration. They don't write their own engine, so the overhead for going cross-platform is really, really small — so small that I have a hard time coming up with examples right now. Not hard coding screen sizes and that kind of thing might be one, but that's about it. There's also some irony in saying that's the better option given the blog post we're talking about.