HN user
That video does exactly the same job explaining the underlying reasons -- down to using much of the same wording, and the same visuals.
And it was online for a few weeks before this article was published.
> I'm disappointed that the question wasn't answered.
It was answered.
And now disappointed that the article only answered the question? :D
Discussion at https://news.ycombinator.com/item?id=23103610 as well
An arc that spans one radian of a circle's circumference has the same length as the radius.
So if you imagine a connected line of 233 suns across the sky, spanning 57.3 degrees, the actual length of that line would be the same as the distance from your eyes to the sun.
John Conway is actually one of the authors of the book discussed in the article.
The original article is a bit better:
http://www.livemint.com/Companies/lDn53REhqvhqGoIxs9MgwJ/App...
Apple isn't actually prevented from selling either new or refurbished iPhones in India. What it appears that they cannot do, though, is open any Apple Stores there, because they don't (or can't) comply with a rule that "at least 30 per cent of the value of procurement of manufactured/processed products shall be sourced from Indian small industries" (from a similar story about Walmart: http://www.thehindu.com/business/Industry/30-local-sourcing-...)
It looks like what they wanted to do was to manufacture the original phones in China, as always, but do the refurbishment in India, and thereby call the refurbished phones "locally sourced". If they could do that, then they could run their own stores in the country, assuming that the refurb phones made up 30% of their product.
The Indian government rejected that idea, so I presume that Apple will need to continue selling through third-party retail stores, or come up with another way to comply with the rule.
Apparently they have that covered, too: http://motherboard.vice.com/en_ca/read/canada-changed-its-el...
It can't be officially signed until after the election, but they can still negotiate. And all three parties, according to the article, are in support of the agreement.
Big Hero 6 isn't original, if that's what you're saying there -- it's drawn from the same Marvel universe as Captain America and Guardians of the Galaxy.
http://en.wikipedia.org/wiki/Big_Hero_6_(comics)
Heavily adapted for a different audience, certainly, but still not an original story.
From reading http://en.wikipedia.org/wiki/Helium-3#Fusion_reactions, the 2p are two protons, and not positrons, as valarauca1 is saying.
So, 4 protons and 2 neutrons go in, 4 protons and 2 neutrons come out.
But charge still needs to be conserved -- I presume that the spare electrons just aren't shown in the reaction; if they were bound to the protons, then we'd see 2H rather than 2p.
Related to this: https://twitter.com/__apf__/status/551083956326920192/photo/...
HN Discussion: https://news.ycombinator.com/item?id=8838332
And if your problem requires only one of each, and needs them for the same amount of time, then your optimization would be the correct one.
Now scale this to a situation where solving the problem requires ten thousand machines for each developer working on code, and where each minute of time spent writing code translates into two days of machine time running that code, and the numbers start to look different.
This all looks like a lot more drama than it really is. There's a lot of reasonable discussion going on between the two parties now.
See http://seclists.org/oss-sec/2014/q2/681 and https://code.google.com/p/lz4/issues/detail?id=52&can=1 for more recent, measured responses.
It's more likely that it's because they are two separate physical actions (returning the head to the left, and advancing the paper one line). They could be used independently: You could print a line in bold, for instance, by issuing a CR without an LF and then printing the same line again.
A carriage-return operation takes much longer than a single character, or even two or three. It doesn't make sense to issue two characters just to take up time. The printers always had to have some internal buffer memory (and handshaking over the communication lines to say when the buffer is full) in order not to lose any characters.
It seems back now, but in case anyone finds this comment the next time GitHub is under DDoS:
http://webcache.googleusercontent.com/search?q=cache:KNnwGeD...
The first argument, ",8" caused the load to come from the attached disk drive, rather than the default cassette interface. The second argument, as explained by others, was to load binary files into their defined locations.
So you could also load binary programs from cassette with a LOAD "*",1,1
That's not a configuration we'd come across in testing, but I'll check it out.
Can you raise an issue on https://github.com/MobileChromeApps/mobile-chrome-apps for this?
There's almost nothing that you can do with Cordova that you couldn't do with mobile Chrome apps, since, under the hood, they are Cordova apps.
In fact, the plugins themselves have all been available for some time on the Cordova plugin registry (I think Andrew announced this at PhoneGapDay in Amsterdam last year), and you can use them on standalone Cordova projects.
Much of this project is about getting Chrome packaged apps to run as Cordova apps -- that is, single-page apps, with a manifest file, background scripts, and the chrome.* APIs. The goal is that you could take an existing packaged app, build it with this tool, and have an Android and an iOS version running in a couple of minutes. (There are obviously a lot of caveats in that statement; mobile devices are different from desktop in a lot of ways)
There's no intention of being "better" than Cordova -- We've been a big part of the team that has been building Cordova for the last couple of years. If anything, it's a testament to how powerful the Cordova platform is, that we've been able to build this framework on top of it.
It's available to everyone right now; go ahead and clone it from GitHub, or install the cca package from npm -- it's a "developer preview" right now because some of the APIs are still changing; I wouldn't consider it stable enough to ship an app to users just yet. We're definitely looking for people to try it out, though -- we want to know what's working, what's missing, and what's just more difficult than it could be.
The first and last female samples are identical (except for size, they appear to be exactly the same image). Hard to believe that one was identified correctly almost 80% of the time, and the other only 30%.
As a matter of fact, most of the engineers on this project are regular committers to the Cordova project. (Cordova is the underlying project, btw -- PhoneGap is Adobe's build system built on top of it)
We're very committed to the Cordova platform, and we're very active in pushing it forward.
Though there are a lot of individuals, and companies, involved, I suspect that, by any measure, Google is one of the top contributors to Cordova these days.
The overall density of primes is known, and decreases continuously as the numbers get larger (See http://en.wikipedia.org/wiki/Prime_number_theorem)
What this theorem says is that no matter how large the numbers get, no matter how sparsely the primes are spread out, on average, there will always be pairs of primes that are relatively close (within 600 of each other)
Well, it's on github, you could look through the history, and eventually you'd find this:
https://github.com/paulirish/browser-logos/blob/17bbcde4c555...
You can submit the error, with the option of declaring what language the page is really in.
Unfortunately, "JavaScript" isn't in the list.
It's likely to provide some help for compression (rather than minification), if you're gzipping your assets for transfer.
This is probably most effective if you tend to specify the same values for the properties as well, so that a run can extend from one property name through its value and to the next property name.
Clustering properties with identical prefixes will provide some improvement by itself, as it can keep the 'backward distance' values used in a small consistent range, but I expect that's going to be a much smaller effect.
Yes, but:
typeof(["an array", "contains multiple things"]) == typeof({but_this_one: "is an object"})The battery notification looks identical to that in iOS6, and probably has the same behaviour.
If you run your phone with the display off, say from 21% battery down to 11%, then it will cross the 20% reporting threshold. The next time that you unlock the phone and activate the display, you will get the notification.
It's not inconsistent; nor is it just being "optimistic" -- it may be poorly worded, but it consistently displays that same message every time you unlock the phone after the battery drains to 20%.
If the person who took that screenshot had waited another ten minutes, then the battery would probably have reached 10%, and the 10% notification would have been shown instead.
What's with this posting? crypto-gram has been going for a long time (I've been subscribed for at least a decade).
These days (since 2004 or so), the newsletter is essentially a compilation of the month's postings on his blog; If there's something interesting in the newsletter, people usually post a link to the actual blog post.
15:50 UTC: We are working to mitigate a large DDoS. We will provide an update once we have more information.
Except that it's http://fuchsia.bikeshed.com/ :)
This was originally posted on Steve Blank's site here: http://steveblank.com/2009/05/15/supermac-war-story-11-the-c... -- not sure why the WSJ chose to recycle it four years later. This is probably the third or fourth time it's been on HN.