What I find funny is how easy it was to install 64-BIT Windows 10 natively on my 2006 Mac Pro. Tells me s little something about Apple's artificial obsolescence practice.
Off topic, but no, it doesn't really. Getting people to write new drivers for old hardware is
expensive, even if the hardware itself can work in a fully 64-bit environment. A couple of the IBM X-series servers from that era that I have in my care won't fully work with Windows 2012R2, so this is really not an Apple-only problem:
If a company doesn't feel obligated to support old crap in new systems, they can focus on improving things, where they otherwise would have to either let old and possibly bad design decisions live on for a long time, or write compatibility wrappings around the old/bad stuff. Apple has done this for quite some time. Microsoft is beginning to learn that the only way to fix some of their old security flaws is by going this way.
The bad thing that can be said about Apples philosophy in this particular area is that because most computers today are connected to the Internet, obsolete hardware that still works runs the risk that someone somewhere discovers a serious security hole that won't get patched. This problem can be mitigated by following basic security principles while using such a computer, and avoided completely by air gapping it from the Internet. The latter pretty much requires you to have a secondary computer which can be connected to the Internet, though; but such a computer doesn't likely need to be a Mac Pro, and doesn't likely need to be part of the work environment that requires a Mac Pro, so it can be had a lot cheaper. On the other hand: You wouldn't have had to save many dollars per month since 2006 to be able to buy a contemporary Mac Pro in 2012-2014.
