skysight-inc/HackerNews huggingface dataset:
The problem is, typescript will still silently infer 'any' type in certain cases even with all the no-implicit-any compiler flags enabled, and you'll never know when this happens until you have a bug.

Not to mention that its type system is unsound by design, and not because of null. Typescript only pretends to be safe, so in practice you end up writing a lot of type annotations for very dubious gain.

Stricter options like Facebook Flow or Scala.js are way more useful.
Say a trusting trust attack is discovered. Whats the resolution? Do you manually edit the binary? Do you rewrite a compiler in a language with a verified compiler?

Would something like randomizing memory layouts, or reversing stack direction be an easy mitigation or solve an attack like this?
As I said there, Wheeler was exemplary for handling most of this right ahead of time. He gave credit to Karger for inventing the compiler subversion attack. He wrote the reference page on high-assurance FLOSS (for compiler verification) and high-assurance SCM (for repo security, esp distribution). He also wrote a cheat I gripe about in reproducible builds to give us something to work with if high-assurance methods get ignored. Any of his stuff on this subject is worth reading.

Here's his high-assurance and SCM pages:

http://www.dwheeler.com/essays/high-assurance-floss.html

http://www.dwheeler.com/essays/scm-security.html
Some hunter-gatherer groups lived in areas with much greater resources than others, for instance in the Pacific Northwest where they had the potlatches. From what I've read, the Fertile Crescent was such an area. (e.g. https://en.wikipedia.org/wiki/Sedentism#Historical_regions_o...)

I don't know about quarrying stone, though.
It's not really a rabbithole in most cases - unless you have exceptional expertise (and you'd know), you should trust someone else right away, not eventually, because you should trust yourself even less.

Even if you have good reason to believe that all available third party systems are vulnerable to one or another intelligence agency, using that would still be more secure than doing everything yourself, which you can't do properly (noone can do that without extensive review from a large community, so you definitely can't as well), and thus making a system that's vulnerable to everyone.
The five most populous states all feature in the top half of this graph (California 3rd, Texas 15th, Florida 18th, New York 12th, Illinois 5th)

While the five least populous states are mostly in the bottom half. (Wyoming 43rd, Vermont 21st, Alaska 30th, North Dakota 48th, South Dakota 44th)

It is much harder to find a small representative group in a larger population. But I a surprised that the errors appear to favor overestimating trumps margin. I would have thought that the sampling errors would go both ways.

Lots of possible explanations including coincidence, etc. But if feels like it might be some pattern...?
I can't get any useful information from videos, it is so slowwwww. Even on 2x (the fastest I can watch), it is still 3 to 5 times slower than I read. Also, I can control my reading, skip the minutiae, or reread important parts or look up some reference — but I can't do that with videos or audiobooks or podcasts. I wonder how people even find it convenient.

Unfortunately, Rich Hickey really loves videos for some reason, so everything he says is lost to me.

(Yes, there are transcripts, but those are linear and unstructured.)
> Urinals, hygiene/contraceptive vending, and (controversially) changing tables are the big ones.

I think I've seen baby-changing tables at all if not most male restrooms at Google.

Urinals... I've never seen another person's trunk when using urinals. I'd get upset if you tried to look at mine no matter your sex or gender. And I'd get as upset as a woman if you showed it like an exhibicionist, even though I have one too. So I think in practice, at Google, urinals wouldn't ultimately matter.

Hygiene and contraceptive vending I can see how people might want to be more private about.
Instrument-Rated Management: Treating Conditions vs. Symptoms
Yes, I think that's fair to say.

I thought of something else rather important: k8s is truly "containers-first", IE containers are first-class in k8s. So it allowed me to get containers in production in a rock-solid manner without being a Docker expert. This is nice if you're seeking the advantages of promoting the exact same docker image from staging to production, for example.
Üniversiteli Samsun Escort Reyhan Escort Olduğunu Anlatyor
Fears of Trump prompt Internet Archive to make mirror site in Canada
I would. I'm sure I'd there was a game that required root privileges on Linux, I would have heard of it. Doubly so considering it apparently works well on wine.

I don't have CS and don't have any interest in buying it, but I'd welcome being proven wrong.

(I would be more apt to consider telemetry-era Windows a rootkit, personally :)
Unless you're optimizing for raw speed, converting from/to base-3 using your language's standard library should be short and sweet.
For QC to work, the receiver must receive the exact same photons the transmitter created. Those photons can not be tampered with, what means they can not be relayed, or reflected by most surfaces.
Not only that, but the state has exclusive access to heavy weaponry. While some firearms are legal, many are not because they're considered too powerful — unless you happen to be the military, of course. Or the police...

Guns aren't quite as effective as they were in the times of the founding fathers, now that the government has RPGs and tanks and fighter jets, etc.
My pick for the most interesting chemical that he's described does not explode, but rather convinces things to light on fire.

http://blogs.sciencemag.org/pipeline/archives/2008/02/26/san...
I think that the key questions are not what you want or what you want to have but rather what you want to do or even more importantly what you want to accomplish.

Of course in addition UX designers do have their own demons to fight. I would call one of them as cosmic expansion of the space, that is - contrast will decrease and distance between meaningful UI elements will increase over the time.
Big city driving is often not driving at all. Want to grab some milk? Walk to the store. Want to go to a restaurant? Walk.

That's obviously not all city transit but it's a much larger part. Also lots of grocery stores still have parking lots (actually garages) in the city. If you're going somewhere like that you can still park easily. Depends on the location I'm sure.

I'm not sure what your dislike of buses is. They are far more efficient than personal transit from a fuel perspective. A bus can be "nearly empty" and still replace a half dozen cars. And at peak times a bus will replace dozens. There are issues with buses but "soot-spewing" isn't one of them, at least not relative to cars.

Small town is also not really country. If you can drive a few blocks to the grocery store, you don't live in the country. In fact, if your house is near blocks, you don't live in the country. Small towns are of course also less sustainable than cities as small towns are basically built like suburbs.
Randomizing memory layouts and modifying the stack will have no impact since this attack isn't exploiting anything in the language, you've created a compiler that intentionally miscompiles source code. And not only does it miscompile source code, it miscompiles itself so that it preserves the exploit.

One potential way to try to remove attacks like this is to run the source code of the compiler through something that randomizes the structure and text without changing how it actually functions. That way, you may be able to defeat the code that is trying to match on code that looks like the part of the compiler it's trying to hijack.
Great news, but more than any feature I'm excited that this might mean development on Disque is picked up again.
You can use

var now = time.Now
Someone's rant was only 4 words (and then continued with decent criticism) and it inspired you to write an even longer rant instead of adding value to the project at hand.
¯\_(ツ)_/¯
First off, no cavity searches here.

Second, yes I agree the border police take things too far. However, I resent the "but you're taking away the freedom of the press" hyperbole.

Sorry, just because you're a journalist doesn't mean you get a free pass at the borders. Maybe that should be the focus of the story?
Recently I was asked how to get the value of the upper four bits of a byte.
It was asked as: how can I split a byte? Do I need to convert it to bitstring?

If he was a front-end engineer I wouldn't be so surprised but he has 3 years experience working in telecoms, CompSci with networking module at UMass. Uses Wireshark on a regular basis.

A very odd knowledge gap in this domain. So yes I think many engineers don't know these things.
I'm assuming that you are attaching an additional keyboard to your laptop. In that case, I would choose a US keyboard. Some heavily used punctuation characters are in more convenient positions than on a German keyboard (I looked at the MacBook version).

As for relearning, it really depends on how much material you write in German. I'm multilingual and switch the MBP keyboard to suit various languages, but it is a pain, trying to get the various accented characters correctly. I certainly can't touch type in anything but English on the US layout.

If only there was an extended keyboard with all European accented characters accessible with a single keystroke and in "logical" positions. The iPad on-screen keyboard solution to this problem is commendable, but still slows me down.

Maybe a programmable keyboard is your answer, e.g. http://www.touchwindow.com/c/CherryIndustrialProgrammableMSR...
http://man7.org/linux/man-pages/man2/syscalls.2.html
That's cool.

But is there no existing language that can be used to describe state machines?
you use an old compiler binary that didn't have the attack yet to compile the latest source code that it is able to compile, then use that compile the latest it can compile, and so forth.

what I mean is that I wouldn't expect a the 2012 rust prerelease to be able to compile the 2016 rust source code, but it can probably do 2013, use that to compile 2014, use that to compile 2015 use that to compile 2016.

As long as you have a single binary from any point before the attack was introduced it shouldn't be an issue. The whole point is that at no point does the source code contain the trust backdoor, so you can just work forward from any binary that doesn't have it yet.

if the very first version of rust binary already had it as an issue, as well as was written in rust, you could conceivably have a problem though. then you would need an alternative compiler, however sub-optimal it might be...

or you could simply patch and remove the backdoor from the binary and then have it compile itself without inserting the backdoor.
How a Lawsuit Over Hot Coffee Helped Erode the 7th Amendment (2014)
"Unless your assembler, loader, OS, or microprocessor is also backdoored :)"

On the lowest level, you can hand-check it with pencil and paper. Per Brinch Hansen used to write the earliest compilers in ALGOL that he type-checked and tested by hand. He'd then write optimized assembly that visibly matched each function or procedure. He claimed the ALGOL still aided correctness plus served as better documentation of algorithms than commented ASM.

Far as Rust, one could do it by hand if they skipped safety checks and optimizations. Otherwise, do it in older or randomly acquired stuff highly unlikely to be subverted. Many such devices.
> Google is a 'de-facto' monopoly, and they print money. They are super, super rich, and literally have billions more than they know what to do with.

> So it's easy to justify a lot of extra expenses

I see how it can look like that from outside, but from within Google is pretty serious about expenses and costs. All the perks and benefits are an investment to acquire and retain the employees, and to allow them to be as productive as possible.

Remember as an example that Google stock doesn't give dividends: all profits are reinvested in the projects.
Strangely, in Boston they call the dish "General Gau's Chicken". This never made sense to me.

Then again, Bostonians also have a weird taxonomy around milkshakes vs "frappes" (and also "malts"? I'm so confused, and I lived there for two years)
Gobleki Tepeh is such a fascinating site. I love the way it both throws a spanner into historical understandings and alludes to them in interesting ways.

It's not just before agriculture, it's just before agriculture, almost moments before. This is also the area where historians think it first happened. That leaves room for curious ideas like agriculture as a byproduct os civilization rather than the other way around.

The next oldest settlements are newer, less ornate and well.. settlements. No one can even figure out what Gobleki Tepeh was. Doesn't seem to be buildings. The next oldest sites are the likes of Ain Ghazal & Jericho. These were proto-cities with dwellings. They come with some pretty weird ancient art, but at least we can imagine what these people were up to. They grew crops, lived in houses, buried dead, made statues. They fit into the narrative mould history. Megalithic outdoor sanctuary on a bronze age scale before known agriculture or settlements, at a time when people were supposed to be living in small bands? Beautiful mysteries.
He should talk with the Cloud Formation team about their reasons for supporting(it's a full shift in reality) YAML.
I don't know what alot of numbers looks like, but this is what a regular alot looks like:

http://hyperboleandahalf.wikia.com/wiki/Alot
Interesting that they're using JSONPath, which isn't even specified formally anywhere. The only other major implementor that I know about is Kubernetes, which has some odd extensions for templating. (JSONPath itself, of course, isn't very well designed in the first place.)

We're working on a new variant of JSONPath that we're hoping to publish as a formal, comprehensive specification. It's essentially a superset of JSONPath with some syntax warts fixed (like the need to start with $). I wrote a little about it on HN a week ago [1].

[1] https://news.ycombinator.com/item?id=13032391
Especially since the poster is likely not a native English speaker.
Freestyle Olympic wrestling also has many useful techniques for winning a real street fight, and as an activity it builds the type of strength that is very effective in a fight. Worth taking a look at wrestler and BJJ practitioner Daniel Cormier's recent win of the UFC light heavyweight championship over Anthony Johnson, an extremely talented striker, to see why this is the case. Johnson essentially had a small window of time to knock Cormier out, and he nearly did, but once Cormier manage to get a hold of him the fight was brutal after that.

Strength training and general athleticism alone too will often allow you to win over someone who practices a martial art that is purely focused on striking, especially one of the more ornamental ones. Hard to win against someone that can just pick you up and slam you on the concrete ala Quinton Jackson.
Bitcoin Beat the Trough of Sorrow
As verbose as cloud formation is, I really like it. You can represent the entire state of your architecture in a single JSON file: VPCs, EC2 instances, Elasicache clusters, security groups, IAM roles, everything. Updates to the cloud formation template are atomic and can be rolled back, saves you the trouble of writing a long runbook to install your system, and your template can be kept in version control.

You want to talk weirdly over-engineered, check out SWF
Interesting; I wonder if it's a regional difference? Broccoli in General Tso's is nearly universal in the New York City region. I've probably ordered the dish from a few dozen places over the years here, and maybe only one or two omitted the broccoli.
Crossed the US/Canada border probably 30-40 times, both via plane and car. Of the 4 rough incidents I've had with border agents, 3 have been with the Canadians and 1 with the US.

I've had the Canadian border agents accuse me of trying to smuggle in a car to sell (depending on the exchange rate it can be profitable). I've also had them grill me as to why I'm coming to Canada. "Who are you meeting? What will you be doing?". I'm Canadian, you have to let me in!

On the US side, it's mostly "Welcome home!" even though I only had a green card. There was one time when a CBP officer got testy wanting to know who owned the car while my wife was driving. It was more his foul mood than anything.

Logically, you'd expect the US agents to grill me considering I'm not a citizen, not the Canadians.

That said, the US and Canadian border agents work very closely together. They share their lists of "suspects" and are more than willing to hand someone over to the other side if it makes their life easier.

Another comment said that since this happened in a Canadian airport, the guy should have just left. I'm pretty sure the US CBP would have let their Canadian colleagues know about this guy and he wouldn't have made it out of the aiport.
What if your application is not necessarily architected for containers? Have you heard of existing systems being successfully migrated without significant changes in software architecture?
It's not called out specifically in the prose of article, but I think the dimensions overlaid on the image show quite a bit of intentional space left for tolerance around the sides of the battery, and they mention the walls formed by the aluminum carrier around the battery pack. This is pretty clearly intentional "walling off" of the battery from the rest of the PCB, and (I assume) is more protection than other devices were designed with.

If my assumption is correct, though, I find it strange that article footnote seems to contradict this by essentially saying the engineers didn't give enough space around the 'front' and 'back' of the battery. Did they protect the PCB and battery from each other, and fail to protect the battery from the front and back of the phone?
I'm persistently getting an error "Skov is damaged and can't be opened". I extracted the folder from the disk image to my Desktop. I tried right-click->open with the same result (and Gatekeeper gives a different error anyway).

I'm still on El Capitan. Could that be the problem?
The US Department of Defense is a huge customer, for one example.

The current constellation got bought for pennies on the dollar when Iridium went bankrupt. I believe this new generation is the first new constellation they've put up since then. It will be interesting to see if they can make it work. Launch costs are a lot lower now, which ought to help a lot.
I think they did a very good job in discussing it openly instead of going the homebrew-way.
How to Make an Amazing Tensorflow Chatbot Easily
Unfolding the Tesseract (1984)
Starting points for data driven graphics from the FT
I agree, it's a terribly ambiguous headline. Headlines have a way of dropping everything that gives context to a sentence. Makes sense when you're limited to a relatively small piece of paper, but on the Internet you can write as much as you want. So put those extra words back in there! "SpaceX plans on launching a rocket bearing a satellite"... or better yet, "SpaceX plans on launching a rocket containing a satellite".
Who Lives with Their Parents?
You certainly can do this in python and often will need to when dealing with binary formats. The struct library is a great help for this. (https://docs.python.org/2/library/struct.html)
At first before reading the article I was very much against it. But after reading it, it seems a little bit more reasonable but I would really strongly prefer two things if this were to ever get implemented: 1) don't use Google. There must be services that will provide analytics pro-bono/really cheaply for open source/non-profits that aren't tied to a company with terrible privacy track records like Google. 2) make it abundantly clear that this will happen and explicitly give the opt-out instructions the first time (if it was indeed opt-out). As in, "We are enabling user tracking for better usage statistics. If you would like to opt-out, please type <...>." I know that I rarely read changelogs and that if things are not presented to me at installation time they would probably sneak in, through the fault of the Django team or not, but I'd worry that such a thing (notifying users directly) isn't easily possible through pip installations/setup.py.

However, would it be very useful statistically compared to the Pypi installation numbers? Sure, Python is different than NPM because NPM almost always locally installs packages whereas Python installs globally by default, but the numbers must still be high as Django is likely one of the highest installed packages from Pypi and in Python-land in general and as czep points out, because they would only be tracking themselves, it would be hard to compare numbers to anything. It would be useful from a total amount perspective but it wouldn't have any use in comparing to other packages because the kind of data would be different: Django would have usage statistics whereas Pypi has installation/download statistics.

I'm also surprised this is even necessary, since the main purpose of this is supposedly to be able to talk to potential investors for the DSF with concrete numbers. Is Django being basically familiar with every Python developer not enough? I'd really want to know specifically if investors have said they want usage data explicitly, rather than the nebulous idea that it may help make it easier to raise money before I'm more open to the proposal.
Associated repo https://github.com/ft-interactive/visual-vocabulary
I'm pretty pumped about this. Things are looking really good but still not obviously in the clear. Cautiously optimistic :)
Even if you've done nothing "suspicious", you can get automatic screenings just for having a name that is a Soundex match to a fugitive.
"carrying" would have been much better WC.
More like prison and then banishment. I don't get why so many people think that illegal immigrants would take a very high risk, very low reward deal as voting without citizenship. Most citizens don't even like voting, so would it even be a high risk, moderate punishment deal?

By analogy, it's as asking someone to be a drug mule, and if they're successful they get to wait in an extra line at the DMV. Would you take that deal?
Ban all passenger vehicles, cut the size of the roads, expand the subway: you've just made life easier for emergency vehicles to get where they're going. Taxis are horrendously space inefficient in a city choking on people.
SWF is awesome, but it can feel very abstract for most use-cases. In light of this, one of my good colleagues wrote a library called Super Simple Worfklow. It provides the level of simplicity that one would have expected from SWF to begin with. We opened sourced it at my company, check it out[1]. We use this library for production services.

(Full disclosure: I work at Bazaarvoice, and my colleague does, too!)

[1]: https://github.com/bazaarvoice/super-simple-workflow
This site is a lot older than stonehenge. Taking the oldest and youngest proposed dates for the two sites, and Stonehenge is still closer to the present than to Gobleki Tepeh. Ancient Britons were farmers. They lived in village communities that we can picture forming larger societies with religion, organisation and (fabulously impressive) masonry skills.

Gobleki Tepeh predates known agriculture and permanent settlements. It really is a singular site, with genuine mystery.