skysight-inc/HackerNews huggingface dataset:
They can't. In order:

Eve is a murder/capitalism simulator and has almost no physics in the first place. (There's 3-dimensional positioning, but you can fly through planets and shoot through other ships as much as you like; also the entire world is static.)

No Man's Sky is 90% an art piece with some added murder simulation.

Elite: Dangerous, also a murder/capitalism simulator, only unlike Eve it's more about the immediate visceral.

Notably all three of those pretend space ships are, like WW2 planes, subject to air drag, have a terminal velocity and have no automation on-board whatsoever, and astronomic physics aren't even considered in the first place. These games are literally WW2 fan fics in "space". (Or really, ether, as old-timey people thought of what's between planets.)

If you're looking to teach physics and astronomics, Kerbal Space Project does that quite well, even though it also ignores relativity and speed of light considerations.

More importantly, none of these games are even remotely able to tackle the topic of civiliations and saving them, which won't be done with a gun, but with the word. The closest thing i can think of to that are the Mercenary games: https://en.wikipedia.org/wiki/Mercenary_(video_game)

Edit: Not saying that the three mentioned are bad games, just that they can't be taken seriously as space games.
I'm not sure I always agree with this. David Beazley's 2015 PyCon talk on concurrency (https://www.youtube.com/watch?v=MCs5OvhV9S4) was one of my favorite talks of the conference, and it was almost all just live coding.

Part of what made that talk compelling was that it took a concept that lots of people find complex/intimidating (how the internals of an asynchronous IO library work) and in ~30 minutes created a full working example in front of a live audience. Writing the code live in front of the audience helps to nail down the central theme of "this stuff isn't actually as scary as it looks".

There are certainly talks that would be better of just presenting snippets of code, but I think there's a time and a place for live coding examples as well.
Muse Brain Sensing Headband Teardown
And it's interesting, too, how often people go in the other direction, and seem to think "any shred of theory, however improbable, means you can't be found guilty", and attempt to try to classify it as "beyond any/all doubt".
I believe you are right about the direction. :-)

Point still stands, DNS hierarchy doesn't imply culpability or legal responsibility in either direction.
OS X 10.7 is unsupported as of October 2014, so I doubt Apple will be doing anything special to fix it. It still sucks that there's effectively a time limit on the software on your machine though.
Wow, never thought I'd see slowbeef referred to as a YouTuber.

I helped a bit with his work on Policenauts but we haven't kept in touch since then. Maybe I'll try to get involved in this.
Living coding isn't lazy, unpracticed living coding is lazy. I find live coding to be a lot more effective than explaining code that's already there; as a speaker, you have the opportunity to explain the reasoning behind and relationships between each line of code.
The scientific can’t be destroyed, but the scientific infrastructure can be. To do experiments and make scientific breakthroughs you need access to a wide range of skills, equipment, and reagents. If this goes it will not be easy to get it back.
These are generally pretty popular:

https://www.youtube.com/watch?v=a9xAKttWgP4

https://www.youtube.com/watch?v=DmT80OseAGs
But these apps aren't paid for by subscription.
I'm not about to change the floating-point type to a non-binary support.

I think that 15 digits is the "right" value for ordinary display purposes. If you present a literal value of up to 15 digits to the machine, it gets converted to some approximation which, when printed back with 15 digits of precision, gives you the same digits.

By using 15 we avoid this:

1> (let ((*flo-print-precision* flo-max-dig)) (tostring 0.3))
"0.29999999999999999"
2> (tostring 0.3)
"0.3"

I have no "rounding error" because I haven't performed a calculation. I understand that when I enter 0.3 into the machine, the floating-point value isn't exactly 0.3. I have an error, because the representation can only provide a close approximation of 0.3.

Yet I know that this approximation is so close to 0.3 that I would like it printed that way. Now of course it will be printed that way if I round to, say, four places. But that will throw away precision for other numbers. If I round to DBL_DIG digits (15), I get the maximum precision, without having my input numbers altered into something else.

It is useful and elegant for the default printing precision to be as high as possible, yet such that numbers that I enter into a REPL are echoed back at me pretty as I entered them, modulo choice of notation.

No, of course, DBL_DIG doesn't guarantee that I can do any sequence of calculations, like 0.3 - 0.2 - 0.1 and still get back a result which is exact to DBL_DIG digits! There is no lower bound on how inaccurate a floating-point calculation can be, if it is carried through enough iterations!
None of these things are really a problem any more. Scala has come a long long way since 2011.
It's not so clear cut as you seem to think. A lot of science is graspable in its essence by people who would struggle with the mathematics. And a lot of scientific journals are written in unnecessarily difficult prose. As for lawyers interpreting the law, well the law is much more complicated than science in several important respects: it is not a single system based on a small set of fundamental axioms, it is not even required to be consistent, it is continually changing.

Also, even if we do get a dumbed down version of science then, so long as it is still science, we can build upon it.

I'm glad you put 'agree' in quotation marks because of course people in general do not agree, they have in fact no option but to pretend to agree or forgo the service.
It's being downvoted not (necessarily) because people think it's offensive, but rather because it's hypocritical.
Except for the original game, which used procedurally generated galaxies, and didn't feature Earth. This was the only way to get the game to fit into the 32K RAM of the original BBC Micro.

https://en.wikipedia.org/wiki/Elite_(video_game)
> The "misrouted investments" you speak of, are only possible, on any large scale, by an ever increasing money supply provided by a central bank.

As he pointed out, not true, it's also possible by too much centralization of wealth, i.e. inequality. Inequality happens regardless of central bank interference with the money supply.
All the same tricks could just as easily be applied to (wget|curl) pipe to shell scenarios.
I haven't had occasion to use it in anger, but I keep doitlive[0] in my back pocket for such things. 'Live' typing, but repeatable and working each time.

[0] http://doitlive.readthedocs.org/en/latest/
An old video, but still a fun one for getting an intro overview of the language: https://channel9.msdn.com/blogs/pdc2008/tl11
You're assuming the goal is to teach astrophysics, rather than astronomy. If we're just trying to teach the space equivalent of geography, the physics and plot don't matter so much as the physical locations and nomenclature.
Ask HN: How do you see the VW emissions scandal panning out?
I've been following the VW emissions scandal with a mix of interest and horror, and I'm curious about what's going to happen next.

In particular, what will the fix look like? What if the fix actually leads to less favourable engine characteristics and people refuse to take their cars in?

Just curious about what people's opinions are here.
Not publishing negative results is a symptom, not a cause, of the current extreme competition in science. Fix the competition issue and we will fix problems like the non-publication of negative results.
More than the specific problems with collections that he talks about, I think the problem of allowing clearly broken methods into the standard collections is the real issue. Why would they accept an implementation f map where map isn't safely composable? Why would they use incorrect type signatures? Why would they allow so many casts? I haven't finished the video yet but every issue he brings up seems to be about more than a mistake in a library.

It looks to me like you can't trust Scala because the people behind it are ok with accepting clearly broken or poor quality implementations.
Radioactive copper can't stay radioactive long. The longest-lived isotope is 64Cu, with a half life of 12 hours.

Mildly radioactive junk is not that rare. Stanford used to have a little fenced area near the toxic waste incinerator with stainless steel parts left over from accelerator experiments cooling off. 55Fe has a 2.7 year half life, so you let it cool off for a decade or so, then recycle. The only protection was an chain-link fence, a radiation warning trefoil, and a street light. One day somebody cut the fence and stole the stainless steel, prompting a search of scrapyards. But the metal was near the end of its storage period anyway, and wasn't detectable as radioactive.
Thanks for the video, looks interesting.
> The compilation cost for a dynamic language like Javascript is zero, the cost being completely amortized with everything happening directly at runtime.

This is one of the big points I always try to make to people. JS compilation is cheap and maybe it's faster to spit out some functional code. But all you've really done is pushed the rest of your work to tomorrow. Your type verification happens at runtime, and now instead of your bugs being compiler errors, your bugs are production errors that you've exposed your customers to.

With Scala I rarely need to use the debugger. With JS and PHP I have to constantly use the debugger to track down "what type does this variable actually have in this random edge case at runtime?"
This rings true, regarding training... lost an opportunity this year because I hadn't used Django REST framework yet, even though I have years of Django and REST experience separately. Probably would have taken the better part of an hour to fill that deficiency.

Part of the problem are the blog posts that became fashionable a few years ago. The ones that talk about accepting only 10x developers, and the "horrible" outcomes of hiring the wrong person. While they have truth to them, what a disservice they have done to the industry. Hiring managers are now frozen in fear and inaction. Not everyone can be a "unicorn" but certainly even average developers can crank out good web apps with occasional guidance and high standards around them.

Since most places are looking for multiple devs, why not hire an extra and cut under-performers when that becomes clear in a couple of months? Start them with low-context tasks.

Besides the race/gender problem, another issue is the age thing, which the article didn't mention. Imagine an other industry where people with experience are excluded! "Only 28-year old white guys with beards need apply". No, your new event-driven web framework is nothing special that hasn't been done a hundred times. But those in charge now unfortunately don't have the experience to know that.

Oh, and the pay problem, despite tech companies sitting collectively on trillions of dollars.

So there we go, this "tech shortage" seems to be mostly self-inflicted IMHO.
My belief is that the effort os a linear function of your code base size. This means the larger the code base, the more effort required to port.

Also, porting is made more difficult by the fact that Python is a dynamic language, so a lot of errors that could be caught at compile time will only be catchable through a thorough testing suite. I have seen little evidence to suggest that porting from Python 2 to 3 is actually straightfoward in the sense of not requiring significant effort proportional to the size of the code base.
I tend to think of Time Series data as being several orders of magnitude larger than 23 million data points per week (38 per second) but now I can't seem to find a good definition of Time Series data. Anyone have thoughts on the rough threshold between event data and time series data? I think of arrays of hundreds/thousands of individual sensors that take 10 measurements a second as "different" than user generated data that is time-ordered.
It's also incorrect. The 2035 number is the root certificate. The leaf signer is (as of last night): Not Before: Sep 24 19:09:31 2015 GMT Not After : Oct 23 19:09:31 2017 GMT
The point of live coding is to show it works. Which is always nice to see! Also, for instruction, glad you are hyper smart, but I for one can't follow that fast if it's completely knew to me. Live coding demo I can usually follow better than a video.
Astronomy is the study of the laws of stars, not of their names, regardless of how close "nomy" sounds to "name".

https://simple.wikipedia.org/wiki/Astronomy

Additionally Sagan was most certainly conflating it with astrophysics, as is commonly done, and evidenced by his mention of "stellar evolutionary events".
https://news.ycombinator.com/item?id=10546717

And

https://news.ycombinator.com/item?id=10527860
I came here to say exactly this and link to that talk. If you can't code live then don't, Beazley apparently can. Python lends itself to these kinds of talks because of its brevity.
If anyone has questions about starting app from react native I would me more than willing to chat! Ask away.
Earth's Water Was Present During Planetary Birth
Agreed about ease.

The first time I reversed anything was when I was playing a shareware game on my mom's Quadra 650 running Mac OS 7.6.1. I was maybe 12 or 13. I had reached the end of the game's limited demo, and it asked me to enter a code.

I discovered that a program called "Super ResEdit" would open up the game and show me its internal resources. Icons, text, menubars... and also a long column of lines that looked something like "ADD R1, R2, R3" and "CMP R2, R3" and "BNE +0x8".

Anything of the form "B ..." or "BEQ ..." or "BNE ...", when I moved the cursor over it, would develop an arrow pointing to a different line. Aha! "B" stands for "Branch". In that case, "BEQ" stands for "Branch if equal", "BNE" stands for "Branch if Not Equal". It must be that "CMP", which usually preceded one of these lines, stood for "Compare"...

After that it was a matter of finding a section called "do_registration_check", seeing a bunch of arithmetic ("ADD", "MULT"), then a "CMP" followed by "BNE". Apparently if I entered an incorrect code, the "Branch Not Equal" path would be followed. I didn't know about NOPs at the time, since the compiled code didn't have any, but I could change a "BNE" to a "BEQ".

Super big rush! Discovering, on my own, how to take something apart and bend it to my will.
That's really cool. It sounds similar to Squashed Image support on Quay.io[0]. Is it open source?

[0]: https://blog.quay.io/New-quay-features/
I came to the comments on this one just to make sure this talk got mentioned as a counterpoint. Fantastic explanation of everything as he went along.

As I recall, he actually took the same conceptual problem and rewrote the solution in a handful of different concurrent styles.

And no, at least in this video I can not think faster than Dave Beazley can type. By the time I've just about figured out what nuance of concurrency he's showing off in his last example, he's already got his next example typed out!
1. Go to HN to procrastinate.

2. Find article on how to not procrastinate.

3. Ack.
This is pretty interesting. It would be great if there was a step-by-step guide to check my own Docker containers. Instead of looking like a piece to promote Quay.
Sylvia Earle and her work to protect the oceans
Live coding doesn't mean a poor presentation. Thought bad live coding generally does. I don't want to see someone stumble around, but Jim Weirich's live coding of katas turned me on to a lot. Not only katas, ruby, but how he coded- refactor menus, etc. Extremely valuable.

https://www.youtube.com/watch?v=WBJ3hdcM7G8
It is a weirdly common misconception that the agreement in question requires the US and UK to protect Ukraine's territorial integrity. All it does is require them to respect it. This is the actual wording, taken from your link:

"The Russian Federation, the United Kingdom of Great Britain and Northern Ireland and the United States of America reaffirm their obligation to refrain from the threat or use of force against the territorial integrity or political independence of Ukraine, and that none of their weapons will ever be used against Ukraine except in self-defence or otherwise in accordance with the Charter of the United Nations."

Basically, everybody involved pledged not to attack Ukraine. They made no pledge to protect Ukraine from other attackers. The only signatory who has violated the agreement here is Russia. The agreement does not require the US or the UK to protect Ukraine from Russia.

(Strictly speaking they are required to ask the UN to defend Ukraine if they are attacked or threatened by nuclear weapons, but that hasn't happened.)
I can already sell anything to anyone, anywhere.
Yeah 1400 sq/f is almost double the average household size in the UK unfortunately...
http://www.dailymail.co.uk/news/article-2535136/Average-Brit...
It's quite a shock especially for Americans who move to the UK many to London then going to see flats just to get a reality slap when a 2 bed flat is the size of their old garage in the burbs..

And I personally don't know if I should laugh or cry every time some one links me a "tiny house" video which turns out to be larger than my flat (and the flats of most people I know that don't live in a detached house) which costs about 3800$ a month in rent...
Obviously a single query is faster than a join, but it's very hard to guarantee that you'll always be making that single query.

Data inconsistency is not about concurrency. See this example on Wikipedia illustrating why 3NF is necessary: https://en.wikipedia.org/wiki/Third_normal_form#.22Nothing_b...

In that example, "Al Fredrickson" can potentially have 2 birthdays even in an entirely single threaded app.

I'm really curious to hear a use case where Mongo was actually significantly faster than Postgres. Could you give a toy example that illustrates the flavor of the problem?
Some hints on controls would be nice. Also, in chrome the top two things aren't clickable. Otherwise, this looks adorable!

Edit: I wonder what kind of horrible people would downvote the parent post.
Submit Spark Job Using REST Api in Standalone Mode
I recently went to the Walt Disney Family Museum in SF for the special exhibit "Disney and Dali" (still there until 1/3/16). It's an interesting look at their mutual admiration and brief professional collaboration.

The regular museum is also well worth a few hours of time, even if you don't consider yourself a huge Disney fan. Walt was an incredible innovator and risk-taker and I found it very inspiring.
I agree with you, but I'm probably biased because I've used live coding in one of my talks. However, the intent of coding live was similar to the talk you mentioned - it was to show people that what I was trying to accomplish isn't as hard as people think it is. In fact, it's easy enough that I can do it in an hour while explaining out loud what's happening.
Whether a demo is helpful really depends on the audience, the nature of the presentation, and what points you are trying to get across. It's just one of a number of rhetorical devices.

For example in sales presentations to C-level managers it's generally better to avoid a demo and just assert the product works and sell the benefit to the business. When selling to technical folks demos are often a critical part of the pitch to show you are for real. Videos make it look as if you either don't know the technology or are afraid to show the product in action.

This is all part of basic rhetoric. If in doubt, just ask: what would Cicero do?
Oh nm, that's my Hacker News Enhancement Suite extension doing that.
He basically describes Star Raiders (Atari, 1979). https://en.wikipedia.org/wiki/Star_Raiders
Or the classic

1. Want to stop procrastinating and get stuff done

2. Spend hours reading "how to get stuff done" blog posts
There's a bunch of people who added a to-do to reply to this saying "Me too!" whom you'll never see.
That is open to interpretation. I adore Contact and i got nothing even close to religious out of it.
What I like to do is cover the entire total, and tell everyone to pay what they think they ought to. Maybe this varies a lot based on who you go out with, but this generally winds up with me paying less than my fair share (people round up in order to avoid being seen as stingy/nitpicky/shirking).
Experimental drug targeting Alzheimer's disease shows anti-aging effects
Fixed 1 second of braking time won't save you if the front car hits an immobile object.
The correct formula would be (1 + .046 mph) seconds [0], where mph is speed in miles per hour. It evaluates to 3.76s at 60mph and at 4.9s 85.
Note that 1 second of reaction time is not exactly generous: http://www.webpages.uidaho.edu/niatt_labmanual/chapters/geom... - cites times 'less than 2.5 seconds' to actual brake application.

[0] 1mph/(9.8m/s2) in seconds, according to Google, assuming friction coefficient of 1
Maybe it's harder to rationalize letting a nuke get into the wrong hands. Stuff like this is usually rationalized with something like, "Why should I do the right thing? It doesn't help me any, and nobody gets hurt, or at least the people who get hurt are far away." But even an idiot might pause and think about the possibility that their life might be negatively affected if they end up starting a global thermonuclear war.
Haha who would 'like' that?