> IMO, > this is the cost-effectiveness you should be striving for. If you > can achieve it, you will reap the requisite revenue to justify that > noble action. Really taking care of your customer base. Could there > be more air-tight business case?
If I had 20 sharp programmers sitting around looking for something to do, and a wad of cash sufficient to bankroll them for two years without concern for maintaining profitability quarter after quarter, I *might* put *half* of them on 64 bit development. The other half I’d put on strategic stuff like tool prep for Longhorn and Whidbey, with an emphasis on finding or creating “breakout” solutions.
64 bit computing will definitely be a force in the mainstream Real Soon Now. It’s not a question of *if* 64 bit will happen – it’s already happening. It’s a question of “How will it be surfaced?”.
Fundamentally, Win64 has all of the same problems and limitations as Win32. No object model, no language interop, manual DLL function import declarations, manual this, manual that, manual everything. It’s the same old schlock with no real “breakout” opportunities. It’s familiar enough to be comfy-cozy, but it’s not different enough to let you to do software better.
I view .NET as different from all of that. It’s different, it’s scary, but for the right reasons. With .NET, the definition of what is an operating system platform is going through a massive consolidation *right now*. This consolidation of services and functionality is producing a more coherent, more productive, and more flexible foundation for application development. This will be a springboard which will propel new software development models providing built-in service levels that only a few years ago were filed under “fantasy fiction”.
That springboard only works for those who are looking for it, and ready to jump on it when they recognize it for what it is.