![]() Some developers have gone out of business, some hardware is no longer within any sort of reasonable support timeframe, etc. Whether or not a particular developer wants to support the latest operating system is a different issue, of course. ![]() There have been tweaks over time, but there were no "OMG, this is broken and there's no way to fix it other than a complete rewrite" type issues. I have a large development environment (over 1M lines of code) that I've been dragging around since 4.2BSD on a VAX and it still builds and runs on the latest FreeBSD and Linux releases. The platform-independent part is likely being compiled for both 32- and 64-bit modes already. In the case of drivers, there is usually a larger platform-independent part and a much smaller OS-specific part. ![]() Regarding 64-bit conversions, for most code it is relatively painless. From what I've read, the whole "What? You have a printer driver not supplied by Apple? Why?" thing came up when Apple started requiring drivers to be signed and was a bit of a surprise to both the driver writers and Apple. ![]() Windows has driver signing and the additional WHQL certification of drivers if desired. ![]() However, this does point out a flaw (intentional or otherwise) in Apple's developer relations. I don't really have a side in this fight, since the one "Mac" I have is a Windows virtual machine (I have to do builds of some open-source software for many environments, which includes 32- and 64-bit Mac OS X). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |