skysight-inc/HackerNews huggingface dataset:
My favorite part of this is the mission patch they came up with for the team that had to stay at JSC: http://imgur.com/a/9YiQZ
> Indian governments have been most undeserving of our taxes simply because they've misspent it and/or misdirected it to achieve their own means

Can be said of 99% governments in the world.
deleted after a day
Why I hate your classic HTML app:

- Every click is a full page load, and you still didn't manage to get caching right, so it takes 2 seconds to load.

- When I have multiple tabs open, your badges and notifications fall out of date, because you never poll for updates.

- If I mis-enter information into a form, your error handling forgets all my information and I have to re-enter it.

- You forgot to update the styles on that rarely-used page, and now it's got half the new CSS and half the old CSS and the point is the header runs halfway down the goddamn content in Times New Roman.

I get it, there are problems with SPAs. But this perfect land of one-page-per-link has real usability problems if it's not implemented properly, and there's a lot of maintenance overhead associated with a sprawling mass of transcluded templates. If we're going to criticize an architecture because it's easy to poorly implement, I don't think "ROCA" or whatever we're calling it has any meaningful benefits over SPAs in the general case.
>Moreover, is there any sensible way at all to encrypt secrets without baking the secret key into your image? I can’t think of any.

Using PGP / GPG sounds like what you need
> Despite widespread speculation, the possibility of the signals coming from an advanced alien civilization has been largely ruled out.

In other words, none of the scientists want to sound like quacks. How could this possibly be "ruled out"? Oh right you put "largely" in front of it.
Meh. I was a Fedex Ground truck loader for 2 summers. When the box of Crickets en route to a petstore has a tear in the container and crickets are wandering all over the bed of the truck and boxes -- it's gross.
In person is the solution in this case, I think. I got on GameStop's text list and it went off while I was in the car. My SO and I immediately stopped at the first GameStop we could find and pre-ordered 2. Other people came in and they were all (as far as I could tell) Nintendo fans and not scalpers.

We plan to keep 1 and use the other one as a contest prize that we'll run on Facebook once we're able to pick them up in a few weeks. We've already pre-paid and have our receipts (or "golden tickets" as the GameStop cashier called them!) The receipts have our names on them so we are the only ones allowed to pick them up.

I hope stores do more of that in the future.
I guess this is cool, but not really that novel a result (and yeah, it's an ATel, not a paper yet, although that's just a matter of time). We've seen similar burst storms from this FRB source before, which is what allowed us to localize it in the first place. And I'm disappointed that they used the Hubble Deep Field - we have very nice deep images [1] of this field already.

But yes, the Breakthrough digital hardware is really pretty neat!

[1] https://www.nytimes.com/2017/01/04/science/fast-radio-burst-...
Yet another tool which uses machine learning to ease software engineering.
A very appealing approach !

Yesterday, there was that post [https://news.ycombinator.com/item?id=15125621]
about a tool which explores a target system to improve code with error and vulnerability checks.

Now, this tool, which uses a database of ill-typed programs with their fix,
to improve the error messages returned by a compiler on typing errors.
"ISS, we have a problem."
You are technically incorrect (The best kind of incorrect.)

Imperative is to Functional as Alchemy is to Chemistry.

Are chemists smarter than alchemists?
His statement does not sound like a criticism of the police. It sounds like a criticism of her opinion of the police.
During the floods these dogs were Chained to Death and Nobody even considered
Honest advice for JavaScript developers
Henry Kissinger on Board of Luxembourg Forum on Preventing Nuclear Catastrophe
Most welcome. Looks so much better. And it was whalesalad to report it first :) Have a great day!
Yes this is how I interpreted it but I'm sure the other people here probably know much more which leads me to believe that must not be the case.
Can someone link to popular sites that do things he's criticizing?
Good thing our society doesn't optimize for maximum absolute wealth growth in a vacuum, else we'd have 1 person with all of the country's wealth.

> If we equalise wealth, however, such that both have $4,899.13, then in 50 years Jane will have $34,816.57 and Jo will have $13,186.44, for a total wealth pool of $48,003.01

Have you considered second order effects here? What if additional wealth allows "Jo" to increase their per annum return because they invest it in a business or education?

> In this sense there is hence a direct tradeoff between economic growth and wealth transfers from richer to poorer in the long term (all other things being equal).

I have a BA in Economics as well, and ceteris paribus models stop being useful past the 2nd year of study. I don't think they're ever useful except to illustrate the most basic concepts to freshmen and laymen. When you apply such models to the real world, you end up with a situation I described in the 1st paragraph.

In this case, the condition assumes that the rate of wealth creation is fixed and unalterable on a scale of 50 years. It also falsely assumes (just world fallacy) that wealth is already allocated in such a way as to belong to people with high (unalterable) wealth creation potential.
Flink's SQL implementation actually follows ANSI SQL - which I think is very important.

There is a way of interpreting streams and tables to make ANSI SQL meaningful in the presence of streams, which we follow [1].

The big advantage is (besides not having to learn another syntax and retaining compatibility with SQL tools and dashboards) that this seamlessly handles the batch (bounded/static input) and streaming (unbounded/continuous) use cases with literally the same SQL statement.

[1] http://flink.apache.org/news/2017/04/04/dynamic-tables.html
Does he even know fractions yet? It sounds like you're setting him up to hate programming.
Some of this hits home for me. I work on the WAY DEEP backend of one of these 'modern single page apps', so dont really care about the REST apis or UI/UX. I will say our actual website is a nightmare to use and I attribute a lot of it to (A) mgmt demanding bad UI/UX on short timeframes(B) front end folks having the power to write butt loads of JS code to achieve said goals with no thought to system wide architecture / integration. We have so much shit happening each time you click to a different part of webapp, we seem to have hit the messy phase of a codebase where you cant change one part of the site without breaking something else in a totally different section of the codebase.

to be fair though, as with everything there are pros and cons. Once i learned to deal with some of complexities and crazy UI/UX, using our web app is like driving a spaceship and it does work pretty fast considering all the data getting lifted, html getting rendered etc.
Yeah, you're right. After unblocking and watching the video that seems pretty clear. Still, hardly racist.
The problem is ticketmaster, and this is the ticketmaster verified fan program. They are to concerts what time warner is to the internet. They're only trying to solve the problems on their end, without endangering their monopoly. This solution just gives gains to the artists, probably to keep them from straying.
So kind of like hosting files you didn't intend to.
What an interesting story and credits those who may be missing from the general narrative of codebreakers in WW2.

The impact of breaking NAZI codes and learning about the murder of your people -- without being able to act -- is a terrifying position for any human to be in.
Credit Card OCR with OpenCV and Python
So apparently one of the reasons it has been "largely ruled out" is the amount of power that would be required to generate the signal. Because we know that our knowledge of physics is not definitive, it is entirely possible that there are ways of exploiting physics that we aren't aware of that could produce such amounts of power. We also know that our knowledge of whether there's alien life, and, if there is, what their capabilities might be like, is very limited. We know that we know very little about what they might be able to do and why they might do it. Thus, it would be making a massive assumption to think that, just because we don't know how or why such a signal could be artificially generated, that therefore we can largely rule it out.

Thus, I believe the appropriate position is being agnostic. We don't know. If we learnt more then that could change, in either direction.

This argument is based on positive knowledge about the limits of what we currently know, not the nihilistic argument you reference.

.

A relatively-recent example that comes to mind. These days we know of many many planets outside of our solar system, but it wasn't long ago that we had not found any. I remember hearing a lot of people say that the fact that there was no evidence of such planets meant that there odds were very low. They were making the same mistake: of not factoring in the known limitations of the knowledge we had (i.e. we knew that the tools we had weren't good enough for spotting planets below a certain size/distance away from us), and assuming that the knowledge we had was representative of how things actually were.
I'd argue along the same lines as a dead comment here:

the student's mistake (well, beyond not contacting them to report the issue) was using the FCC's official letterhead to create an embarrassing document and uploading it to their official website and posting it on social media.

That's pretty much a "fuck you" and not a great way to start a conversation.
Boost burns happen significantly more frequently than every few years. At 400km and a drag profile as large as the ISS, decay would take around a year or less, depending on attitude. A little bit more reading:

https://space.stackexchange.com/questions/9087/how-often-doe...
The downside of Ember (at least the last time I used it, several years ago) is you must do things "the Ember way", which isn't inherently bad, but there's a lot of implicit functionality that "just works" until it doesn't, and can make debugging a painful experience.
but that's the point: an application isn't a webpage. An app doesn't have a concept of back and forward, it has undo & redo. It doesn't need refreshing because it's syncing with the server by websocket. It doesn't have location it has state.
One big downside of SPAs the author didn't mention is the chain reaction effect I wrote about last year[1], where if you start to implement one browser-native feature in JS, it breaks other browser-native features, and it begins a chain reaction where you basically implement the whole site in JavaScript, and the result ends up being noticeably worse than if you had just stuck with native browser features from the beginning. It's not necessarily specific to SPAs, but it's definitely a very common problem I see with them.

[1]: https://sdegutis.com/blog/2016-03-21-why-i-dont-use-clojures...
Most mathematics isn't constructive (https://en.m.wikipedia.org/wiki/Constructivism_(mathematics)) so it doesn't really come up I think. E.g. you know how matrices need to have a certain shape to be multiplied? People don't really talk about what happens if they don't.

Physics on the other hand very much has types, the unit to type correspondence is dopetastic.
It was submitted. Other HackerNews users voted enough for it to be on the front page.
Shouldn't the falcon 9 be included?
> the bureaucracy is now larger and more powerful than ever under this government

Umm... no. The red tape is now minimal at the Central government level. Digital, removal of archaic laws, clearly defined parameters for bids, etc.
> Maybe your single page app is different, but the ones that I know break most of my browser’s features, such as the back and forward buttons, page refresh, bookmarking, sending a link, or opening a link in a new window or tab.

That reminds me: if anyone out there has any advice how to make AppCache play nice with JavaScript-based routing solutions (say, react-router), please let me know.
Channels overlap, but not in the way you think. You need to monitor the correct channel to see the traffic on that channel. The overlap between channels is interference and kills Wi-Fi performance compared to sharing channels. 1, 6 and 11 in practice the only channels that should be used, not 13, and so there is where you will find almost every AP.

The others has been manually configured by someone that has no business touching networks, which may in itself make them interesting from a security point of view.
Blockchain: The right side of crazy
What I picked up was a sarcastic comment that would undoubtedly get your ass fired in any other position with a PR aspect. Is the officer overtly racist in his work? Maybe, maybe not, but we don't accept much short of perfect when it comes to policing. There's never a time for snark as a cop, especially when you add hot-button issues to the picture.
Misconceptions about Initial Coin Offering (ICO) Law
How about a gyrocopter or is that not a short takeoff?
That still seems like it requires a level of trust that the original bank is holding onto the funds and has the cash liquidity to cover the total number of coins issued.
Space is so disappointing because everything humans do there is super complicated and fragile.
Title needs a pdf tag.
Seems like the difference of assassination by hit-and-run/"robbery gone wrong" vs polonium. One screams "state actor", the other is almost entirely deniable..
It sounds like you may be looking for the cluster autoscaler: https://github.com/kubernetes/autoscaler/tree/master/cluster....

When used with Kops, it should give you what you're looking for (with the baked in kops AMI)
What you hate is just bad design and programming. All these things can be handled in an SPA.
I'm really grateful that those review papers are being made, but they're not a very accessible source for non-experts. How do I find them? How do I know if a given review paper is exhaustive or not? If it's still relevant or has been superseded by another one? What I'm suggesting is to generalize the work being done to create review papers into a resource that is easy to find, authoritative and continuously updated.
Indian navigation satellite stranded on rocket after launch
Come on, this is clickbait as it can be with the title and the first line of the article, that's what I hate.
"If I mis-enter information into a form, your error handling forgets all my information and I have to re-enter it."

This. I have a very short list of architectural must-haves that I use when evaluating junior dev's code at the start of a project, and not having robust error handling that preserves submitted form information is right up near the top.

It's an annoying design mistake with two input elements, unworkable with five, and just plain cruel beyond that.
Agreed. It's institutionalized crony capitalism.
Noting that the plans they made were all as a result of having enough advanced warning of the storm to 'bring in big camping backups and setup cots (assume those were there already?'. I would think that the planning should or would include a case where there is no warning at all. In other words personnel would be required to keep items onsite like hospitals do with crash carts for emergencies maybe storage places or bomb shelter esq. After all if one thing this storm taught (the chemical plant with the generators on the ground) is that you can't really predict the unknown unknowns. It doesn't seem, relative to the cost of space missions, a big deal for each employee to keep onsite (at JSC cost) items that would be needed (including medicine; refreshed as needed) in the event of no ability to plan ahead.

My wife works as a doctor at a hospital. I am always amazed at how they make no plans at all in bad weather to have a system in place to make sure she gets to work. It was actually my idea to tell her to buy an SUV so she wouldn't have problems when it snowed. It's literally left to all employees. They don't even have a way to reach her in the case of a mass county wide emergency. For example we don't have a landline and they don't have my cell phone and so on. It's all very ad hoc.
In addition to linking tickets to the buyer by name, I believe the ticket selling platform should facilitate easily reselling tickets in the case where the buyer cannot use them. If I am unable to attend a concert, I should be able to indicate this to the platform. The platform should then attempt to sell the ticket at the most appropriate price. If the ticket could be sold at full price ahead of the event, I should end up paying nothing except possible transaction costs. If the ticket sells at a lower price, I should only end up paying the difference.

Easy and safe reselling of tickets should be possible, at ideally no cost to the person reselling the ticket. I think this would be a nice feature of a consumer friendly platform, and a necessary mechanism in order to make the "link ticket to name" approach be fair.
Most of your criticisms are solved with basic javascript, not necessarily single page applications.

> You forgot to update the styles on that rarely-used page

That's solved with proper css, not SPA.
How Programmers and Developers Can Help Houston Right Now
I'm going to start CluckBox, a service to have a live chicken delivered to your doorstep every month.
Well apparently it's not just my phone using it to track my location. This article convinced me to disable the always on Wi-Fi scanning.

> However, Wi-Fi scans are not only used by the device to derive its location, analytics companies now leverage the Wi-Fi probe requests to estimate the number of visitors in stores and malls and to record customer mobility. Indeed, by counting the number of unique MAC addresses broadcast in probe requests, retailers can derive the number of smartphone carriers in their store. Location tracking of these customers is performed by following these MAC addresses as they are heard by antennas located in different spots.
Define handling transactions, they have Node services which are touching cardholder data and are subject to PCI DSS compliance. The web layer is Node.
Even Angular solves most of these problems.
Eclipse as seen from the Moon
Integrating Spring Data JPA, PostgreSQL, and Liquibase
Except the the science doesn't appear to support that. Read the thread.
I agree that it's not overtly racist, but it is a very dark joke.
The thing that makes it particularly offensive is the fact that it's a dark joke about a real situation and real people from a public servant who has power over in said situation.
Yes, that's probably the closest thing there is. I wish we had this for all fields of science
>None of the things described here are inherent to single page apps.

Does it matter though, if they are still all prevalent on single page apps?
FTA: "and other things to and from stores (eg, getting your broken iPhone to a Postmates-using repair shop)."

Yeah, about that. We run repair shops, and were approached by Favor (Postmates competitor) about doing this. We love Favor; they are local to us in Austin and we'd like to do more business with them.

The problem was insurance. Our insurance refused to cover it as the phone wouldn't be in our possession. And (at least at the time) Favor's insurance also was not covering if a phone was lost or stolen during a "run."

When it's a small food order (most of the food orders they run are around $20-$30, or even less), it's not the end of the world if something gets lost or stolen. It's a lot bigger deal if it's a $969 iPhone 7+. Even with a broken screen and iCloud locked, they're still (unfortunately) worth significant money on the black market.

As far as I know, no delivery company has overcome this hurdle.
I would say that the opportunity to freely share values without needing to defensively copy is of greater benefit, especially with an increasingly multicore future. Updating in-place also requires memory barriers, which don't scale.
Any idea how to do this in 7?
I would go even further and say we need a free software mobile OS.
Agree. It takes a lot to walk away from something and say you were wrong.

But, sadly, part of the saga of nodejs could have been avoided by people looking at the history of computing. If you look at Go's concurrency model it was entirely mapped out in the 1970s in CSP. There wasn't really any need for go the 'single thread, non-blocking' route that nodejs took and evangelize it as nirvana. There was a ton of distributed systems work done in the 1970s. Just look at Lamport's clocks paper.

I'm not criticizing Dahl directly here, more a sense that people ignore history in a field that has only had history for far less than a century.
Edit: Apache Spark. See below.

Some do. But more importantly, if your runtime doesn't, then it's still more obvious how to add parallelism, and more self-contained when you do.

Let's say you were using asynchronous IO in a functional style; not even full-on monads, just async/await like in C#. Since you have explicit data dependencies, you can easily see where the `await` is unnecessary, or coalesce multiple calls into await Task.WhenAll(...).

var slow = await conn.Query(@"slow query");
var fast = await conn.Query(@"select top 1 * from some_table");
var emailresult = await SendEmail(fast);
return (slow, emailresult);

Instead of awaiting `slow` before continuing with `fast`, it's fairly obvious that you could start the task and not await it until the others have already kicked off:

var slowTask = conn.Query(@"slow query");
var fast = await conn.Query(@"select top 1 * from some_table");
var emailresult = await SendEmail(fast);
return (await slowTask, emailresult);

That way, your email sends almost immediately, since line 1 never relinquishes control flow and just continues straight on. Then your `await slowTask` only blocks the return, instead of the entire function. This is pretty big if you're lining up a hundred slow IO tasks.

Note: while async IO gives you the actual parallelism, it's only because of the explicit dependencies that we are able to see which parts can be done simultaneously. I've been coding like this for so long I can barely imagine how to do it imperatively, but if you exposed an interface like `async Task GetSlowQueryResults()` and `async Task SendEmail()` using internal fields for intermediate results, it's utterly opaque and you can't tell which has to complete first.

Edit to respond better to your actual question:

There's a kinda big problem with auto-parallelizing, which is that in FP, outside of IO, everything is parallelizable. Spinning up threads or even shuffling data within a thread pool is pretty costly, so most attempts at micro-parallelizing everything haven't gone anywhere. You can annotate things in Haskell to run in parallel, or simply choose a parallel map or parallel reduce instead of a sequential one.

On the other hand, when spinning up threads/processes/jobs is relatively inexpensive compared with the cost of actually computing things, the idea is very successful. Take Apache Spark. You write a program in functional Scala or Python, and the scheduler will automatically distribute work over your cluster if it's big enough to warrant it. The scheduler also makes note of where intermediate results are, and will happily cache, reuse, shuffle or partition them around to continue on with the work. The engine essentially evaluates a DAG, with some optimizations for transport/persistence costs.
From my experience observing its usage, it can refer to the willful beta-[noun] of any topic. They would call a person a 'cuck' for not taking a lead or position of power, just as easily as they call a country 'cucked' for not being nationalist enough. What remains is promotion of aggressive alpha-everything tendencies.