The best reason I can think of is portability. Visiting your parents and using their computer? No need to install a native app, just open the web page (hopefully in the future at least, this says you still need to install a plug-in). Want to use it on Linux? No need to wait for Microsoft to update the Linux app (if they ever bother to update it), just use a standard-compatible browser to open the web page. Microsoft wants to add features? No need to make sure it works on a bunch of different OSes and versions, just make sure the web page is still compliant with the standards (you still need to make sure the browsers handle the standards correctly, but this should be an easier target).

Not that this is perfect by any means. But nowadays computers perform well enough that most users won't even notice the problems you mention, and the other advantages more than make up for the problems.

If the goal of your design is to provide a thin phone made out of a material that provides a premium look and feel, but then users need to put the phone in a giant rubber case to prevent it from breaking, you failed at all the goals of your design.

But Google doesn't market Android as "It just works"

That's true, but that's a smartwatch problem, not a Moto 360 problem. And a smartphone problem. And a tablet problem. If you're already traveling with electronic devices (and the Moto 360 is useless without at least one), it's just one more charger to pack.

I suspect the number of people wanting to strap a device to their wrists for sleep monitoring are a very small subset of the potential smartwatch market. The changes you suggest would hurt the already struggling battery life of this thing, and make it bigger to boot. Given the small number of people that would take advantage of those things for sleep monitoring and the number of sales that would be lost due to the battery and size changes, it wouldn't be worth it.

I've seen a lot of people on this site bash smartwatches if they have less than a week of battery life, and that always seemed like overkill to me. I suspect a lot of people (most?) are like me and take off their watches at night anyways. As such, placing it on a wireless charger dock at night doesn't seem like a problem - as long as the watch has enough battery life to get through the day until I take it off at night. Which is doesn't, according to these reviews. I don't know if I like the look of one enough to buy one anyways, but that would keep me from buying one even if it was better looking.

He never said "not evil". He said "typical big company evil", which is still evil, just not as bad as "phone company evil". Besides, as others as mentioned, he's talking about the American T-Mobile, which is a good bit different from the European version.

The slight curvature also reduces visual geometric distortion. When you watch a perfectly flat TV screen, Soneira explained, the corners of the screen are farther away than the center so they appear smaller.

I have a 30" computer monitor at work, and while I like it better than my old dual-screen setup, I've noticed this issue with windows placed close to the edges. I wonder if there are curved computer monitors in the works, or if this is just for huge TVs. The main problem mentioned with curved TVs (distorted view for anyone off-center) would rarely be a problem with a screen that usually only has one viewer, and it would fix the edge distortion problem.

Or I could have just kept reading to the next line where they say pretty much the same thing.

Mozilla would have preferred to see the content industry move away from locking content to a specific device (so called node-locking), and worked to provide alternatives.

Instead, this approach has now been enshrined in the W3C EME specification. With Google and Microsoft shipping W3C EME and content providers moving over their content from plugins to W3C EME Firefox users are at risk of not being able to access DRM restricted content (e.g. Netflix, Amazon Video, Hulu), which can make up more than 30% of the downstream traffic in North America.

Translation: We don't like this, but if we boycott it we are going to lose users to browsers run by companies more concerned about keeping media companies happy so they can keep licensing content.

This is why I've never bothered with do-not-track settings. Not only is it wholly unenforceable, but it seems like a giant "Look at me!" sign. Given that the vast majority of people don't even know do-not-track exists and never change the default settings on any program, surfing with the do-not-track flag on seemed like a great way to tell the people I really don't want tracking me that I'm technically literate enough that they should pay closer attention to me.

The surrounding metro areas may not have the dirt cheap rent like the city, but it is still going to be *much* cheaper than places like San Francisco. And if don't want an hour commute into the city, try living some place closer to the city than Troy.

Note that this article is about "metro Detroit", not "Detroit". Plenty of safe places to live in the Detroit metro area, especially on a tech worker salary, they're just outside the city proper. And even if the jobs were in actual Detroit, it's still possible to commute from outside the city. But whatever, it's an article mentioning Detroit, let's just bash Detroit.

Well, the key word in my original post was *eventually*. Stuff like ESPN3, MLB.tv, and March Madness on Demand work already, I don't think it's too far out there to either increase bandwidth or develop more efficient protocols to handle more customers in the not to distant future.

I'm not familiar enough with the inner workings of a CDN to say specifically, but I'm pretty sure something similar can be set up for live events. Instead of sending a single copy of an old show to a CDN to be distributed to all the downstream end users, a single live stream could be sent to a CDN equivalent and that could be forwarded to all the end users. Of course, I'm just a lowly end user spitballing here, so maybe I'm missing a huge hang up that would prevent this from happening.