There's still a lot of mainframe stuff out there in cobol, after all. And a crazy amount of DOS. Business moves sloooooow.
There's still a lot of mainframe stuff out there in cobol, after all. And a crazy amount of DOS. Business moves sloooooow.
The beauty of what Google's doing (and a lot of their playing is creating a pointillist map) is in this space: they're making it so I can get (right now mostly) text from one place to another through multiple streams to a final display regardless of ANYTHING. There are still some places file metaphors exist (docs), but that's fading in their newer products. Add robust lines of demarcation (privacy/security via groups) and the 'features' of Word don't beat the 'killer app' of portable, trackable, malleable information that people can collaborate on without effort.
So: watch out, Office. (Though I love what you're doing in Excel)
You know the main problem with Excel? Finding out what changes were made, keeping updates between multiple teams/people in sync, sending the correct version of the doc. once updated, etc.
If Google Docs Excel was as good as Excel today (it still lacks quite a bit, esp in UI), we'd never use Excel, simply to save a huge amount of time syncing everybody.
However, there is a huge ecosystem around Excel - lots of enterprise apps have tight Excel integration and an amazing amount of complex stuff gets done in VBA in Excel.
As to your other point, I've actually persuaded quite a few (very bright) finance people how to use TortoiseSVN and they picked it up pretty easily and seems to work very well for them. Wire it up so that you use a sensible diff tool to show differences between revisions and it actually is pretty civilised. Almost like real code! ;-)
But it's by no means the only option if they fall behind.