skysight-inc/HackerNews huggingface dataset:
The guidelines say:

Please don't do things to make titles stand out, like
using uppercase or exclamation points

and:

Otherwise please use the original title, unless it is
misleading or linkbait.

I think the idea behind this change in title is because the original is perceived as being linkbait; it has an explanation point, is very opinionated. The kind of thing that really tempts you to click through, or come and post a scathing rebuttal, because of how strongly worded it is.

Not saying I necessarily agree with the new title, but it is milder, and I think that in general moving away from clickbait titles is a good thing. There's enough clickbait junk going around the rest of the internet, having at least some standards at HN is fine.
"They took two weeks to deploy the fix. Considering those two weeks included Christmas and the bug didn't affect security or render the site unavailable, this seems like a pretty good response time."

Note that plenty of smart companies have things like production freezes at holiday times :)

So this is not entirely surprising.
Silicon Valley is still getting it wrong on income inequality
"the way it would seem to"

{} initialises all elements to 0.

{0} initialises the first element to 0 and the rest to 0.

The latter form just introduces confusion.
The user agent (by itself) provides you none of those things....

> Why are you pretending that there is some sort of difference between "tracking a user" and "tracking the user's browser"

I'm not? That isn't what I said.
Why we shouldn’t worry about leaving print behind
Relatively, yes.

Other comments suggest being based in a different location around the country instead – those will have both cheaper labor costs and cheaper office space. Will the ratio ever go below 5% though?
The number of ratings agencies isn't the problem, who pays the agencies is the problem: it's the issuer of the debt in most cases. This arrangement is more efficient than buyers paying for ratings, but misaligns incentives. Supposedly mutual funds do additional research on debt issues beyond looking at ratings, and that might help, but it isn't very public.
I thought Babel 6 was some kind of satire on Javascript build tools. I even hit him up on Twitter. In fact Sebastian was serious. https://twitter.com/drewhamlett/status/681245325282164737
> ...disproportionately strong...

Emotion is great. I want to understand other people's emotions, which means titles should express them if they are present. It's for precisely that reason that I appreciate tamping down "over the top" linkbait, if that's what this is.

Understanding others' emotions gets hard if everything is a life-threatening emergency†. It's like watching CNN during their worst years: every possible event got a "BREAKING NEWS" banner. It made it hard to stratify emergencies. If every title devolves into "THE INTERNET IS ABOUT TO EXPLODE because git just went to v2.8" HN would become useless to read.

† I'm not saying that's what this article is doing, just making an example.
Possibly there is better communication between the YouTube and Chrome teams than between YouTube and FireFox. As in they probably cross test each release.
And pretty much all of them are unreliable garbage...

So you have experienced thousands of unreliable garbage apps. I feel really sorry for you. My experience has been the opposite: lots of wonderful and reliable programs. And when I found one that wasn't good, I stopped using it and replaced it with a better one.

I mean as a user. As a programmer I've seen all kind of programs, from "critical mission" to "quick hack" and from excelent to unreliable garbage. And you know what? It's not language features but ludicrous incompetence what makes an app unreliable garbage. There are programmers out there that can make unreliable garbage in any language.

The "secret" to make some app reliable is not reserved to NASA and the like. Follow two simple patterns:

1. For every user action, validate input, try executing the code, catch the occasional exception and show an error message.

2. For every resource, allocate, try{ using it } finally { release it }

Put each of these skeletons in a function or method, so the resource is a local variable (no colateral effects) and it's easy to debug.

That's all. Well, also: don't be too "creative" unless you know what you're doing (most times you don't).

I'm fifty-something, spent a lot of painful time mechanically applying that recipes to rotten codebases, and when I read the kind of criticisms you made I assume they come from people too young to have real world experience on what they're criticizing. The alternative is worse: to be the kind of people that created that rot and then blamed the language.

Just in case: I don't believe that manual memory languages are "better". I love Python and (most of the time) JavaScript.
Hackazon – A Modern Vulnerable Web App
That would be better, but not per user, per session. Currently I have surf(suckless.org) just pick a common one when I launch a tab (via tabbed): https://github.com/jakeogh/rndagent
Sounds like the ultimate solution here is to just give browsers a killswitch, so they'll eventually just stop working if you don't keep them up-to-date. (I'm not sure whether I'm joking.)
Anonymous Communications Network Called PrivaTegrity Launched
I'm with you. In fact my last project I simply wrote my own build script by including the dependencies that normally would have been wrapped with grunt / gulp and used them directly. So much easier and far fewer development dependencies.

Grunt and Gulp make building slightly easier. Slightly. That's really it honestly. In fact my build scripts look very, very similar to what a Gruntfile.js file looks like.
Maybe the current prices are already low enough that raising them would make the customers go away?
I get what you mean. Our application broke during the Redux 3.0.4 => 3.0.5 transition because one of our other dependencies didn't play well with the new version. Yes, that is just the tip of the iceberg.
That's a fatuous response. There are many reasons why San Francisco doesn't have New York City levels of public transit, the most important of which is that it's a comparatively tiny city, approximately 1/8th the size of New York, by population. If the "bay area" were a single city with a single government, it would be much easier to build a comprehensive transit system.

Moreover, New York has been one of the world's largest cities for over a century. It's had a while to get good at things. San Francisco was a cow-town until the 1980s.

I realize it's self-satisfying to blame NIMBYs for everything, but the facts are more complicated.
Actually, it's a great point. For the vast majority of us, coffee is coffee. I have an Aeropress that I use at work and Keurig's at home. I can't tell the difference. So tailor your configuration to the masses with options to configure if that user has "better taste buds".
No particular materials right now besides the website.

We expect to collaborate with many third parties over time. We're just getting started, so not sure on the specifics yet!
Thank you! I never did quite get the point of fashion. Now I know it's just another one of those things that I'll understand when I'm older.
Off topic but does anyone know what terminal emulator is being used in those screenshots?
Unless you need to support ancient devices, SNI SSL on Azure is $9/month.
Every year someone learns to program and for some reason the first thing they do is start lecturing.
+1 for just starting with bootstrap - which will introduce you to a little jQuery. That'll be a good foundation and will allow you to have some fun without being overwhelmed.

Once you have that in your pocket you'll be ready to try any of the new js frameworks that are being mentioned here.
This is best thing I read all day!
I've always believed that "linkbait" is a MIDLEADING title or one that omits key information only to force you to click on an otherwise uninteresting title.

Linkbait: "You won't believe the disgusting thing this A-list star did in public!"

Non-linkbait version: "Tom Cruise accidentally stepped in dog poo."

The first is linkbait because it teases you to learn who the star is and what was the disgusting act (which was actually quite boring).

--

Linkbait: "This company sucks at app stores!"

Non-linkbait: "Amazon sucks at app stores!"

The first is linkbait because it forces you to click to learn which company it's talking about. It would most likely make the reader think it's about Apple, or maybe Google Play Store, both of which are probably more interesting than Amazon's store. The second title is NOT linkbait because even though it's inflammatory, it conveys enough information to let the reader decide whether it's worth a click. The reader immediately knows:

* It's about Amazon app store.

* It's going to be very negative.

If the HN reader is interested in how Amazon's app store is doing and how users are reacting, then it will stand out as a link worth clicking. If the HN reader doesn't care for an opinion about amazon's store, or doesn't want to read a strongly-worded one, they'll pass. There was no baiting at all.

---

I argue that the editorializing of the article created MORE of a problem, because it wiped away an important piece of information for HN readers: that this is a strongly-worded negative review. The edited title ("Amazon is relatively new..") conveys no information about the article. Frankly, it now sounds like a very dumb article.
Well, I can't see the year it expires, but it was likely the year of publication, or maybe the next.
Mathematicians invent new way to slice pizza into exotic shapes
compare the experience of using both coffee machines, even if the former doesn’t give you the exact kind of coffee you want, you are still far better off.

Documentation is terrible for applications. If you think that your application really requires documentation, it’s too complicated, and it’s going to make your users frustrated.

I strongly disagree. There is value in providing good defaults, but users will and should be encouraged to go beyond them. That's what the documentation is for.

Being frustrated is also normal. It's a natural part of the learning process. If everyone was always expecting everything to "just work" and gave up the moment they encountered the smallest bit of frustration, nothing would ever get done.

That said, although there is a lot of superfluous complexity in software today (dependencies are mostly responsible), I don't think it justifies turning everything into unconfigurable featureless appliances or not writing documentation. General-purpose computers are immensely flexible and powerful, and if we want them to remain that way, I think it's well worth putting in the effort to learn. The culture of instant gratification that seems so prevalent today may become counterproductive in the long term.
I have to strongly disagree with you. I run my own online thing and find that keeping expenses down has given me a huge competitive advantage over similar sites.

I would also stress that there are other reasons to keep complexity down, like hating to do paperwork (or work of any kind).
Calling something linkbait doesn't mean that that thing is factually incorrect, or even a bad title. It just means it's a superstimulus for off-topic debate. HN isn't a magazine; it's a forum. What the articles get labelled isn't about being accurate, or even evocative; it's about eliciting productive discussion.
Why does a transpiler need a configuration? Isn't the whole point of it to transform one set of script to another set? Seems to be a very basic set of default configuration items could be (and should be) integrated into said application and allow advanced users to override.

But yeah in node land if you don't upgrade to the latest major you're going to be left behind in bug and security fixes (good luck finding projects with actually maintained LTS branches and if they exist they're almost always the previous major version and nothing further back).
Commercial success and quality ("good movie") are obviously very different things. Critics care about the latter. Quality is hard to quantify, but that's no excuse to take such a poor proxy as sales. If you want to test whether Rotten Tomato scores are meaningful, I say you'd have to test whether they are meaningful to a particular individual with particular tastes; i.e., test the correlation of someone's judgments against a critic's.
I carry an apple watch that does not make it past 36 hours of strictly telling time. (feeling spartiate again, maybe I'll finally order that pebble... :-)
Slightly off-topic but holy cow, this! I've been describing this to many JS developers when it comes up and I find that many feel entirely the same way but we tend to not do anything about it. Gulp can use babel, babel can use webpack, webpack can do babel, it's madness frankly and yet the pattern continues. Maybe I'm beginning to become a curmudgeon but I'll just sit out of this game and use stable tooling and potentially other languages that can provide a more mature workflow. What really gets me is there are things like Dart that don't get a lot of traction though it provides mature support for a lot of the things we need to bolt on to JS to make it a usable and productive language. Not that you need those things anyway to be productive I digress.
Yes, I was criticizing the whole industry. Publishers abuse the tools ad tech provides to basically steal money from brands and often at the expense of consumers. Brands are so eager to cut costs, they ignore the basic principal that you get what you pay for. Big agencies use these tools to mask hidden profits. VCs invested gleefully at the opportunity to "disrupt" the agency business. And the anarchistic emergence of ad tech is what's made this all possible.
ddrescue also shows progress by default. Not sure if it has a comparable feature-set as dcfldd, but for data rescue/forensics, it definitely does the trick, and seems to be much more actively maintained.
I remember McDonald's and Burger King burgers in the late 70s (as a wee child) and in the 80s. I remember them being DELICIOUS.
Define sufficient.
Its in the middle of Manhattan, so there are grocery stores everywhere - Trader Joe's is just a chain with a particularly strong cult following, and there are fewer of their stores in Manhattan compared to a lot of their competitors.

(I like Trader Joes well enough, but even when I lived very near to that specific store I'd make a conscious effort to avoid it. Proximity to New York University's dorms seems to do it no favors on the already very busy 14th St corridor.)
There's also StartSSL (https://www.startssl.com) for certificates too. You can get basic ones for free or pay a relatively cheap amount to get more a higher tier validation. I've been using them for years successfully, and when combined with SNI, I no longer need to pay for a multi-domain certificate.
I am sorry but what is AR deployment?
Dell Has a Severe Tech Support Scam Problem
'El Chapo' Guzman: Sean Penn Interview Provokes US Scorn
An abuse of power to achieve... what, exactly?

dang is here as a moderator precisely "on behalf of the community." As in, he acts to facilitate productive discussion. You might disagree with his decision here, but I can't see any way in which he has different goals than you would want him to. At worst, he has made a mistake, and the backlash from it will make him not do it again. (At best, he is being "the hero we need" by attempting to stop a flamewar argument before it starts, even if that means taking the heat that that flamewar would have spawned entirely himself.)
Cologne attacks: New Year's Eve crime cases top 500
The hard part of optimizing code is to find areas were your code is weak at and taking too long to do something.

In my best practices and I learned this from a video by Grace Hopper, is to use less code to do the same thing. Less code takes up less memory and usually runs faster.

Just writing code and then compiling it without any errors doesn't mean it is done. You still have to optimize it and do security checks as well as quality checks. You still have to check for bugs and side effects. You have to use it and think like a user would to see how the user would see it.
Yes, this is correct.

I just realized I misread the GP's comment: thought it said "P-value" in general instead of "P-value of Pearson correlation," as a result I thought he was referring to a regression P-value.
Looks like Pantheon Terminal used in elementary OS
Quite frankly, Im surprised the reason behind this isnt common knowledge, at least among us geeks.

The reason is hardware designers have hit a wall, they cant make single threaded applications run any faster.

So your brand new gaming PC is no faster at running single core applications than your 10 year old computer is. You can copy over any single core application from your new PC to your old one, and it will run just as fast.

What your new computer has is more cores though. Ideally you want linear scaling. That is if you have 2 cores your program should run twice as fast, and if you have 256 it should run 256 times as fast. This kind of scaling is almost impossible to achieve. Most programs don't scale beyond a certain number of cores.

Your multithreaded program might run a bit faster if you throw an extra core at it, but very quickly throwing more cores at it doesn't make a difference. It might even get slower. You have all those extra cores idle, or worse they are busy waiting.

Most programs dont scale well to many cores because any synchronization between cores kill scalability. If you have ANY sequential steps in your application that will put a limit on scalability.

As an example say you have 4 cores. You have a main loop on one core, it posts expensive work to the other (3) cores. And when they are done, you collect all the results and use them somehow. This final step is sequential and it kills your scaling. Your application wont run 4 times faster. And it probably wont run any faster if you throw 16 cores at it. This is because that one core is synchronizing with all the other cores. So those other cores do a lot of waiting around. And any sequential steps in that one core becomes the bottleneck, as those other cores will all end up waiting for it.

This message is already too long. So long story short. Single threaded programs are no faster on new computers, and most multi threaded programs dont scale well to many cores. Its a huge wasted opportunity to let cores be idle or underutilized. We have to fundamentally change our programming style and tools to take make use of all available cores.

More info by Herb Sutter:

http://www.gotw.ca/publications/concurrency-ddj.htm

http://herbsutter.com/welcome-to-the-jungle/
Yes, I don't know why really. I actually started at like 8
In the JS community there are overkills à gogo, a cacophony of many build tools, package managers, various --pilers, minifiers, maxifiers etc. The cadence of reinvention is unfathomably fast, I don't understand how one keeps up, but I guess most of the non-problems these quasi-tools solve would easily be solved with make and some vendoring, though that is already invented and time-tested ergo bad and boring...
The Martian Won the Golden Globe for Best Comedy
AMAZING 44 YEAR OLD SKATEBOARDER
It's a part of the learning process.
From what he describes, it might be something like a quota service or an ad service that does consistency checks over the course of user sessions to fight spam/abuse/crawlers.
I have shared your experience with front end tooling. I was recently pleasantly surprised by browserify. Next to no configuration - just a few chainable deps that are all built to work together. All in all, it took about 30 minutes from start to end to get a es6/jsx transpiler -> JS working.
I am a remote worker. Our team averages 15-30hrs/wk each. Some of us never get above 15. I personally average 25-30 when I'm at home, and 15-25 when I travel. I travel for about 6 months out of the year.

If I am not in someone else's company and am able to open my laptop, I'm working. What I mean by that is when most people would be lounging on their couch with their laptop cruising reddit, or watching TV aimlessly, or reading, I end up thinking about work and then just clock in. I get my general goof-off online time via my phone when I'm getting from A to B or am otherwise not in a position to open my laptop.

This means I very often end up working 7 days a week. I think a few times this year I hit 38hrs in a week. I generally keep track of work via my phone when I'm unavailable or working less and if something pops up I clock in and take care of it.

This is just my nature and I'm happy I've found a job that gives me this type of flexibility. Filling work time into the bits of downtime that would otherwise be wasted allows me to match my free time to those that I love, like my father or partner (who is a schoolteacher and has frequent vacations).

Maybe this isn't for everyone, but if I had to back to a traditional work environment I'd probably lose my mind. The ability to travel, visit my father for a few weeks, take a 10 day vacation with my partner multiple times per year (plus summer/winter break), wake up whenever I want, work out for 3hrs 3x per week, followed by an hours at the pool - that's amazing. I wouldn't trade this for anything.

I think I am much, much productive in this type of work environment than any that I have ever had. It makes my work better, more focused, and keeps me happy & loyal. Flexibility is king.
Isn't it false to say "the expected value of a lotto ticket is greater than its cost" as opposed to "the expected cumulative value of all lotto tickets is greater than their total cost"?

Because, a given ticket can only have the values of jackpot (or share thereof), intermediate prize (or share thereof), or zero (most being zero).
And what's wrong with that? As long as the attention-seeking is not hurting anyone, then this is probably a great way to find and meet like-minded people. He's not hurting anyone. If he truly enjoys the Newton, then he's not even hurting himself.

The universe is terribly lonely as is. I'm not going to fault anyone for their harmless attempts to reduce the loneliness.
Exactly. Spammers can use any email address they'd like and Verizon simply passes it on to the recipient. A spammer used one of my domains (with valid SPF records added years ago) and texted thousands of Verizon customers. I intercepted all replies to the texts with a catch-all email and found hundreds of complaints including several death threats and a father who told me his young daughter received a porn text from my domain. After 3-4 days, their spam filter finally kicked in. My domain was blacklisted and I basically had no control over it.
You can program in vim, or program in an IDE.

You can also code in assembly, or in C#, or python, or however.

It's about the features the program brings. It's your choice to use something else - I'm just providing (a hopefully better) alternative.

Best,
John
I think the point of the parent comment is that they would have done it right away even if Chrome usage had been at the same 3.5% share.
Do you believe there is a limit to what models we can train with layers of differentiable units?
You missed the 'connect' euphemism

"She advises couples who sleep at different times to make sure they find other times to connect, whether it’s the morning, the half-hour before the first partner goes to sleep, or even the weekend."