Applenut Said:"perhaps you're too dense to comprehend."
Oh yes, this is serious grey matter. Not sure I can get my cranial region around it sufficiently. "I'm talking about things third parties have refused to support. things that just will theoretically never be supported in OS X.
How about some concrete examples? Maybe give us some idea of of when a peripheral manufacturer or software developer has come out and said "we will not support OS X, now or in the future. Theorhetical = pulled out of your ass.""Other OSes have many of those areas filled in a little by the developer community. even if the software/drivers don't work they try their best. The Mac doesn't have that kind of community and I was asking why?"
For someone with such tremendous cranial capacity, I'm surprised you haven't figured this one out yet. Does the phrase "three months" ring any bells? The API's for OS X are just now reaching a relatively polished state, and the OS itself as well. Witness 10.1 and the Dec Developer Tools, which filled in A LOT of holes with bug fixes, API documentation and such - things those developer types need, I'm sure you'll agree.
There are many examples of developers who have basically been wiating since March for the OS and the APIs to mature a bit (Adobe, Macromedia, Epson, AGFA and Kensington all come immediately to mind). Get it now?"too involved for you?"
Oh clearly. Really involved. I'm breaking out in a cold sweat. How about you...any of this starting to make sense now?
YES, there is a developer community out there that --in time-- will be able to provide unofficial hacks and such to fill in where official drivers aren't there. But just like the official developer types, the hackers need a good set of API's and documentation to work from, and a stable OS as well. We've had both for a sum total of about two weeks now, since the Dec Developer Tools plugged a lot of holes in the documentation - upwards of 700 holes.
Like I said. Next topic. This one is pointless.