An important example is when Microsoft launches the web suite for Office 2010 and it potentially runs slowly in older IE versions.
What will also be interesting is how far their backwards compatability travels. Will Microsoft signal the death of IE6 by not supporting their own software in their web Office suite? Unlikely, but interesting regardless.
Interesting question. On the one hand, they could give IT shops a reason to upgrade to IE8. The main holdouts on IE6 are corporations with legacy apps.
On the other hand, such an requirement would give the same shops a reason not to upgrade to Office 2010 at all.
If I know MS, they probably created JavaScript callable stubs for the .NET components already in the OS. This is the same way JScript cheated by calling ActiveX components that shipped with the OS and Office. I would be surprised if MS really embraced web standards. Or we can expect a portable Silverlight runtime which brings ActiveX to non-MS platforms (like Flash, but from an actual tool vendor. Adobe is struggling being Sun and Pixar at the same time; they're speaking to a wide audience with diverging interests)
In this video, Chris Bryant of Microsoft makes an offhand comment that the components of the new Microsoft Office 2010 for Web are "some of the biggest Javascript applications ever built"
Yuk, big does not necessarily imply good. From the video, it looks like they've ported as much of the Office applications as possible directly into the browser. The only UI changes are the pieces they had to disregard because the browser didn't support them.
Whatever "web 2.0" is, it isn't the same old applications now running in the browser instead of MFC.
When comparing Office 2007 (and 2010) with Office 97 one can clearly see these are not "the same old apps".
Especially when combined with the Office Servers.
JavaScript isn't such a bad language. It's essentially Scheme in C cloths. It has first-class functions, lexical closures, prototype-inheritance and more.
yes. I always feel like javascript is never learned "the right way". I feel this way because when I first learned it, I was essentially trying to write java code.
I wonder why no one ever tells javascript noobies that functions limit scope, not {} ?
The reason to develop Silverlight was to kill flash and compete with Adobe. However, Silverlight hasn't been a big success and it's now obvious that if any technology is going to take over Flash, it's HTML5, CSS3 and JS. It seems the best move to take JS seriously for MS. By the way, Microsoft is hosting the jquery conference to come.
Silverlight hasn't taken over yet, and it's too soon to say it's "not a big success" - it looks like it isn't a big failure - from what I heard from Scott Guthrie's public talks, the installed base of SL is on track with MS expectations. SL3 is being pushed quite hard, MS has not given up on it.
It's not obvious that HTML 5 will make Flash/Silverlight obsolete. But it's competition for sure.
It is the nature of MS, being a very large company, when asked to chose between competing technologies, to choose both, so that whichever one wins out, they will be there. Hence, Javascript and Silverlight.
MS has deep pockets, and in both paths is leverage existing assets to cut costs and increase developer familarity - JQuery in Javascript, and .Net and XAML in making silverlight.
Javascript and Silverlight are orthogonal. The first version of Silverlight was only programmable with Javascript. It wasn't until Silverlight 2 that C# was a supported language.
Microsoft is a huge company and the departments are loyal to their own bottom lines before each other's technology investments. The Office team clearly recognized that they needed to support alternative browsers in order to be competitive.
I believe the Office web apps use Silverlight for a few small, optional features (this may no longer be true).
Silverlight supports "Alternative browsers". In fact, it's easier to get the exact same rendered output on screen in Silverlight than in Javascript, since it's running the same engine in all browsers, just via different plugins.
Which, to my (probably outdated) knowledge, is why they used Silverlight for print preview.
The key here though is that I can log in to any random machine with any common browser and use the primary features of Office. Google Docs offers me the ability to read a spreadsheet on a kiosk in a hotel, so Office web better do it too. If Silverlight was required, that wouldn't be realistic until it achieves Flash-level or greater adoption.
I'll see it before I believe it. I'd be very surprised if they didn't somehow manage to cripple it on non-windows os'es. Sorry for being such a pessimistic old man.
What will also be interesting is how far their backwards compatability travels. Will Microsoft signal the death of IE6 by not supporting their own software in their web Office suite? Unlikely, but interesting regardless.