Microsoft ?
is the next windows update need ARM processor ?
It doesn't require one, but Windows 8 (and Office) are to be provided for ARM. Versions of the ARM architecture have always been popular in small devices, including smart phones for more than a decade, the original Apple Newton and the Nintendo portables since the Gameboy Advance but those 'small' devices are now big enough that it makes sense to try to sell full-fat Windows and Office to device manufacturers.
Windows NT is a little like NextStep in that it shipped for multiple processor lines during the 90s, when it wasn't clear where the market was going, and has only specialised since. So that part won't necessarily be as hard as you might think. Office has a Mac port so you'd hope the core stuff was architecture independent, but the reason VBA macros were missing in Excel 2008 was apparently that they were unable to get them to work within Office:Mac for the Intel port.
Anyway, I'm with those citing an ongoing lack of innovation from any vendor as evidence that the desktop OS market has become stagnant and is likely to remain so for a while. I hope the trend for cleaning things up, shrinking them and optimising them as per Snow Leopard and Windows 7 continues, but only if £25 remains the price.
Re: the main topic; the Core 2 Duos do have an important architectural difference from the Core Duos before them but Apple have used insignificant differences to draw a line in the past, such as the requirement for a FireWire port to run 10.4. OS releases tend to work on any hardware less than five or so years old, so you can expect to get six or seven years out of a Mac before it becomes ineligible for the latest OS (ie, the release after the final supported one) and then, inevitably, for the latest software.
EDIT: as to the future, for a few years, Apple have been transitioning their compiler suite from GCC to Clang/LLVM. LLVM stands for 'Low Level Virtual Machine' — which takes the output of the bit of a compiler that understands C, C++, Objective-C or whatever and converts and optimises it into an instruction stream for a virtual machine. In the normal suite there's currently a compiler step that then converts the results into Intel or PowerPC code. I believe Apple would be more likely to remove the final step and do that at run time, in a broadly similar way to .NET, Java (including on Android), etc, should they plan to offer a single OS across multiple architectures in the future. With the modern ways of arranging these things, such an approach can actually provide benefits beyond architecture independence, allowing a program to be tuned for the specific processor it's running on.
That's all speculation, of course, and quite possibly won't happen. No published materials or rumours currently suggest it.