Comment Re:WTF is an Oort Online? (Score 2) 181
The funny part is, I bet HTML5Test doesn't measure what you thinks it measures...
The funny part is, I bet HTML5Test doesn't measure what you thinks it measures...
What the chart shows is that, for a 50-inch screen, the benefits of 720p vs. 480p start to become apparent at viewing distances closer than 14.6 feet and become fully apparent at 9.8 feet
So, if we are to accept the conclusions of this article, we shouldn't really be able to tell the difference between 480p and 720p until we get to roughly 10-12 feet. That's ridiculous, I could tell a 720p from a 480p image from twice that distance. If you can't, double-check that 20/20 of yours, may be time for a new prescription.
Wait, isn't Tizen supposed to be able to run Android apps?
If that's the case then it might not be as hard to tempt devs if all they need to do is list on Samsung's app store while they attempt to sweeten the deal in other ways (higher margins? free spa treatments?).
In essence the only remnant of Maemo/Meego is Sailfish, the continuation of Mer.
I feel like I need a Tolkienesque chart to keep up with this.
Hopefully by that point project Shumway will have arrived.
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.
Why not Mozilla's Hello service?
It's browser-based, encrypted, open source and P2P.
You do currently have to use Firefox to generate the initial URL to share (but that will hopefully be remedied in the near future).
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;
alert(x);
}
> 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.
Fast, cheap, good: pick two.