Ugh.. Ive been exactly in his shoes. He's trying to demo an area, and dogfood an unrelated area (browser). I know when Ive done Azure work before, it'll work in Chrome and firefox. But that's about it. Or it could be some goofy problem with the browser, or how MS handles what browser it thinks you're running, or a million other possibilities. Who knows.<p>But the best way to continue a demo, is just to get the demo done. And frankly, that someone from MS can install and get to work with Chrome/Google, cool. Get it done, then get it right.<p>Tl;Dr. The hotseat of live demos can suck. Really suck. Don't diss till you do one, and it falls apart. There really is nothing worse than having big yuckity-yucks sitting there, tut-tutting you because the "Thing" you're showing off falls flat. You feel about "." this tall.
It’s exactly this attitude of just get it done that has reignited Microsoft.<p>They probably get flack for this, but it shows they’re focused more on results.
From the presenter's comments, it sounds like a GPO locked down Edge. In that context, it makes sense to immediately install another browser and Chrome is the market leader.
Any estimates on what the economic cost of entry is for developing a competetive browser?<p>As someone who has no background doing web development, would also like to hear from web devs on what proportion of a project is spent building features vs handling edge cases in browsers (like the one that was hit here in the article).
I'm sure that the Azure team built their portal to work with the most popular browser and didn't concern themselves with Edge too much, just like every other web developer.<p>Anyway, I like how he unchecked the Telemetry feature before installing Chrome so that he didn't have to "help make Google Chrome better".
This kind of state of mind is what makes me interested in a product.
Being an AWS user, I will have a look right away at Azure (now that they have a free tier of sorts)
He was presenting Azure and the browser was enable to parse a XmlHttpRequest. It could be an error on the browser or on the server side application. Because he is on the server side team he blamed the browser.<p>Rule #1 of pointing fingers: it's always someone else's fault.
To be clear, this isn't a product called "Presenter", this is a person who works for Microsoft who switched to Chrome during a presentation. Nothing to see here.