Woody Leonhard's no-bull news, tips and help for Windows, Office and more… Please disable your ad blocker – our (polite!) ads help keep AskWoody going!
Home icon Home icon Home icon Email icon RSS icon
  • Amazon Echo Show – gonna be hard to beat

    Posted on May 10th, 2017 at 08:02 woody Comment on the AskWoody Lounge

    No doubt you’ve been reading about the Amazon Echo Show – Alexa with a screen — that’ll ship on June 28.

    https://www.recode.net/2017/5/9/15594724/amazon-echo-show-connected-speaker-touchscreen-smart-home

    Amazon’s ‘Echo Show’ Gives Alexa the Touchscreen It Needed

    I’ve ordered two. Even if I only use them as intercoms, they’re worth $230 each.

    I look at Microsoft’s efforts in the same niche and, frankly, I’m embarrassed. Microsoft is so far behind the mark, and the products they’re just now announcing (but not releasing!) seem antiquated right out of the starting gate.

    (By the way, y’all know that Charlie Kindel, the “director of Alexa Smart Home” and driving force behind Alexa, was once the GM for Windows Home Server, yes? Brilliant.)

  • Google Chrome won’t be allowed on Windows 10 S

    Posted on May 10th, 2017 at 05:05 woody Comment on the AskWoody Lounge

    If you haven’t read Ed Bott’s latest ZDNet article, and you’re even remotely interested in Win10 S, hurry over there and absorb it.

    The approach — forcing browser makers to use the native plumbing — isn’t new. Apple requires iOS browsers to use WebKit, for example (see Paul Krill’s article). We saw something similar with the IE-as-default wars in Windows 8.

    Microsoft’s between a rock and a hard place, but the decision doesn’t surprise me at all. What does surprise me is that it’s laid out in black and white. I expected to see months of waffling.

    In my opinion, keeping Chrome off Win10 S is just another nail in Win10 S’s coffin. But it really couldn’t be any other way.