skysight-inc/HackerNews huggingface dataset:
If you could take 10 4 year olds and start training them in music that way, you won't get 10 Mozarts. I doubt you'll get one. (I'll concede they may all be very good for 8 year olds though) Different people learn different ways.

I guess my point is, for a given training program, you're going to have a wide distribution of effectiveness of graduates.
> Between enterprise backend web services.

For me at least I would not want this sort of job, and I doubt I would be considered qualified.

> Android

It's unclear to me if native apps won't be usurped by the webview route.

> and to a lesser extent desktop apps

This is almost clearly on the down trend.
We added "Show HN" to the title because it looks like a perfect candidate for that. If you don't want it there please let us know.
Well, the point is that just shrinking stuff that looks pretty good isn't professional typesetting. Attention to stroke size in small-caps fonts are exactly the difference between a professional system (or just a professional typesetter) and using MS Word. It's not out of the question to build a JS-based system to do this kind of thing, but it would be a great deal of work, with probably little payout. After all, Knuth and crew have been doing the work and the upkeep on TeX and LaTeX for what, twenty or thirty years now?
> Even if you don't use Google Apps it's also not possible to have own XMPP address that happens to look the same as an e-mail address that Google knows about (even if it's non-Google address and non-Google XMPP). When they see it they route GTalk users' messages straight to GMail chat, bypassing XMPP.

This stops happening if you disable Talk+Hangouts from the admin panel: https://admin.google.com/AdminHome?fral=1#AppDetails:service...
How to Be a Better Human in the World of Software
New iPad app “LiveFrame” – A digital photo frame app that keeps you connected
The passenger cabin extends around a space. That space is located outside of the passenger cabin, but inside the aircraft.
A brief scan suggests they are engulfing an unpressurized section of airplane volume since unpressurized sections don't weigh as much.
In Germany it's the same. Are there countries except the USA where this method is the normal one?
Why do you assume that back blows would not have been just as effective at removing the blockage? Obviously in your case it's great that the Heimlich worked, and natural that you appreciate it having been used. In some cases though, perhaps back blows are even more effective. And they are certainly easier to perform correctly.

Also, five back blows take less than five seconds to administer. Certainly it is beneficial to know the Heimlich as well, and be ready to administer it if the back blows fail, but I'm inclined to agree with the current medical opinion that they should be attempted first.
Our galaxy is only 100K lightyears across. A civilization that attained only 10% lightspeed could populate the entire galaxy in a million years.
My mindset is that of a scientist I guess. I don't trust people's own accounts, especially in such a heated debate. I want numbers, research and objectivity.

> However, sadly, often the motivation is "she's successful" or "people are listening to her".

Sources please!

The wikis you linked seems highly loaded and written with agenda. The writing is purely self-serving(?), without criticism of itself. I am sure whoever wrote that feels it is the right way, but I don't see much value in that myself.

The FLOSSPOLS survey linked seems very interesting and objective though, thank you!
look up the date of the executive order footnoted above...

or maybe that's too difficult?

you're too smart to argue from ignorance.
The "How to Learn Emacs" infographic that's linked a little ways down on that page includes a bit of attitude that drives me nuts:

NOTE: The Emacs tutorial has lots of weird terms: "Meta key", "frame", "buffer". This is because Emacs started a LONG time ago. Don't worry, you'll get the hang of it with practice.

I have no idea why we make people jump through the hoops of learning archaic terminology, rather than evolving the software to use the terms people actually use today.

The Meta key is called the "Meta key" because that's the label that was on the keyboards of the Lisp machines in the MIT AI lab when Emacs was first developed. It's been thirty-plus years since that key was found on anything close to a significant fraction of keyboards in use in the world. There's no evidence that it's ever going to make a roaring comeback, either.

In other words, the Meta key, as a key, is dead and gone. It is literally as dead as disco! And yet the name persists, even though the way people have interacted with the "Meta key" for decades has been to press a key labeled something other than "Meta."

So: why hang on to a dead word? It serves no practical purpose, and does active harm by confusing people new to the editor.

But no, rather than update our terminology so it bears some resemblance to the world we actually live in, we hang on to it and tell newcomers that to learn Emacs they're just going to have to get used to pretending they're working on a space-cadet keyboard, because that's The Way It Has Always Been Done. Sigh.
Some background: there is a regular expression module in the small stdlib OCaml ships with (the String module mentioned in the article). Unfortunately, it is terrible and full of global state. The ocaml-re package is interesting but really low-level. However, it has one interesting feature: it makes it possible to build regular expression in a composable, type-safe way. The humane-re package provides higher-level operations, though last time I checked didn't (yet) support substitution.
I imagine it'd be uncomfortable to be seated at an angle askew to the takeoff/landing vector.
Me too haha, insufficient coffee -.-
Darn, I thought this was going to be about audio consoles[1].

[1]: http://arrakis-systems.com
Javascript.

Growing use among web apps, growing use on server side. Applications are running more and more on the client. Most popular way to build an API is with Node.js, API's are only growing. MVC frameworks are only growing. Use of JSON is growing.

The answer to this question seems fairly obvious to me.
"The Emacs way" is very much "learn some elisp and write whatever you want".

I switched from Vim to Emacs and in the beginning there were some things I really missed. One that I remember was "*", which in Vim/my config highlights current word in whole buffer and let's you n/N between matches. In Emacs, doing the same with M-left C-s C-w felt just wrong.

Fixing this was a matter of 2-3 lines of very straightforward elisp. I since started relying more on Occur mode and IEdit mode for this, but the experience of lacking a feature and adding it absolutely painlessly remained with me.

Writing simple elisp and simple editing-related features is a joy under Emacs. It's much easier than in Vim, for a number of different reasons. This makes me think that "the Emacs way" is about scripting and programming it to do whatever you need it to do.
Read the friendly headline: it's a doughnut-shaped plane, meaning there's a hole ("outside the cabin") in the middle ("inside the aircraft").
> For niche professional documents, like research papers, I'm sure it's accepted and expected, but you're probably already using LaTeX for those anyway!

I think by LaTeX you mean Microsoft Word. For social sciences, at least.
I didn't think I would, but I love Inbox. I really want it for my work Google Apps account. Snoozing stuff is a killer feature. Wiping entire lists is a killer feature.

I get maybe 5 marketing emails a day, and a few actionable emails a week in my personal email. I get about 10 actionable emails a day in my work account, and about 200 emails that could just be wiped. I'd get so much more value out of Inbox for Apps.
It could very well be but I am very close to some of them and am confident that they are neither oblivious nor feeling like they have to hide anything. They are well respected in their respective communities.
No impropriety intended. Yes I work for what3words. Apologies for not disclaiming comments & replies.
The best all-around resource I have come across thus far is https://en.wikibooks.org/wiki/LaTeX
I love how the article starts off by telling us that the author "climbed to Everest base camp," as if that has any relevance whatsoever to the topic at hand.
Any aeronautical engineers around who could give us the TL;DR of just why it's a good idea to have a hole in the middle? To a layman (me) it would seem seriously destabilizing to have a hole that's perpendicular to the direction of flight, esp. since a delta wing seems to pull off more or less the same shape without the hole.
I found out about this via one of Aaron Swartz's blog posts: http://www.aaronsw.com/weblog/dweck

It's a good read.
I'd do it for 250k + bonuses.
Humblebrag... or most just brag.
There's an SRFI that outlines an indentation based Scheme syntax called Sweet-expressions. It also adds infix operations.

http://srfi.schemers.org/srfi-110/srfi-110.html
I don't necessarily agree with GP, however there is currently no good measure, and that's one reason to bolster his opinion.
Startup Explainer Video DIY in 4 hours and $34
Out here in sfusd, middle school is known as the weak link. Benioff recognized this and specifically donated some money to try to improve them.

However, it may be difficult to overcome a structural difference. It's telling that middle school is the one area where public and private schools completely diverge. Private schools are almost always K-8, followed by a separate high school. This happens for small very expensive private schools as well as larger parochial schools which often serve a more middle class or low income population (often reaching a similar scale to public schools), so it's really not a function of scale. Only the public schools seem to engage in the practice of separating out students for 6-8k.
> It's not about being "programmers" but rational human beings.

I mention programmers because of the forum. And no, programmers tend to nitpick more. We are trained to nitpick more, because that's part of how you get bulletproof code. And that's great when dealing with code. But it can be problematic in discussions because it easily leads to derailing off into little niggling points. Like this one.

> Your clarification here should have been in the parent comment to begin with.

No. No, no, no. One does not have to put every possible caveat into one's initial statement, especially when the context is established. That just makes for very long, boring things that nobody reads. I trust that most readers will approach things with smarts and goodwill. When there are multiple ways to read something, I trust that they will find the most useful one. If all that fails, I hope they will say, "Hey, did you really mean X?" Which in this case happened.
Startup dilemmas – Strategic problems of early-stage platforms on the Internet
This, if you've ever ridden in the jump seats of a jet and felt your head and guts go sideways during climb out it is very disconcerting. You know that feeling that the jet it tilting way up when your sitting forward? You get the tilt is really sideways when you are sitting sideways. I expect you get used to it but it no doubt makes those seats hard to sell.
The video on the analysis page explains it:

http://www.minedata.org/analysis/

We'll get the source scripts in git soon.
Am I the only one here wondering why the layout of an airplane interior be something patentable?
It's not quite the same, and here is why:
In audio, the samples from an ADC are generally very close to point-samples indeed. Not quite, because ADCs can not sample the input at infinite small times. Or actually really point-like if generated algorithmically.

However, this is not true for pixels.
The meaning of the pixel values in a source image is arbitrary. It can be point-like, but I would argue it mostly isn't.

Pixels in a display device /never/ are point-like. They always fill an area. That's just a physical reality.

We also can not use a simple band pass to limit the (spatial) frequency content. If you take the videolinked in the sister comment, and assume that t is a spatial direction.

A pattern like __^^^___^^^___^^, that is black-white-black-white... would show ringing when the slopes don't match pixel borders. What do we do instead? Either align it, or integrate over the pixel area. I.e., the pixel overlapping the slopes would have grey values.

(Edit: realized parent post didn't link the video)
Once again the meme that China was hacking to find dissidents was a lie for propaganda purposes, and the actual motivation was to see who the USG had wiretap orders on, to see if any of China's own spies had been burned.

But, it makes China sound evil when you tell the public that they are doing it for human rights reasons.

http://www.washingtonpost.com/world/national-security/chines...
I genuinely can't tell whether the article is suggesting that Inbox is for advanced users or for non-advanced users (and GMail for whatever the other user is). I believe, based on my own understanding of the two products, that GMail will continue to exist for advanced users, and Inbox will be simplified. But, the article is not at all clear on that; the last sentence seems to flip the meaning of the rest of the article and indicate that Inbox is the "advanced" one, while GMail will be made more simple. Or something.

Author can't English good.
I get it, it's just worded in a really strange way.
I guess that given the sense of urgency I felt, I wanted to get the person breathing as soon as possible, and I knew from my personal experience that the HM was very effective.

I've also read that back blows may further lodge the blockage in the throat, especially if you can't get the person to lean over, and this was a concern for me as well. Whether it's true or not is hard to know, but when your family member is choking and close to losing consciousness, you really don't care about breaking ribs! It's kinda the same with CPR - you don't care about breaking ribs, and it's pretty common for that to happen during compressions.

I'd be interested to know what the potential injuries are from the HM - is the main one breaking ribs?
You can have an object lodged in your throat in such a way that it allows you to exhale but not inhale.

As a child, I remember choking on a bit of bread or pastry or something. I couldn’t breathe in, but I could wheeze and make noise. I was able to dislodge it by pointing my head downward and exhaling forcefully with my remaining air, effectively an internal version of the Heimlich.
I do not mean to be rude but anecdotes are not data.
Another good emacs site is http://www.masteringemacs.org
What are McRib patties made of? [video]
Make patents 100x more expensive and see if they still think that.
No, and I didn't pass it off as data. It's a personal anecdote, as I have stated.
Give me the metrics of a good programmer, and a way that they could not be gamed ...
...?

He's guest authoring a post on TechCrunch - they probably asked him for a bio so he gave them a unique anecdote, an impressive one at that.
"...but I think they're too rare now for it to be wise to use them"

The ligature of 'f' and 'i' is not "rare" and it is not "unwise" to use it. Actually many professionally typeset books are using it: it's not an "idea" as you wrote. It is something very real and often used.

It is so common and so good looking (I'd even say "so perfect") that you probably never noticed it but I can assure you that it's used in many of the books / newspapers / magazines you've read during your life.

I've written and typeset about a dozen book (one with LaTeX, all the others with QuarkXPress: it was before the InDesign days) and I can tell you that when I see a non-ligature "fi" I directly notice it because it is really poor looking.

Of course in addition to LaTeX, both QuarkXPress and Adobe's InDesign and several other professional typesetting software do the common ligatures.
There is also this theory http://arxiv.org/pdf/1212.1110v2.pdf which avoids the stratagems used in the ΛCDM model.
You couldn't use this for communication as there is no way to "set" the spin of an entangled photon. You'd effectively have two receivers for the same random signal but no way to actually influence the signal.

I think there was a HN link a while ago about ideas to use this as a perfectly secure key exchange mechanism for crypto. I don't know how serious this idea is, though.
I use tmuxinator in a similar fashion.

Starts my vim instance, bash prompt, sources virtualenv, server instances, and console/repl.

I start-up in about 5 seconds.
That's disappointing. So in the end, Twitter is no better than Google or Facebook when it comes to user tracking.

We are the product, indeed.
It should not be patentable, but, unfortunately, the bar is very low at the moment.
It's certainly a great resource and extremely comprehensive. Personally I think it a bit too detailed to be an effective beginner's guide.

And I say this as one of the credited authors of the LaTeX wikibook (https://en.wikibooks.org/wiki/LaTeX/Authors)

Therefore I'd still plug my own Getting to Grips with LaTeX as a good starting point for newbies: http://www.andy-roberts.net/writing/latex/

I promise that's my final plug :P Quite frankly I'm just happy people want to learn LaTeX other word processors.
It's not written very clearly, so I can understand the confusion, but that's not how I interpreted the article. It sounds more like the sequence of events went like this:

1) Based on their observations of user behavior, the Gmail team started pushing to simplify Gmail's interface;

2) This prompted a backlash among Googlers, who use Gmail for their work email and therefore need the sort of power-user features that would have been dropped in a simplification;

3) The Gmail team pushed back with a "you are not the user" argument;

4) A giant political furball ensued, with the stakes being whether Gmail would become a simplified email tool for general consumers or a power-user email tool;

5) The "power-user email tool" side lost, but as a peace offering they received a consolation prize: rather than dropping their ideas altogether, the Gmail team would build a separate product (Inbox) incorporating those ideas. (I call it a "consolation prize" because any separate product will have to fight for its own user base, making success much harder than if it could roll out to Gmail's already massive user base.)
iOS apps can use GPS in the background, as long as the user permits it. I use it to map my travels all the time!
Back in college I would typeset my polisci and literature papers in LaTeX. Professors would write notes about how great my papers looked, they were so used to Word.
(La)TeX the typesetting engine is great, but (La)TeX the language is clunky. Without proper support for namespace, it's rather difficult to abstract and write macros without worrying about side effects. I have real troubles to guess which package a command is from.

Are there any alternatives that have solved this problem?
The Startup Founder and the Russian Nut
This happens in business class on many airlines (long haul). I've never felt it to be a problem at all.
Oh, that could be. Mathematics and computer science are the only fields for which I've read many papers, and they tend to be LaTeX.
Simple tweet crashes iOS Twitter app
Thanks for writing these, i found it easy to pick up latex by following them.
C++ is steadily adopting D features :-)
Brilliant.

I always learnt more by doing. A few years ago I came across ARCalc[0] and playing with it really made me grok functions. Now SineRider gamifyies the exploration of functions. Neat!

[0] http://www.pouet.net/prod.php?which=30468
I'd spend time on IRC where very smart developer hang out and exchange ideas. I learned a lot on there by asking the right questions to people who are much better than me at those skills.
If you haven't tried it already, look into `latexdiff` and `scm-latexdiff` which are awesome for generating diffs.
While I don't mind the cold too much, for me the darkness in the winter is really frustrating. It seems like such a small thing, but when it gets dark at 4:15 it really takes away my motivation to go outside.
>This will lead to a division like in the early 90s again, where to do serious work you need a "workstation" which will be quite different to a normal machine.

I'm not comfortable with that... at all, but it may not be a bad idea.

As Alan Kay says, computing is the one field where, thanks to Moore's Law, you can live in the future just by spending enough money. He puts forth a pretty good argument that one of the problems with modern computing is that it's too incremental, and one of the reasons for that is because most programmers (and students) use consumer-grade laptops and desktops, and thus they're stuck writing code for yesterday's state-of-the art hardware. On the other hand, programmers using workstations can write for tomorrow's consumers. He attributes much of the breakthrough progress of the 1970's Xerox PARC to its willingness to buy the researchers and programmers $60,000 workstations (that's adjusted for inflation, and they built 80 of these)[1][2]. The expressed goal was to be able to develop software for the computer that would exist 10 years hence.

[1]http://history-computer.com/ModernComputer/Personal/Alto.htm...

[2]http://data.bls.gov/cgi-bin/cpicalc.pl?cost1=10000&year1=197...
Since it is a template you could always use universal references to avoid copying where not needed:

template <typename Collection,typename unop>
void for_each(Collection&& col, unop op){
std::for_each(col.begin(),col.end(),op);
}

I'm happy to see more people reading Bartosz, I find his blog very interesting. One point to emphasise about that particular post is that the proposed range library he discusses is already available today, and has been for some time, in the much overlooked boost.Range library.
Not exactly; just considering the trade-off of sacred cow vs. tasty burger. I'm not opposed to property or possessions, but I do think the burden of proof is on the believer rather than the skeptic, and our society seems to put a higher sanctity on property than on community or commons, as though it were an immutable axiom of the universe. (I'd also really like to hear a First Principle on the subject that doesn't contain "Because USSR".)