That's an attitude I love to see. Especially since OS X updates are now free and afaik all hardware that supports 10.9 will run 10.10.
Very nice looking and polished job!
The user experience comes first, no compromises. But please note that I'm not saying that I'll drop support for 10.9 because there's some convenient API on 10.10 that will save me a few days of work. 10.10 would be a requirement if and only if it provides a meaningfully better experience.
I also think some developers might start requiring 10.10 for their next major versions, assuming they have been designed in line with Yosemite's new visual language. Supporting both < 10.10 and >= 10.10 UI-wise would involve non-trivial amounts of work, would for most small indies would be impractical.
Because when OSX n+1 is released, it's immediately impossible to get any work done on OSX n?
I'm still on 10.6 and see no reason to upgrade.
No - but the same logic applies to application software, right? If SuperApp m+1 requires OSX n+1, surely you can continue to get work done with what you have now - SuperApp m running on OSX n?
There's no reason for developers to handicap SuperApp m+1 by avoiding all OSX n+1 APIs...
No, but as a developer, I can do much more on OS X n+1. And you're not even on n, you're on something like n-4.
Curious though, is it hardware holding you back, or do you simply not like the direction Apple is going with OS X atm?