skysight-inc/HackerNews huggingface dataset:
That's alleviating the symptom, rather than fixing the problem. When one needs an IDE to read a plain text file, it's time to stop.

Why don't I use an IDE to read it? No, how about why doesn't the original coder write the code for other people to read, instead of forcing me to use an entire IDE just to piece together what they're doing, like I'm some kind of code archaeologist.

I'm debugging this thing across a flaky modem line through which I'm getting an echoed terminal, I've managed to get gdb running and narrowed it down to a handful of suspicious lines of code, and the gimboid who wrote it assumed that everyone who ever looked at it would actually be using Visual Studio 20-whatever with all the plug-ins, rather than plain text a line at a time. Brilliant.
"Yes, you could solve that problem with complex, interdependent systems that will fail in unpredictable ways."

Isn't that what you have now by depending on people?
It isn't perfect, but Lombok[1] helps with this. It uses annotations to automatically generate getters and setters. The downside, of course, it yet another dependency and more annotations.

[1]: http://projectlombok.org/features/GetterSetter.html
Nice, you totally cut and pasted out of context:

>>Often in the media, protesters can gain sympathy for their cause by prompting authorities to take physical action against them.

>"blame the victim" right from the start (2nd paragraph). I guess that sets the tone for the army people who are normally pretty isolated from social issues and don't have very well informed opinion of their own.

Sentence immediately before this in the same paragraph "During unified action, U.S. forces should never violate basic civil or human rights. Most protesters are law-abiding citizens who intend to keep their protests nonviolent, but some protest planners insist that the event involve violence."

>>The level of violence is determined by the willingness of demonstrators to display and voice their opinions in support of their cause and the actions and reactions of the control force on scene.

Again, the sentence before this one: "Violence can be the result of demonstrators beginning to conduct unlawful or criminal acts and authorities (who are responsible for the safety and welfare of all) enforcing the laws of the municipality, state, or nation."

You're biases are clear.
I'm assuming C++14 will have 1320 keywords and a bunch of weird operators to use so people can ignore it even more than it's being ignored.
I admire Java for the fact that it is significantly more painful to write mutable rather than immutable classes.

I love C#, but I do wish that setters weren't so easy to define (and that classes were sealed by default, and that fields were read-only, and that all extant warnings would become errors, etc.).
Because it takes an enormous amount of work, most of node.js source code (or at least a lot of it) is basically libuv bindings for V8. To make it work on top of SpiderMonkey is a lot of work (though multiple people tried). And the gains from having it run on SpiderMonkey are questionable, at least until more of the ES6 fanciness is implemented - and then the question is where V8 will be at that point.

P.S.: It could always make sense to make a "modern Node.js" that embraces es-next features for core APIs, but that's still ~1 year out.
what do you mean?

C++ is a language designed by committee. C++14 is meant as a "tock" release, fixing some of the things in the C++11 "tick" release. ("tick" releases are larger, and "tock releases fix some of the problems in the "tick" release).

Compilers then attempt to implement the standard, and have their own versioning system.
How to build an audience with YouTube
If you want to rid yourself of GC problems, go buy Azul's Zing JVM. It works like magic.

(disclosure: I'm a very happy customer of theirs)
4 Ways to Restart the Mac Finder
The version number identifies the tonnage of crap that has been added since C++98.
Until now there have been four standardized versions of C++: C++98, C++03, C++11, and C++14. And the versions have been consistently named (to be precise, "nicknamed") as "C++YY", where YY are the last two digits of the year in which that ISO standard was adopted.

Note: C++03 was a very minor change (sort of a "bug fix"), so people sometime refer to C++11 as direct successor of C++98. Also in the interim (2007) there was C++-TR1 ("ISO/IEC TR 19768:2007") which was not a formal standard per se, but instead a technical report specifying bunch of standard library extensions (which were formally included in C++11)

For sake of completeness: The format C++YY is the one which is commonly used almost everywhere, but the official language name follow ISO's convention. Here is a mapping:

C++98: "ISO/IEC 14882:1998 Programming languages C++"

C++03: "ISO/IEC 14882:2003 Programming languages C++"

C++11: "ISO/IEC 14882:2011 Programming Language C++"

C++14: "ISO/IEC 14882:2014 Programming Language C++"

There are also language classifier like (E), (F), etc present at the end (e.g., "ISO/IEC 14882:2014(E) Programming Language C++"). I am not sure if the official standard is fixed in a particular language, or are all the different language translations equally authoritative (I suspect the latter, but it's just a guess).
Are you targeting small business (e.g. restaurants) or large retailers? Restaurants want more control of their customer feedback, but it's not easy for consumers to visit many different sites. Small businesses need a service that can be integrated as easily as Disqus, but that provides end-users with easy search & submission of reviews.
CSS Conical GradientColor – Color Picker in Pure CSS
This is pretty cool, It would be nice if github provided all of that data in their graphs tab
In the article, it says: "Bob claimed to be philosophically opposed to marriage; Jacqui was fine with that." so I suppose they didn't get married at all.
"Another aspect of this massive population outflow hasn't yet drawn much attention. Whatever their motives and wherever they go, those who depart will be shadowed by the organs of the Leninist state they've left behind. A sprawling bureaucracy—the Overseas Chinese Affairs Office of the State Council—exists to ensure that distance from the motherland doesn't dull their patriotism. Its goal is to safeguard loyalty to the Communist Party."

That quote reminded me of this[1] New Yorker article on the first case of "economic espionage." It's an interesting read and a look into a different kind of "spying."

[1] http://www.newyorker.com/magazine/2014/05/05/a-new-kind-of-s...
I don't think there are any new keywords for C++14.
Nothing can jump an AirGap.

Literally nothing. If something jumped an AirGap then a USBdrive, or CDrom/DVDrom, etc. was infected. In which case the system wasn't Air Gapped, it was part of a sneaker net.

Most commonly we refer to sneaker nets as Airgaps, when often their just as vulnerable as a normal network. Dirty USB sticks are an old as the hills hack at this point.
Actually it was an anti-monopolistic protest against a lower tax on East India Corps tea.

Today, we celebrate monopolies or think they can't exist via deregulation.
Q&A with Nigel Kersten, CIO Puppet Labs
The premises in the argument can abstracted into the following:

if doom_soon, then the probability of myself being in cubicles 1-10 is 100%;
if doom_soon, then the probability of myself being in cubicles 11-100 is 0%;

if doom_late, then the probability of myself being in cubicles 1-10 is 10%;
if doom_late, then the probability of myself being in cubicles 11-100 is 90%;

???

Therefore if I am the cubicles 1-10, the probability of doom soon is 81%;

In any logic class, this argument would quickly be pointed out as a fallacy. The statement of "if p, then q" says nothing about the truth of p, given q. Which is exactly what this argument seems to do, reason backwards from the conclusion when none of the premises are able to be logically inferred from the conclusion.
That's tame compared to what'd it'd be like most places, think XBox live but with grown-up insults.
Here's why a reasonable reader might come to the conclusion that this is not in fact a post about correlation, but rather a device for making a drive-by dig at Sam Altman's post:

* The Redis example is forced. Here's why: most engineers faced with that problem would, sooner rather than later, collect stats about the nodes and immediately observe that the root cause was an overloaded server. As the post admits, the cause was immediately obvious. No statistical reasoning was required, and, in fact, this reader doubts that statistics played too much of a role in Stucchio's own diagnosis. (Whether it actually did or didn't isn't material to my point.)

* The insight being provided about correlation is extremely simplistic. Essentially, it communicates in two graphs the definition of correlation. That might make sense if the post was written in a fashion that tried to communicate the fundamental idea of correlation to someone with literally no acquaintance to the term. But it's not; despite having subheds about what "is" and "isn't" correlation, the writing style more clearly signifies that the author is trying to debunk a mistaken idea about what the term is, implying that its readers are already somewhat acquainted with the idea. Or, put more simply: the fundamental idea the post tries to communicate could have been conveyed in two simple sentences. (Glass houses about my own writing style: duly noted).

* The transition from technical discussion to Sam Altman is abrupt. More importantly, the Altman subject has much more valence than the point about diagnosing Redis failures. Thought experiment: chop everything in this article after Redis out, and imagine it was posted not by Chris but by some random account. Would anyone pay attention to this post?

Unfortunately, the post doesn't have much insight to offer about Altman's post. It's framed Altman in a manner incompatible with Altman's post --- suggesting, contrary to reality, that Altman was trying to present a complete empirical argument about gender disparities in technology. It then tries to beat Altman over the head with that framing. Altman emerges unscathed, because the author is swinging at his shadow, not him.
If noone bothered to send in reports, we cannot assume it is really working, can we? After all, without testing, software most certainly doesn't work.

Who is this John Lewis guy and why isn't his work the part of the official Coreboot images?
Here's a song for English-speaking people to get the experience of listening to American pop music without understanding the words: https://www.youtube.com/watch?v=E77HpMMbDYc#t=83
Community Health Systems data hack hits 4.5M
> Robot butlers 'a gimmick', says hotel workers' union

TV is just a passing fad, says radio broadcasting insiders.

Horseless carriages are noisy and dangerous, says teamster's union.

Power looms aren't a threat, says textile workers society.
Does

return combine( stage1(), stage2() )

bother you too? because that infers the return-types of stage1() and stage2() as well.
"I don't give a @!#? about aesthetics... I have a business to run."
Did you just compare honest hard working taxi drivers to mafia? If government didn't require licences for taxi drivers, you'd have some crazy place like Russia where anyone can be a private driver without any licence and customers actually get cheaper prices and can get cars any time of day in seconds by just raising a hand and negotiate the price beforehand. Oh wait...
"Today, China's borders are wide open. Almost anybody who wants a passport can get one." What's wrong with this?
On the importance of line width, character count, and kerning in title text
I guess that's the part I disagree with. I think Uber and Lyft are mostly doing harm, and not even an interesting new kind of harm: shady taxi companies skirting laws to up their profits is as old as the taxi business. (And doing it "with an app" doesn't make it tech, either, any more than Domino's Pizza is a tech company.) And in some cases (like Sweden) I suspect the conflict is even manufactured for PR purposes: Uber relies on "disruption" PR for its marketing, so has to manufacture disruption even where there isn't anything actually standing in the way of just running a legit taxi company.
The 4th edition of Stroustrup is quite good, and much better than the 3rd edition, which was not even very usable as a reference, due to a terrible index. It's still not a page-turner, though.
Leave it to Americans to approach good coffee this way. It's neither better nor worse than the Australian way (which has produced top level coffee for a long time now), but I prefer the latter as it seems a bit more pure than infusing the process with VC funding and a hungry pursuit for profits.
I see no blame anywhere in the article, and claiming that:

> army people [...] are normally pretty isolated from social issues and don't have very well informed opinion of their own.

is both untrue and offensive.

EDIT, never mind I see you took the bold stance of commenting from a throwaway.
Wouldn't surprise me if wireless hardware companies are involved in this. I'd be much more comfortable with passive sensors being used, but then you couldn't really do traffic optimization. If it's lives you're trying to save go passive. Animals cause accidents too. If traffic congestion is the goal, then we can start talking about this.

> The information sent between vehicles does not identify those vehicles, but merely contains basic safety data. In fact, the system as contemplated contains several layers of security and privacy protection to ensure that vehicles can rely on messages sent from other vehicles.

With all of the stuff talked about in the article I don't see how's that supposed to work.
I really like the direction C++ is moving in. I just really don't like how incredibly VERBOSE it is (though `auto` helps).
There is an official JSON API: https://jcp.org/en/jsr/detail?id=353

But it is unclear how many of the existing implementations conform to it, and it definitely doesn't work toward your misguided One True JSON Implementation goal.
But, of course, the US has never been a Democracy. It is a Republic.
(sounds like all four of you could use a good forest walk :))
Why? It's only relevant to the person responsible for the site, if they're here they can follow up for details otherwise they're irrelevant.
`begin...rescue` is almost syntactic sugar for `case...when`. Actually, for a brief period it was possible to use any object that responded to #=== in `rescue`. That turned out to be an accidental feature and was reverted, but the first version of toe_tag was built on top of it. Now I just make sure to inherit from Module and that's enough.

It's good to know people are interested in this! That's enough to convince me to get it hooked up with Travis CI and give it an official, supported 1.0.1 release.
Impressive cherry-picking ability you have there.
Whilst we're comparing police forces:

"Last year, in total, British police officers actually fired their weapons three times. The number of people fatally shot was zero. In 2012 the figure was just one. Even after adjusting for the smaller size of Britain’s population, British citizens are around 100 times less likely to be shot by a police officer than Americans. Between 2010 and 2014 the police force of one small American city, Albuquerque in New Mexico, shot and killed 23 civilians; seven times more than the number of Brits killed by all of England and Wales’s 43 forces during the same period."

http://www.economist.com/blogs/democracyinamerica/2014/08/ar...
Training will not help a driver localize where a EV is approaching from. I'm not suggesting this system would supplant traditional warning systems, but would simply augment them with additional information. It would allow drivers to make better decisions about how to yield, rather than having the decision forced upon them when I'm suddenly right on top of them.

If it's relevant, I'm firefighter/paramedic, been driving EVs for a decade or so.
Facts and Figures from One Year into an Ecommerce Startup – Uproot Wines
The sugar your parent proposed would still be nice and has precedent in other languages with option types. Swift has something very similar[0], and Rust is debating it[1]. Haskell's do-notation and Scala's for-comprehension are other solutions to the same general problem of conveniently using option types.

It may be a good thing to only support that sort of convenience for option types and not for nulls, in order to further encourage their use. Although using nullable types is already pretty darn convenient!

[0]: https://developer.apple.com/library/prerelease/ios/documenta...
[1]: https://github.com/rust-lang/rfcs/pull/204
Your public facing methods/accessors are a sort of contract between a class, and whatever uses it.

The contract basically says: "I will behave as you expect me to and as we agreed but only as long as you only interact with me in the predetermined(designed) ways that I allow you to"
the key items are naturally embedded in the "context" so an argument like yours can always be made, yet these key items are the ones that's getting ingrained in the minds of their target audience. Basic skill of good copywriting.

to the rayiner below - there is no argument that protests are crushed much more violently in the rest of the world (may be except for a couple of countries like England and Germany). There is a reason i left Russia where just calling for a protest is a felony these days :)
Here's a class C with a variable v of type T. It's supposed to be something that the rest of the world can access. You can make it public. Or you can make it private, and write

public T get_v() { return v; }

So far, not much difference. Both let the world access the variable, and both break encapsulation by doing so.

The difference comes when the class gets more complicated, and v changes. Now v might be null, whereas it never could be null before. But if it is, then what the rest of the world saw as v should now be some default value. So we can say:

public T get_v()
{
if (v != null)
return v;
else
return default_T;
}

and life goes on for everybody that was using v. But if all we had was a variable that everybody accesses, then all the users have to change. They either have to access the new getter or, worse, they each have to copy the logic to check for null.

This is how the getter encapsulates the inner workings of the class, and why it's a really good thing.

P.S.: How do I specify code formatting on HN?
Didn't expect to see a Thelonious Monk article on HN! He's my favorite piano player, hugely influenced my own playing.
Are you aware of DCEVM? https://github.com/DCEVM/DCEVM#readme
The nice thing about C++11 is that the designers seem to have actually tried to increase usability, rather than just maximizing expressivity, which is usually the case. Features like range-based for and auto make programming much more pleasant. I program in a functional style in many other languages, but could never bear to in C++ before because it was so awkward.
It would be a non-trivial problem in urban environments, where the sound has almost certainly taken a few hard reflections before it got to you.
IMO Dart has the best implementation of properties, which you can start out as normal fields, e.g:

class Rectangle {
num left, top, width, height, right bottom;
}

and can access like normal:

var height = rect.bottom - rect.top;

But can later be changed into a computed property without affecting the above callsites, e.g:

class Rectangle {
num left, top, width, height;

num get right => left + width;
set right(num value) => left = value - width;
num get bottom => top + height;
set bottom(num value) => top = value - height;
}

C# is a close 2nd, but it's not binary (or reflection) compatible to change from a field to a property for call-sites (i.e. it's only source-compatible).
Lol I just posted an issue about this. Let's assume it was an honest mistake :)
When I started writing C++ around 5 years ago, I had a perception that it was a language that is "on its way out". As I learned more and more of it, I've been super impressed at how modern it is becoming, and how it is adapting to overcome its perceived flaws. It is becoming a killer language to me: blazing fast, modern, ubiquitous, stable, and expressive.
Recent standard draft (2014-03) https://github.com/zygoloid/cplusplus/blob/master/papers/N39...
> not using flash cards because sometimes contextless learning is not ideal would be throwing away the baby with the bathwater

No, that would only be the case if one decided to stop learning the language all together because they think they'll never be fluent.

I'm proposing to learn the language properly: by exposing yourself to as much material as you can, for prolonged periods of time.
I loved this article.

Unfortunately I now have a burning urge to rejoin TBW ARG which I thought I had escaped from :(
Startup Sim: Hipster CEO is free on the App Store for 24 hours
This is called null-value propagation. It's coming to C# (6) this year.
Neat! I had been trying to figure out what library to use for the upcoming Ludum Dare competition, and I think this answers it.

I'll probably be peppering you with questions/feedback next weekend, in that case. Are GitHub issues the best way to do that?
If you're looking for actual DNA coffee, check this: http://www.coffeegenome.org/research/ICGN_W3_concept_note.pd...

:)
In languages like C++ "verbose" means "specific and obvious" which is something you want to have when writing certain kinds of code.

It's annoying, it's a drag on productivity, but in the long run it's arguably necessary.

Some other languages which reduce verbosity by making more things implicit make it harder to understand what's actually going on behind the scenes. You lose a lot of information.
What is wrong with restarting your application?

Edit: Real Hotswapping will requires profound changes to the memory model. It would introduce too much complexity. I rather restart my application than to suffer from a fragile and leaking platform.
Red Big Barn does not always sound wrong to me. If there are ten big barns and ten small barns, and one of the big barns is red, I would call it the red big barn, not the big red barn. But if there is just one isolated barn, and it is red and big, then red big barn does sound weird to me.
All those things were true when they were said. Its the implicit "in their current form" that's the kicker.
> No one writes "vector<int>::size_type sz = v.size();"

No, but plenty of people write "size_t sz = v.size();" which is equivalent (or superior) in the vast majority of real code. And in the rare situation where the return value of size() is not an unsigned integral type, obscuring that fact with auto is bad form.

The sensible generalization for auto is to use it to avoid specifying ugly template specializations when they are both clear from the context and otherwise unavoidable. So "auto it = x.find(f);" is clearly superior to "std::unordered_map<foo, bar, foobar_hash>::iterator it = x.find(f);" etc.

The real danger with auto is to use it when you don't know what the real type actually is, which is what people are tempted to do. But if you type "auto sz = v.size();" when you've specified some unusual template arguments that cause size() to return uint16_t, you're now obscuring the unusually small width of sz which could plausibly lead to integer overflow.