The key drawback of steam is that building a steam catapult that can vary its power output well enough to launch both large manned planes and (much more fragile) small drones is rather hard. And people _really_ want to launch drones from carriers.
The scenario you describe is pretty much how it worked, with Google and Netflix doing most of the forcing, and Microsoft only helping out a little bit.
It supports consoles as well, via JSMESS. https://archive.org/details/gg...
Videoconferencing from any device on the planet without installing any special software is bloat?
YES, in the same way that every user on the planet would probably want a calculator once in a while but that doesn't mean the browser needs to add one!
Firefox comes with a couple of calculators built in. It has since before it was called Firefox.
MSE support isn't in Firefox 36.
The Youtube-only thing is currently being targeted for Firefox 37, and enabling it in general for 38 or 39 once the standards-compliance issues are worked out.
Half of the sample is below the _state_ average. As in, below the average of a different sample.
Ignoring average vs median issues, what this says is that folks in SV are no more likely to get their kids vaccinated than folks in CA in general are.
we could have lawful access... that we're prohibited from getting because of a company's technological choices.
Now you know how the public feels when they want to make fair use of some video on a DVD or Bluray.
The funny part is, I bet HTML5Test doesn't measure what you thinks it measures...
Unfortunately, Stephane Charbonnier is one of the people who were killed in this latest attack. I really hope you're right that Charlie Hebdo will keep going, but it's a lot easier to recover from physical damage to offices than it is from having the staff that make the magazine what it is killed.
Browsers are pretty complicated, yes. Things like low-latency high-performance VMs, hardware-accelerated video pipelines, plus the details, like actual HTML parsing, CSS layout, a network stack, and so forth. Also, what matters is not just the complication but how fast you're trying to change things, and people are adding new things (flexbox, more complicated CSS layout modes, mode DOM APIs, etc) faster than ever before.
But also, in addition to a browser Mozilla is working on FirefoxOS, which involves a whole separate bunch of developers, since it's not like the browser developers are writing things like the dialer app for FirefoxOS. Also, you need QA, not just developers.
And yes, Mozilla has 1000-ish employees, for what it's worth.
It's not just Mozilla. If I look at https://www.openhub.net/p/chro... I see on the order of 600 committers with commits in the last month. And that's not even counting whoever is working on the non-open-source parts of Chrome. And not counting, again, QA and so forth.
And the worst part is, this is not a new development. Microsoft had over 1000 people working on IE6 in 1999, according to http://ericsink.com/Browser_Wa...
So yes, browsers, complicated.
The "let" keyword is not the same thing as "let blocks" and "let expressions".
The keyword looks like this:
let x = 5;
and is in ES6. A let block or let expression (neither of which is in ES6) looks like this:
let (x = 5) alert(x);
so that "x" is only in scope for the duration of the let block. It's syntactic sugar for:
let x = 5;
> So you still have to buy an iPhone, an iPad, an
> Android phone, and an Android tablet to test on them,
Sure. The point here is to allow you to use the devtools of your choice, not to create a test environment.