3 ms·
Not so sure this warrants the negative comments. I mean, I'd rather see them go this route than not go this route. There's some indirect implications of this t
by thorax 17y ago
Not so sure this warrants the negative comments. I mean, I'd rather see them go this route than not go this route.
There's some indirect implications of this that I like, too--
By Microsoft's account, Office web is probably the largest javascript/ajax app ever written (or at least really big). They also support Firefox, Safari, and (maybe) Chrome.
I can't fathom how this won't put Microsoft into the javascript performance arms race with IE. How can they not invest heavily in making their own browser lightning fast with complicated ajax apps when all the browsers they support will perform better with Office web than IE?
Just seems to me that with every browser competing to have incredible web performance and compatibility, we're all going to win a bit in this case.
- catch23 17y agothey might cheat and just use activex objects. Of course this means that office won't work on non-windows computers, but I have a feeling they won't care about supporting those.
- thorax 17y agoFrom what I read, it sounds like they use mostly JS (as it works in Firefox and Safari). I did see mention that perhaps a few corner case features use Silverlight (which I expected to be 100% of the features), but it remains to be seen how much they depend on that.
- catch23 17y agoI only mentioned it because another company (Intuit) has Quickbooks available online via the web, but you need a copy of Quickbooks in order to run it because it uses ActiveX objects that reference libraries from Quickbooks. Strange way to implement their web strategy!