
Microsoft has recently published the deployment notes for its upcoming 64-bit-native Office 2010 productivity suite. As you may be aware, this is the first time Microsoft has to coded its flagship productivity suite in x64/64-bit binary format. This development is nonessential yet important. Nonessential because the vast majority of documents’ contents do not exceed the 2GB application address space limit but important because future demands always increase (whether that be from document contents or application size). This is also the opportunity to slowly but surely transition the user base to 64-bit while demand for it is still low, minimizing the impact of the transition just like the way Windows XP and Windows Vista’s transition to 64-bit was done when users wanted but not needed the extra capability.
To achieve the goal of a smooth transition, Office 2010’s 64-bit migration path generally follows that of Windows Vista and Windows 7. 32-bit is the default choice for all users, whether or not a 64-bit operation system is running during installation. This means compatibility with existing 32-bit plug-ins, DLLs, VBA code, and the depreciated Equation Editor (MathType) used in Office 2003 and earlier. Only when the user specifically uses the 64-bit Office 2010 setup file will the 64-bit version of Office 2010 be installed. Naturally, upgrading from an earlier version of Office will net a 32-bit Office 2010 upgrade; presumably a clean install is required for a 32-bit to 64-bit upgrade. The other exception is when an existing 64-bit Office program is already installed (like Word 2010 x64) the default setup will choose to install the 64-bit version in place of 32-bit.
It’s been clear from Microsoft that both 32-bit and 64-bit has the same features and functionality and perform quite similarly, and documents saved from either versions will open exactly on both. The one and more pronounced benefit of 64-bit will come from Excel where you can “create bigger workbooks, whether that’s due to tons of data in the grid, tons of charts in your workbook, several really huge PivotCaches supporting your PivotTables, and so on”. (Joseph Chirilov) However the 64-bit GDI subsystem in Windows x64 which the 64-bit SmartArt relies on does not support MMX extensions in CPUs. Whether or not there is a speed difference in rendering SmartArt diagrams remains to be seen.
Overall, this is a positive step that balances compatibility with future development that advanced users can benefit from.









Recent Comments