skysight-inc/HackerNews huggingface dataset:
My only suggestion is to make sure the youtube video plays in HD by default. Excellent work!
Honestly, I'm still on the fence about what acceptable code coverage is. There's people who claim 100% is ideal, others (like DHH) think aiming for 100% is detrimental. My company is at 89% right now, which I think is commendable for a codebase of our size (100k+ lines), but how do we really know? Acceptance tests can cover broadly without needing to test every line of code, but if that gets the job done, what are you really achieving by improving that number from 89% to 100%?
One feature that would make this a killer app in my mind is the ability to import a photo of a whiteboard and have the virtual whiteboard reconstruct what was on the whiteboard in the future.

We often take a picture of the whiteboard at the end of the discussion -- being able to continue to edit that whiteboard at some point in the future would be very handy.
Building your solution to work without server code is amazing. Also, nice UI.
Fancy seeing you in a webpack thread :P
Waved, one-tap voice messenger
www.waved.io
As someone who doesn't know Bob McMillan personally (and so don't have that context when reading his articles), the title attached to an article is an important cue that should be considered.

Yes, I understand he probably didn't have final approval over the title. However, Wired as an organization is responsible for the presentation and content of the article; and the impression I came away with was one of Wired, not of Bob McMillan.
missing typing and SSL.
Re: "Fight the FOMO"

This app is seems to be feeding the fear of missing out, rather than fighting it.
Contrast this with Anne Neuberger's Long Now talk: http://longnow.org/seminars/02014/aug/06/inside-nsa/

One of these two talks was written by a liar.
> it does not allow to sequentially execute tasks: everything is done in parallel

There's a package[1] for Gulp which does exactly that.

[1]: https://www.npmjs.org/package/run-sequence
I've been developing on the sencha products for years. Primarily an ExtJS single page app developed by a large team since 2008 that's now well on its way to 200.000 lines of code. I also wrote a 5 kloc app in sencha touch.

The thing about sencha that makes them different is that they abstract away the html and css parts to a large degree, by constructing the dom programmatically behind an abstracted component api (e.g., a panel component has a title bar, several toolbars, and multiple child components laid out using border, anchor, column or any of the other layout systems). The upside is that the ui controls are richer than standard html controls and require fewer lines to do advanced things (like having a field with server-backed autocomplete). The downside is that html+css skills don't translate well, if at all. Instead of thinking in terms of dom updates, html templates and style rules, you think in terms of the component lifecycle, the container layout system and themes. The skillset required is extensive and specific, and the code is so deeply tied to extjs that no part of it can be reused outside of it.

Some people like it, some people don't. You can't fight the framework. You have to adopt sencha's architecture and component system completely, or you will have a painful time. We have had to invest extensively in training because the framework is so different from other js frameworks that new developers have a hard time learning it.

As for the whole she-bang, sencha cmd, sencha architect and so on. I tried those tools several times, but they always lacked maturity. The last time i looked at it is 2 years ago though, so they may have improved. Meanwhile we just use the frameworks.

Update: I realized I didn't actually say whether I would recommend it or not. I would not choose ExtJS again, but I would choose sencha touch again, despite the API's being so similar. I feel like the use-case of writing a mobile cross-platform app fits in well with the sencha architecture and api, better than other js frameworks. By contrast ExtJS isn't bad, but it's no better than the free alternatives like ember or angular for building traditional web apps, so I don't see the point in spending the money on a license if you're starting from scratch.
So you thought that Russians and Ukrainians could burn in hell and the West would just keep supporting its puppet Ukrainian government and no western people would feel it? Wrong - you reap what you sow.
You actually can get together with your friends and plan an overthrow of the government. That's exactly what the Free State Project is. It just so happens that their plot does not include violence or other criminal behaviors.

And you can plan a murder. The conversation itself is not a crime. But it is very damning evidence if the prospective victim that was discussed actually turns up dead, showing that the crime was, in fact, premeditated murder and not a less severely punished type of homicide, and that accomplices were involved. The speech is not the crime. It is evidence of malicious intent if a crime subsequently occurs. It may also be useful intelligence that could allow someone to interfere with a crime in progress.

If you overhear the murder conversation, you might be able to prevent a murder. But those guys could have been talking about their clan strategy for a MMORPG raid, and you simply misunderstood the intent. You don't know for certain until someone acts.

Censorship cannot stop crimes. It can only conceal evidence.
This is very nice for your first Android app. Have you done mobile dev before? (on other platforms)
> Personally, I think it's OK to hold professional writers accountable for what their words convey.

Now there's a classic constitutional issue. The law is pretty clear on this -- if you want to offer a quack medical treatment and you advertise it, you might be arrested for misleading the public and/or practicing medicine without a license. But if you put the same words in a book or magazine article that's not an advertisement, you're safe.

If a writer plagiarizes, he might be sanctioned by his employer or gain a bad public reputation. If a writer libels someone, he could be sued in civil court. But writing is safe in ways that most things aren't, based on the idea that we should allow free expression of ideas.

A writer can say virtually anything in a book or a publication that's not an advertisement, not part of commerce, and not expected to be a reflection of fact.
Even as a .Net dev I'm loving gulp.js, I've got it worked into our builds through MSBuild. and it has made our front end a lot nicer to work with.
I practically live and die by the 5 Minute Rule, and as a counterpoint, I've always found Grunt intuitive, if verbose. In particular, I love that its files API is so flexible. I frequently find myself asking questions that look like "I wonder if I can do this X way", and things just work.

Saying Grunt is "very bad" is harsh and only serves to amplify hyperbole that causes much of the churn around JS tooling.

[edited for a grammar nitpick]
Absolutely.

On one hand, it is entirely to easy to look back or even laterally at the decisions people make and fault them for choices driven by circumstances that may not be obvious.

On the other hand, there are plenty of people whose justification for such decisions begins and ends with how well it fits in their own comfort zone and/or how it affects their headcount.

Both of these things are prevalent in Government.

It's a serious balancing act to navigate those forces in managing or reforming existing systems - far harder than building the same with a clean slate.

The materials to come out of the USDS so far have been right on point so I feel confident that this part will receive the same sort of attention, but I have noticed the seeming absence of attention to O&M thus far.
Nearables Are Here: Introducing Estimote Stickers
How do you fix this? If you are "grooving" then there is a high percentage chance that you aren't looking at the sound cloud page but rather doing something else somewhere else. Advertisers pay for your attention so how do you go around doing just that without being 'obtrusive'.
A zoom in/out with mouse scroll would be good to have.
Yes, it was a poor choice of terms. To be clear, eval isn't equivalent except within the narrow theoretical notion of turing completeness: it can do I/O, for instance file I/O. And it accepts high-level language code directly which is very important in a practical sense compared to, say, accepting nand instructions only.
I know it is, but the majority of the tasks are configured in one big hash.
That doesn't even need to be future tense. The "September issue" often means the "display until September" issue for periodicals.
The point is that developers should have the freedom to pick from all existing tools, not the limited selection which have passed a lengthy and expensive procurement process. It's okay to pick Java and Windows, but only if you actually got to choose them, and they weren't the only options on the table.
> Informally, dynamically types languages are chosen when the programmer prefers to get something running before getting something running correctly.

I don't think that's at all true. I think that a major motive for choosing dynamic programming languages is that programmers want to get things running correctly and spend more time on the logic and less on making ritual invocations to the type system that are redundant with other elements of the code. (Haskell and other similar languages with very strong type inference are making this a less compelling reason to choose a dynamic language, but I think it remains an important one for many real decisions, as Haskell hasn't yet acheived the ecosystem and mind-share where its always likely to be considered as an alternative, and not rejected for reasons other than its type system.)

I think people who choose static languages do so because of concerns for correctness, but I think it is a mistake to reverse that to conclude that those who choose dynamic languages do so because they aren't concerned with correctness; many do so because the hoops you need to jump through in mainstream static languages are perceived as being a too-expensive way to get the (often very limited, given the lack of expressiveness in the type systems in many popular static languages) help in correctness that the static nature of the language provides.
False positives happen all the time with these sorts of tools. We got flagged for phishing by AVG because we built a promotional website for a bank. Their reps were pretty nasty until someone from the bank joined in to vouch for us.
> When a user opens a URL with the tel scheme in a native app, iOS does not display an alert and initiates dialing without further prompting the user.

What is the justification for this behavior? Why should the web browser open a prompt but not other apps?
APIs for Democratic State Parties and Campaigns
There are ways, like others have said. There is also a callback system you can use to make things sequential, but last time I looked it wasn't well documented
I'm not advocating concentrated iodine. A few drops of Lugol's mixed in a glass of water isn't going to damage anything - lots of people take that exact amount on a regular basis. We could argue about long term effects of that, but I'm talking about doing it for a week or two to help with something that is killing half the people it infects.

Where is the guy with iodine user id when you need them?
The whole point of their platform is that it's not controlled by any central authority and is resistant to censorship, control, breaches of privacy, etc. The fact that even some of the most horrific and undesirable content, that which people most adamantly wish to censor, CAN'T be censored, is a strong proof that their network works.

All they need to do to is say, "Censoring this is not possible", as they seem to be doing, and that promotes their software. They don't need to talk about, approve of, or even be aware of the horrific things that ISIS does. It's enough to know that people really, really don't like what they're posting.

On the other hand, by actively attempting to censor the content, as Diaspora also seems to be doing, they're also sending the message that they don't actually truly believe in openness as a value, deep down, even though they designed their software to provide it. That actually hurts them a bit in the long run, I think.
That way it'll show up in https://news.ycombinator.com/saved?id=Jayd2014
I'm surprised nothing about functional tests were explicitly mentioned in the article. There were some hints about "engineering the heck out of your migration scripts" (paraphrased) which could be taken as setting up functional tests.

If there is a good tests infrastructure re-writes can be done with a heck of a lot of confidence. Plus there is the benefit of breaking the re-write project up along test lines which helps in not creating the pressure for a, "huge one-time switchover".
> I wrote the Lanczos3 scaler that Picasa uses (about 14 years ago!),

What are you doing now? Picasa hasn't changed much since Google bought it and ignored it (except for adding G+ integration)
Also the Matrix. A sequel to either of these movies would be phenomenal.
What the hell?

When I say "hold accountable" here, I'm just talking about criticizing the writers for the implications of what they say, even if they didn't necessarily mean to imply that.

It's not a constitutional issue. It's not a legal issue. It's not an issue of anything you mentioned here.
Walking The Beat – Mining Seattle's Police Report Data
Should we not recruit people to behead other people? No, we should not. We're still beheading people in that narrative.
> Who cares? Do you have faith in your product, or do you just want to brag about who invested in you?

This is terribly myopic. When you're selling software to other businesses, knowing that you aren't going to disappear in 6 months is a huge deal.

> What are you doing for your customers?

I know the founders of Hightower personally and trust me this is one of the very few companies out there that is extremely customer focused in a terribly backwards industry.
You're claiming that forcing people to wear expensive (to buy and maintain) clothing that is hideously uncomfortable in any climate (other than its place of origin in the British Isles), and that is designed to enforce conformity with the most reactionary norms of the prevailing culture promotes "diversity"?

Okay.
Humans Did Not Wipe Out the Neanderthals, New Research Suggests
I haven't read their _sequels_, but I have read their _prequels_ before reading the original dune and I found them decent. Not exceptional, but not bad at all. Slightly different from the original, though, which might be why they are off-putting to many people who have read Dune first.

(I am reading them in the order suggested here: http://www.amazon.com/Dune-Saga-Chronological-Order/lm/1COAD...)
Because the apps can initiate a call by just pointing a webview at tel:0000.
Another reason is hybrid apps, imagine a contact hybrid app running in something like PhoneGap. You want to click a button and call right away without the phone asking you to confirm your action.

I'm not saying that Apple's design is good, but it is documented.
Looking at all the feature requests here I can't help but think that you guys are reinventing TeamSpeak. The only difference I see is that with TeamSpeak you first must install a client whereas this runs in a browser.
Great to see CodeFights being launched! I enjoyed the graphics and dynamics of MathFights.com as well, well done, Tigran and the team.
You're right.

Since the title is kind of baity anyway with its Upworthy 'this', we changed it (from "This could explain why older adults can't stay sleep") to the article's first sentence, truncated to fit.
Key quote: The new findings suggest that Neanderthals disappeared from Europe between about 41,000 and 39,000 years ago.

"I think that, for the first time, we have a reliable extinction date for Neanderthals," said study author Tom Higham, a radiocarbon scientist at the University of Oxford in England. "This has eluded us for decades."
The Internet has made copying and the transport of bits cost nothing.

This efficiency has also now moved to other industries, like manufacturing, because communication has become so easy.

I recall many people here saying that the record industries need to deal with it or die. Now that this same thing has started to effect your bottom line (or the bottom line of people you might care about), we need government sanctions to make up for the lost revenue.

Instead, I say we just deal with what has happened, like any other business model destroyed by technology (horse and buggy?!). Manufacturing jobs are gone. It's time to learn a new skill and figure out what will make you a living.

A basic income is not sustainable. It will only force legitimate businesses out of the US (which means less jobs) because of the higher taxes. These taxes will also only increase over time, because more and more people will start relying on it as a way to live.
Well, I should clarify, this is the first app I've released on the Play store. I've made a few small apps before, but they were just class projects. (I'm also an Android intern at Lockitron)
I'm fond of http://www.noisli.com/ myself.
>> Ebola virus disease is not like c. difficile. It attacks endothelial cells, liver cells, phagocytes... it's as systemic as they come.

As are the benefits of iodine. But to be clear, you don't think it's worth even trying right?
Show HN: Try Riding the Boosted Board for Free in SF
I find it odd that people use their pinky to type parens. When my fingers are on the home row, '(' is above my middle finger, and ')' is above my ring finger. Typing them with my pinky would require me to contort my hand.
Top links for young founders
I would think a more likely to be exploited use case would be to find the telephone number of celebs. Send the celebrity some specially crafted message on FB or twitter with a good mix of social engineering and you should be good to go (provided they are on their phone when they view your message)
I guess my point is you can buy a 1br condo in Atlanda w/ 55k, you can't buy anything w/ 100k in Manhattan.
Accidental Feature Loss: You don't know what you got till it's gone
I just did a bunch of research on state-of-the-art JS architectures for a new project I'm working on, and neither of my first two choices are on this list. (Granted, they aren't restricted to MVC either.)

Polymer is interesting because it's the first one that's geared around the idea that the browser is an app rendering engine, not a document reader. Being able to declare your own HTML elements and bind them together could very well be the future of web development. Unfortunately, it's still a bit immature to use commercially.

Hence, I chose React. It's idempotent, which is a fancy way of saying the markup it outputs is a strict function of the inputs it's given - no side effects, no externally-mutable state. This means you can live-edit your markup in your favorite editor without having to reload the browser on every save (using a tool called the Webpack Dev Server with the react-hot package). Using Webpack also means your dependencies are explicitly declared with `require` statements. It has all the benefits of Angular's Dependency Injector without all the boilerplate.

Finally, and perhaps most importantly, it has 0 dependency on the DOM. This means you can render your initial request on the server, and pass markup down to the client that's indistinguishable from what you'd traditionally get from Flask/Django/Rails/PHP. There are no assumptions that your client speaks JavaScript, so it's more friendly to non-browser clients like searchbots, which is in turn safer for SEO. It also means your view is already rendered when it reaches the client, which is important in a world where many clients are phones with underpowered JS capabilities. You get both the benefits of a single-page-app (slow client rendering is still faster than slower network requests, and network requests are smaller if you don't have to also send down the template every time) and those of a server-side one (SEO is maintained, and the client can display your page without waiting to execute the JS first).

I should disclaim that I haven't seriously considered Ember since it's been rebranded from SproutCore; however, I have worked on a few Angular apps; and even forgoing the above benefits, React is just easier to work with.
Absolutely an exploitation technique. Or you can facetime them instantly and catch a photo of them in pijamas!
If this bothers you, you are doing it wrong.

If your designer is stuck in iOS pixel-perfect land, use this number to convince them they need to learn to use Asset Studio and live the RelativeLayout way.
I'm curious: Wouldn't 2 buttons be better than a swipe interface?

Perhaps Tinder needs swipe because there's more downside of an error; but I'd think a Hot and a Not button would be faster and still reliable enough for general product liking.
The comments are already pretty deep, but I still want to mention that the right framework is all dependent on what your needs are and what your company is willing to support. Which is why I get tired of article comparisons like this, and trust me, I wrote an article on choosing AngularJS[1] but I still wouldn't push it on anyone.

Each framework has it's advantages, and it really depends on where you and your company align with those advantages. When I started my journey I realized I needed better testing for AJAX events in jQuery, which lead me to Backbone. But in 2012 Backbone seemed like an outdated solution to an outdated app landscape. Now it seems even more outdated, but learning it certainly helped elevate my JS game to choose between Angular and Ember (though now I'd through React/Flux and/or Meteor into the mix).

From there it's really about what you need, as I've said before. For me, a lightweight, performance-driven solution with a great testing framework was necessary. Angular is lighter weight than Ember, but both have great testing frameworks, so Angular won. If I wanted better documentation, an easier learning curve, or better community support (it happens that Rails people seem to like Ember because Yehuda works on it) I would have chosen Ember, but that wasn't important to me or my company. Again, that was 2012-2013, today I'm still using Angular but entertaining the idea of having React replace Angular directives, which I still don't like writing. Again, it's all about what works for you and your organization, and that really is about introspection, not about what some article can do to act as your oracle.

[1] http://code.tutsplus.com/tutorials/3-reasons-to-choose-angul...
> As for diatonic scales that start on an accidental, as far as I know you can use either the flat or the sharp notation. They are enharmonic equivalents. I know there are often traditional preferences, simply to choose the spelling that leaves fewer accidentals in the key signature. For instance, I think that Db major is more common than the equivalent C# major because the former has 5 flats while the latter has 7 sharps.

Yup, that's true, though the choice of enharmonic keys will depend on context: e.g. the V7/V in a sharp key will be spelled in another sharp key even if more awkward, with double-sharps etc. Also, to get pedantic there are no "accidentals in the key signature" by definition.
Avoid success at all cost. :)