4 ms·
What are your alternatives? OSX, where Apple has no qualms about abandoning technology, hardware or software, within a matter of years (the iPad 1 was EOL'ed ju
by FireBeyond 14y ago
What are your alternatives? OSX, where Apple has no qualms about abandoning technology, hardware or software, within a matter of years (the iPad 1 was EOL'ed just shy of two years old, I believe).
XCode and (Snow) Leopard? No such luck.
Now, you do mention the Linux alternatives, which seem to be the most stable... if you can get around any infighting of QT... Gnome/KDE... etc et al.
But it doesn't seem particularly "fair" to imply that this is something of a risk when you choose Microsoft.
- rplacd 14y agoThe Apple situation's slightly more complex than that: they're certainly ruthless with their hardware, but it's a bit of a stretch to claim they have commitment issues with their software technologies - ObjC, Foundation and AppKit's been around since the late 1980s from NeXT without serious architectural changes; UIKit'll be around for a while yet; let nothing come between them and their investment in the Apple Compiler Group. (The upshot is that they've sufficiently abstracted hardware away anyway, so hardware changes aren't showstoppers.) If anything, they're more conservative with tossing out the SDKs than most: OpenGL support, for example, is still absurdly piss-poor, even if they're getting better with their GPU driver support. But it does net you compatibility all the way down their HCL - at the bottom end, for example, is the mid-'07 iMac with the ATi 2600 PRO. They do give not-so-subtle hints to hand over to them the cha-ching, though, when they EOL old versions of XCode - but that's usually the most you're going to encounter. So works Apple in general.
- chc 14y ago> The Apple situation's slightly more complex than that: they're certainly ruthless with their hardware, but it's a bit of a stretch to claim they have commitment issues with their software technologies - ObjC, Foundation and AppKit's been around since the late 1980s from NeXT without serious architectural changes And if you happened to bet on those technologies instead of Carbon, you're probably very happy with that. Well, unless you were writing Cocoa apps with Java, which was pushed as a peer to Objective-C in much the same way that Carbon was presented as a peer to Foundation and AppKit. Those technologies all got killed pretty viciously, even though Apple at various points actually seemed to be promoting them over Objective-C/Cocoa. Apple axes stuff faster than Microsoft is even capable of moving. Looking directly back from their current technology stack, it looks like mostly smooth sailing, but that's because you're not looking at the wreckage to the left and right. (Bonus points: Remember when Apple were all about Garbage-Collected Objective-C until they weren't and suddenly ARC was the new hotness?)
- jawngee 14y agoXCode and (Snow) Leopard? No such luck. You can compile for Leopard and Snow Leopard by dragging the appropriate SDKs into /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/
- FireBeyond 14y agoBut you can't run Xcode on Snow Leopard any more (well, the current version). Admittedly not as much of an issue, as it seems Mountain Lion solves at least some of Lion's pain points.
- vor_ 14y agoApple obsoletes older technology, but it doesn't introduce dozens of redundant technologies only to drop them. There's a difference between keeping up with a linear path of progress and jumping from API to API without any clue as to which one is the "right" one.
- jcromartie 14y agoI think Apple's foundational technologies have been fantastically stable since OS X came along. It's been pretty much the same solid core since 2001, from OS X 10.1 through iOS 6. The only major piece to go away was Carbon, which was pretty much just for OS 9 backwards compatibility to begin with. I use many of the same classes and techniques in iOS today that I did in the very beginning of learning OS X programming.
- csense 14y ago> What are your alternatives? Option 1. Use a third-party abstraction library to make the same code work on every platform. Unity [1] is a popular commercial solution. FOSS solutions include jMonkeyEngine [2] (oriented toward PC games) and libgdx (with a focus on mobile) [3]. Option 2. Instead of writing for Windows, write for Wine. If your program runs in Wine, it should run in Windows (the reverse, alas, is not necessarily true). And you also get support for any platform Wine runs on, including not just Linux, but apparently Intel Mac [4]. [1] http://en.wikipedia.org/wiki/Unity_(game_engine) http://en.wikipedia.org/wiki/Unity_(game_engine) [2] http://en.wikipedia.org/wiki/JMonkeyEngine http://en.wikipedia.org/wiki/JMonkeyEngine [3] http://libgdx.badlogicgames.com/ http://libgdx.badlogicgames.com/ [4] http://wiki.winehq.org/MacOSX http://wiki.winehq.org/MacOSX