Your forgot Nihonium after Japan :-).
It's fairly common for them to be named after places (often where they were discovered). Some other examples are Americium, Berkelium, Californium, Darmstadtium, Dubnium, Europium, Francium, and Germanium.
4,793 karma · joined February 14, 2011
my public key: https://keybase.io/sangaline my proof: https://keybase.io/sangaline/sigs/uKMqGQ_auE6z2qTdrkpZihnoA-DcJ4BeHb35KLA1KZI
It's fairly common for them to be named after places (often where they were discovered). Some other examples are Americium, Berkelium, Californium, Darmstadtium, Dubnium, Europium, Francium, and Germanium.
For example, take a look at the states where Clinton performed best in the primaries. They're Mississippi, Alabama, South Carolina, Georgia, Louisiana, Arkansas, and Texas. All of these states were decisive victories for Trump in the general election and from a perspective purely of wanting to win, it doesn't make sense for them to be so important in the primaries. At the same time, Bernie won a number of states in the primary that ended up being important swing states (e.g Michigan, Wisconsin, New Hampshire, Maine, Minnesota, Colorado). From a strategic standpoint, it would seem to make sense to attach a higher weigh to those victories (the same is also true for Florida, Ohio, and some other states where he lost).
None of this necessarily means that Bernie would have won, I just think that it seems as though the primary process is not very well designed for choosing the best general election candidates. This is even more true if you consider what a large proportion of states have closed primaries that specifically exclude independents. It seems obvious that they will be far less likely to vote along party lines in a general election but, in many states, they're given no say in the primary process. I can understand why the DNC can't just say, "sorry, but the deep south doesn't count and neither does New York or California," but opening up the primaries seems like a perfectly reasonable strategy to put forward stronger general election candidates.
I don't really have a broader point beyond that, it just seems like the parties really set themselves up to produce such, to put it gently, sub-optimal candidates.
I recently started feeling like it might be time to upgrade my 1st gen Carbon X1 and after doing some research I found myself really disappointed by how little the laptop landscape has changed over the last four or five years. After giving it some thought though, I realized that I do virtually all of my work at one desk anyway and decided to look into some desktop options. I found that you can put together something in a mini-case with an i7 processor, 64 GB of DDR4 RAM, 2 TB of SSD, a 28" 4k monitor, a mechanical keyboard, and a high quality mouse for less than about $2k dollars.
This made a lot more sense to me than spending a similar amount on a laptop that offers only marginal improvements over my current one. The obvious trade-off is portability but I would guess that most of us here already have laptops that are "good enough" for most purposes and which could still be used as necessary.
> The token shows the location in such a way that a future civilization will be able to interpret its correct meaning. This will require a technical and scientific understanding which is comparable to our own. This is the guarantee that the archive is suitably protected from premature access. Only a civilization which fulfils these requirements will be able to find the archive as well as being able to process, decipher and comprehend its content. The depiction on the token: Two intersecting lines span a map of Europe.
You're right about them not matching exactly; I did it in a hurry and wasn't looking closely enough. I removed that incorrect statement (though it does seem to generally outperform the simulated annealing).
The tie breaking for pairs with equal differences and the parity of the image is essentially random. It is deterministic in the code, because it won't replace a candidate unless it's strictly better, but it's totally arbitrary which is found first.
On a different note, if this quote:
> The unscrambling problem being solved here is much harder than a typical unscrambling problem, because we are rearranging single columns of pixels.
is referring to reconstructing shredded strips of paper then it is laughably false. The single columns of pixels are extremely clean and correspond very, very closely to their neighboring columns. In reality, the tearing of the paper makes the edges not match very well and it's just much noisier in general. I've worked on this problem before and it's many orders of magnitude more challenging than the reconstruction that is done in this demo.
A lot of people have a tendency to think of each tab as corresponding to a single open file. This is very understandable because it closely matches the paradigm of most IDEs but it's actually an anti-pattern in VIM. Tabs are really meant to be more like workspaces where you arrange multiple windows into a desired layouts. You then have one buffer for each file that you're dealing with and view them in your windows. It's perfectly fine for multiple windows to share a single buffer or to switch out the buffer that is being viewed in any given window. This StackOverflow answer [1] and this blogpost [2] both go into a fair bit more detail.
If you're trying out this approach for the first time then you probably want to add `set hidden` to your configuration in order to avoid automatically closing buffers that aren't currently being viewed in a window. Coupling this approach with fzf.vim [3] makes managing very large numbers of files a breeze compared to using one tab per file.
[1] - http://stackoverflow.com/a/26710166
[2] - http://joshldavis.com/2014/04/05/vim-tab-madness-buffers-vs-...
Having different browsers compete on things like this and then having the better technology become standardized and implemented in multiple browsers seems like a fairly positive outcome.
[0] https://wiki.mozilla.org/WebExtensions
[1] https://addons.mozilla.org/en-US/firefox/addon/chrome-store-...
As a side note, the synchronous request processing is more a consequence of Python rather than flask itself. I've personally found that I build more scalable things in Python, compared to something like node, because it lends itself to scalable architecture decisions. You can do a lot of things in node that are super convenient when you have a single server but that require major changes when you expand.
[1] https://github.com/Shougo/deoplete.nvim
By the way, are you on Android? It lists the permission in such a way that it makes it sound like we're looking at all of the local wifi network names (which we absolutely aren't!). I wish the permissions were more granular.
We just launched a browser extension [0] for taking screenshots of Facebook posts and we were basically tasked with accomplishing the same thing. We approached it by fetching all of the external resources and inlining them as data URIs, wrapping the HTML in an SVG element, drawing the SVG to a canvas, and finally extracting the data URI for the canvas. It works really well and eliminates the jitter/delay associated with scrolling around to capture multiple screenshots.
Good thing we also automate the anonymization of private information or this announcement might have obsoleted us on Firefox :-).
You might also like to check out an example of the image pages that people share [0]. We're really looking forward to getting some feedback from HN and are happy to answer any questions that you might have.
[1] https://github.com/sangaline/dodona/
[2] http://sangaline.com/blog/optimizing_for_swype/FITALY.html
They were probably referring to the oil depressions being visible but the title is certainly misleading.