1,095 karma · joined April 6, 2011
But Greenwald was the one drawing attention to that stuff, by asking Snowden what he expected the US government to do to him. Snowden wasn't volunteering that on his own; it was Greenwald trying to play up the human-interest angle.
I couldn't imagine that Google would actually use Dish's spectrum to build a traditional cellular network. Building all those towers is a huge investment and I didn't think that played to Google's strengths. But, assuming that Loon needs licensed spectrum, maybe Loon (or something like it) was the plan?
As much as I hate how the media is focusing on Snowden rather than the actual leaks, I can't help but wonder what the deal is with that relationship.
Pretty please! Excited to see pcwalton's zero.rs work, which I understand to be a prerequisite for a Rust2JS. But deeper JS integration than emscripten currently provides (e.g., mapping rust structs to harmony binary data StructTypes?) would be even more awesome. When are you going to land 749786, anyway?
Re: Dart and PNaCl--they've been useful for providing political cover to people who want to evolve JS more aggressively.
http://mozakai.blogspot.com/2011/11/code-size-when-compiling...
False. That's what they say, but that's not what they do. When digital broadcast TV was getting standardized, content owners insisted that there be a "broadcast flag" that would prevent receivers from copying broadcast data. There was a bunch of push-back against that proposal, and it died.
And what happened? They go ahead and broadcast everything anyway. It turns out that the broadcast flag wasn't actually necessary. Without the flag, content owner business models work just as well as they did before.
Flash is going away. Silverlight is going away. The presence or absence of DRM in HTML isn't going to change that. Some people remember the frustrations of flash and silverlight and think that the W3C EME proposal will solve those problems. But those problems were solving themselves just fine! Now we get to look forward to a bunch more pain with proprietary, non-interoperable CDMs.
I don't mean to sound negative, I'm just not clear on the point.
Those poor oil companies, being outspent by the Green Party spending juggernaut!
Flash and silverlight lost to an open, interoperably-implementable standard (html). This EME proposal just standardizes an interface to something that's not standard or open (the CDMs).
Some people like to say that content producers will never let up on their demands for DRM. But that's happened already in music and with the broadcast flag, and it's starting to happen in book publishing as well. We should keep fighting for it to happen in web video.
Everything is available pirated already, but people still pay for netflix & friends because they're convenient and most people are honest. If DRM doesn't make it into HTML, there will still be a viable business model streaming video to paying customers without DRM.
The movie is the point of the whole enterprise; it seems like a natural reward.
In that case, there was a bunch of push-back against the broadcast flag, the proposal died, and now all kinds of stuff gets broadcast in the clear. When push came to shove, the content producers didn't actually need the broadcast flag, and their business models still work without it just as well as they did before.
The same needs to happen with the EME proposal; people who care about this kind of thing need to push back and kill it just like with the broadcast flag.
It's sad and ironic; using "who" in object position is a common mistake, and prescriptivists (grammar nazis) often correct it to "whom". But in this case, "who" would be right, but the poster has seen the correction so often that they've applied that "correction" even where it's wrong.
PS - thanks for posting first and giving me an excuse to talk about it :)
They're taking genome size and trying to relate it to time. And the way that they're doing that is to take organisms from the present day, and imagine some of them in the past. The less "developed" or "complex" an organism is, the further in the past they put it. That process is the flawed part.
In other words, the y-axis (genome size) is well-defined, but the mapping of organisms onto the x-axis (time) is not.
The real problem is that "complexity" and "development" in the context of evolution aren't well-defined. So the way that they place genomes on the x-axis is really arbitrary.
> You mean exponential growth, not an exponential distribution, and exponential growth never hits the x-axis.
Right, exponential growth. And yeah, the horizontal line that they're extrapolating back to isn't the x-axis, it's the y=1 line. The point remains: roughly speaking, it seems like small changes to the curve could produce large changes to the x-coord where y=1, since the curve is so close to horizontal there (on a linear-linear plot), right?
- Generation length (faster-reproducing organisms tend to have smaller genomes)
- Transposons (sections of DNA that use cellular machinery to copy themselves to multiple places in the genome; they're usually viruses that got incorporated into the host germline some time in the past)
Genome size isn't anything like a direct measure of "complexity" or "development"; some plants have genome sizes that are orders of magnitude larger than the human genome.
The worst part is that they take genome size sampled in the present day across multiple organisms, and then they assume that some of those present-day genomes represent genomes from particular points in the past. So the x-axis in the regression is basically a guess.
I'm not a statistician, but I imagine that fitting an exponential distribution can make the x-intercept sensitive to data errors.
If you expect the value of bitcoins to keep going up, why would you only hold them for short periods of time? You're suggesting that people would wait until the last possible moment to change their dollars into bitcoins. But by doing that, they're losing money if the value of bitcoins is going up relative to dollars. In that case, the best strategy is to switch into bitcoins as early as possible, and hold them as long as possible.
So how does clang do on nbody.c?
So it's nice to see some non-mozilla involvement and momentum in Rust/Servo. Maybe that means that an investment in learning/using Rust is that much less risky :)
[1] http://www.mail-archive.com/dev-servo@lists.mozilla.org/msg0...
Ack, I hope GLSL shaders are well supported. It would be terrible to have to write a whole second set of shaders in HLSL for IE.
https://github.com/zpao/spidernode
but then they dropped it.
[for (x of a) for (y of b) x * y]
but those would be really nice as well.
A few months ago the ES committee decided to switch them from reading right-to-left (as in spidermonkey comprehensions, python, and haskell) to reading left-to-right (as in C#):