skysight-inc/HackerNews huggingface dataset:
> I think there are several lessons to be learned here.

Indeed. Unfortunately, they've mostly been learned by others before this, and ignored or forgotten. If you want to see how these issues have been dealt with in the past, look to a project that's been doing the same thing for much longer, such as CPAN and the Perl module ecosystem. It's been around for quite a while, and is very mature at this point. Here's a few features that I would hope other module ecosystems would strive for:

- Mirrored heavily, easy to become a mirror. [1]

- Immutable by default, older packages migrated to special archive version of system which does not archive older packages. [2]

- Indexed in multiple ways (author, name, category) and searchable. [3]

- All modules tested regularly on a matrix of multiple operating systems, language versions, and module releases. [4][5] There's also often a few different architectures tested to boot (IBM/z, Sparc), , but that may be quite a bit less regular.

- Static analysis of modules as a service to authors to help them possibly identify and fix problems, as well as reporting . [6]

- Module installation defaults to running all tests and failing to install if tests fail.

- The ability to set up a local private CPAN mirror for yourself or your company (you can peg your cpan client to a specific mirror). [7]

Undoubtedly there are features of other module ecosystems that CPAN doesn't do, or doesn't do as well, and could look to for a better way to accomplish some things, but that's the whole point. None of this exists in a vacuum, and there are plenty of examples to look to. Nothing makes any one system inherently all that different than another, so best practices are easy to find if you look. You just need to ask.

1: http://mirrors.cpan.org/

2: http://backpan.cpantesters.org/

3: http://www.cpan.org/modules/index.html

4: http://cpantesters.org/

5: http://cpantesters.org/distro/P/Path-Tiny.html

6: http://cpants.cpanauthors.org/ (CPANTS is distinct from CPAN Testers)

7: http://blogs.perl.org/users/marc_sebastian_jakobs/2009/11/ho...
> The todo-list of an average home-maker today would be more complex than that of the princes from a few centuries ago.

Well yes, they had other people to manage their todos :)
Yes, the astronauts have been there.

Edit: clarify astronauts http://www.joelonsoftware.com/articles/fog0000000018.html
depends on whether the additional platforms are trivially ignorable or not.
I stand corrected, there doesn't seem to be a way to manually allocate and de-allocate memory. Looks like there is a switch to turn off GC, but it's intended for debugging.
It's great, but without tinkering - you never really learn how things actually tick.

I always chuckle to myself when I'm told by 40-year-olds how their 14-year-
olds are "so amazing with computers!". But yeah - Jimmy can open up Facebook on the iPad like nobody's business, but Jimmy has no fracking clue what's actually happening or why, or how to even diagnose common issues. Then again, maybe that's ok if Jimmy doesn't give a crap about how computers work.

I grew up in Europe and never had a car until I was in my late 20's so I never tinkered with them. Now, if something goes wrong, I just take it to the dealer. So I'm like Jimmy with the iPad.

There's no problem for me or Jimmy. The world is fine.

But then there's Billy. Unlike me, Billy didn't grow up with DOS and early Linux, so Billy has never had to look at a hex dump or figure out what pointers are or registers or flags - Billy just hits "Go" in his Java IDE and prays everything works out. If it doesn't, his eyes glaze over and he heads over to Stackoverflow.

Billy is hampered by today's world. He doesn't have to tinker with his PC or iPad, but not only that, he's actively being prohibited from tinkering with them. They're not only appliances, they're sealed off, protected by dozens of copyright and patent laws appliances that you don't even technically own anymore without signing-off on 7 different legal agreements. It's insane.

Billy might never learn about how a computer actually works. And one day he'll have to diagnose/fix something that only the 30-somethings can and he won't know how, and not because he's dumb.
Note that this is mostly caused by the fact that mobile game developers are courting such a distribution by making "pay-to-win" games where you can pay more to get advantages without limits.

While such a structure means that a game developer can earn 10k or more from a single player, it also makes the game worse for those who aren't willing to spend unlimited amounts of money and thus drives some of them away or causes them to decide to not spend any money at all.

If this is not desired, the simple solution is to have an "unlimited pass" that gets you access to all current and future IAP/DLC content that gives a game advantage for either a fixed one-time fee or a fixed subscription fee.

This is probably not often done because the game developers believe that it would be less profitable overall.
I dislike the model for this reason:

1. Game devs have an incentive to make the game crappy unless you pay
2. When it comes time for you to pay, you have to support all the freeloaders.

I would venture a guess that most games could have higher median "fun" and still only charge $2-$5 . Instead of charging one person $10k and 5k ppl nothing.

just my thoughts though, no science/data to back it.
>> The BSDL does not make much economic sense to the company open sourcing their code

If this were true then Cloudera, Horton and a whole bunch of other companies would be out of business, yet in reality they are doing really well. All that AGPL is doing for Citus is:

1. Turning away people (customers) who are religious about licenses.

2. Eliminating any possibility of this code ever being integrated into PostgreSQL
For an example of this taken to a ludicrous extreme, several years ago an AWS user complained that downtime of a few EC2 instances were putting lives at risk. They were hosting cardiac monitoring services on single EC2 instances with no multi-AZ or multi-region capability.

AWS forum post: https://forums.aws.amazon.com/thread.jspa?threadID=65649&tst...

Previous HN discussion: https://news.ycombinator.com/item?id=2477345
It's called the 80/20 rule -- 80% of a result caused by 20% of its participants: https://en.wikipedia.org/wiki/Pareto_principle
Only if you don't know what you're doing. The problem with DNS is that it might work even when it is misconfigured, and misconfiguration is the source of strange issues.
Oh gosh, I thought it was a super odd comment :)
Plus four police officers. And there's also this testimony:

According to San Francisco court records, Nieto's former friend Arthur Vega described a March 5 incident in which Nieto had used a stun gun.

In a March 14 request for a restraining order, Vega said Nieto shocked him four times in the back in front of his wife and 3-year-old son. Vega said he had been picking up his son when Nieto appeared and forced himself into his wife's car.
Vega said Nieto had screamed profanities. He and his wife got away, but two days later he saw what he believed to be Nieto's car following him.

http://www.sfgate.com/crime/article/Man-killed-by-S-F-police...
they are not bashing programming communities, they are bashing stupidity.
Another idea that's not supported is the pathological way function scope is interpreted. The two dang functions in the MRDV flow past each other, like a case fall-through [2], but for function scopes. It makes sense artistically in the comic, but I'm not super clear on what it would even mean in terms of a real program.

[2] Only Duff's Device comes to mind here, but I think we're looking at something more pathological with the MRDV

https://en.wikipedia.org/wiki/Duff%27s_device
To quote an old adage, package size doesn't matter.

The actual issue has to do with trusting a package of any size over time. This is true regardless of whether the package implements 1 line of code or 1000.

The trustworthiness of a package is a function of several factors. Code that is not actively maintained can often become less trustworthy over time.

What we need is one or more 3rd party trust metrics, and our bundling/packaging utilities should allow us to use that third party data to determine what is right for our build.

Maybe some of us want strong crypto, maybe others of us want adherance to semver, maybe others want to upgrade only after a new version has had 10K downloads, maybe others only want to use packages with a composite "score" over 80.

On the continuum of code quality from late night hack to NASA, we all must draw a line in the sand that is right for a particular project. One size does not fit all.

It's a big mistake (as well as a profound example of bad reasoning) to blame micropackages. The size of the package has nothing to do with it. Any codebase with any number of dependencies faces some risk by trusting the maintainers or hosting of those dependencies to third parties, which is the problem we need to do a better job of solving.
As the author of Groups on iOS and the Qbix Platform (http://qbix.com/platform) I think I have a pretty deep perspective on this issue of when "my thing" becomes "everyone's thing".

When a company goes public, there are lots of regulations. A lot of people rely on you. You can't just close up shop tomorrow.

When your software package is released as open source, it becomes an issue of governance. If you can't stick around to maintain it, the community has a right to appoint some other people. There can be professional maintainers taking over basic responsibilities for various projects.

Please read this article I wrote a couple years ago called the Politics of Groups:

http://magarshak.com/blog/?p=135

This is a general problem. Here is an excerpt:

If the individual - the risk is that the individual may have too much power over others who come to rely on the stream. They may suddenly stop publishing it, or cut off access to everyone, which would hurt many people. (I define hurt in terms of needs or strong expectations of people that form over time.)
Some of us haven't seen the story yet. I'm guessing those who upvote the story are part of that group. Maybe a better mechanism would be a feature that doesn't show you stories (grouped by URL) that you've already interacted with?
How Freudian!
It's rather sad really, taking advantage of some people's propensity to addiction, exploiting it for financial gain. Somewhat the digital equivalent of rigged casinos or drug pushers.
Keep in mind that flagging drags a story down.

In my experience, story quality plays a big role and luck a somewhat smaller one. Because what makes a story good on Hacker News can be a bit different than what makes it good on other sites someone with 2000 karma is probably more likely to submit a better story -- e.g. right now this submission about a fourteen year old Linux text book: https://news.ycombinator.com/item?id=11352295 is on the front page -- simply based on the likelihood of greater engagement and more experience.

My observation is that many stories that get 100 upvotes in an hour generate low quality discussions and disappear due to flagging, though there are exceptions.

My unsolicited advice is to write good comments and post good articles and not get to tangled up in trying to optimize around timing.

Good luck.
"Don't implement critical systems with tools that any idiot can use, because they'll show up."
I've played Boom Beach for over a year without paying a penny. If the game were to say "Content beyond lvl 10 is $1 a month" I'd probably pay .

But $12 is nothing to me, and dear in other locales.
I was recently testing out google's OCR for some PDF docs - it thought it worked really well (and is pretty reasonable priced). i didnt care so much about the structure of the response/document.
So, the ideal to-do list will be defined in prolog?
"high performance" is a bit vague. maybe "particularly latency-sensitive" or "requires quasi-deterministic execution time"
> The more categories you add, the more blurred do the boundaries become.

I think that's kind of the point. There isn't a single coherent dependency for all cultures for all content.

To have a simplified single set is to place one (semi arbitrary) value system over another.

You could study the correlations and common concurrent uses, and maybe provide common suggestions, like Amazon does. But again, boundaries and weirdness.
Regarding the category-specific severity levels (instead of "low", "medium" and "high):

The three levels currently used are definitely not completely arbitrary. I'm sure we all can tell mild violence and really severe levels of violence apart. But I definitely see your point, nonetheless.

For "nudity", the different levels of "bare buttocks" versus "full (frontal) nudity" come to mind, for example. This caught be implemented in custom severity levels, of course.

But the major advantage of the three general levels is that the higher ones include the lower ones. That makes things as easy as choosing one severity level for each category.

If, for "nudity", you have the two levels suggested above (and potentially dozens of other levels), you have to provide a check box for every single level or "sub-category". That's far more complex, both from a consumer UX perspective and from the tagger experience.
This article and the comments here saying "This is common knowledge in the industry" and "I'm getting tired of people saying this is a bad thing" are a beautiful illustration of why mobile games suck and freemium is destroying the industry.

There are plenty of good games out there. The problem is nobody plays them. Then the devs of those games say "Fuck this, I'm out" and go on to start making pay to win games because that's how to get paid making games. It's gotten to the point where the games we play aren't even fun; we just find an easy game that lets us shoot up a shot of dopamine once in a while and settle for that. Or maybe we pick up clash of clans, play "free" for a month, then once we're hooked we pay way more than we'd ever pay for a real game every month just to be competitive. And we still lose, because someone else has more money.

The majority of popular mobile games are a costly addiction, not a hobby.
Courts enforce the laws. Policing (detective work, particularly) is to identify people to feed into the court system.
What is nefarious, or at least extremely sloppy, is that the paper's authors claimed prominently that they had captured all of the data on every concussion in the NFL within the time period. Also, they included the games played by the teams that provided no data in the total, which therefore reduced the incidence rate of head injuries in their final analysis.

From a companion article in NYT:

“It was understood that any player with a recognized symptom of head injury, no matter how minor, should be included in the study,” one paper said.

And in confidential peer-review documents, the committee wrote that “all N.F.L. teams participated” and that “all players were therefore part of this study.”
Python 201 – OrderedDict
> If you don't like the content in movies you don't have to watch them.

Your comment is incoherent.

This website is a tool for people to use for themselves to decide if they want to see a movie or not. How do they know if they don't like the content in a movie? this site will tell them.
The #<value> at the end of the linked URLs is what's letting them get past dupe detection. It happens sometimes.
It kind of depends, Go's GC cycle in recent releases is minimized so that no GC cycle will last more than N milliseconds (I forget the specific amount), depending on your specific timing needs, it may be acceptable... You can also write your program so that objects/references are held and GC doesn't happen, depending on your memory constraints and needs (ram is cheap, and systems with 64-256GB are possible relatively inexpensive, compared to developer pay for a month)

Though Rust is probably more appropriate for your needs, in terms of more modern languages.
No, you can't republish an existing package version after unpublish. (unless you ask npm nicely and they know you)
That depends on your setup, for the master instance you'd run it just as you would for other setups. Streaming replication is common there. For the sharded instances, Citus has the ability for you to set what your replication factor is. Here Citus is then aware of when a node fails and will automatically redistribute the data to a new node, essentially taking care of that for you.
That's one of the easiest thing to do. Just add multiple NS to the domain. As long as they are configured correctly and at least one is up (and for limited time even if none are up) the service is available.

With DNS you actually can achieve 100% uptime.
Just for anyone who was confused as I was...the submitted URL is a sidebar for the massive article markrote links to. That said, I like the submitted URL because it's another example of how bad data (in this case, the database of concussions sloppily put together by the NFL) can be combined with old-fashioned research and reporting (looking up old football game news articles) to find damning evidence.

Or, more broadly speaking, never trust a dataset without corroborating it with your own research.
"I'm sorry" is me telling you what I am.

"Please accept my apologies" is me telling you what to do: take what I'm giving you.

I can easily give you my apologies without being remotely sorry. Sorrow is a feeling, but apology is a statement.

But it's still up to you to decide if you want to take the apologies I want to give to you, or disregard my polite command that you should.
The size of the package matters when smaller packages tends to higher numbers of packages as dependencies.
> Why? The "jokes" were clearly in bad taste, and meant to belittle women.

Can you quote the jokes and explain how they were meant to belittle women?
> There isn't a single coherent dependency for all cultures for all content.

Really an important point. Thanks!
But isn't this kind of the point? This gives you a programmatic way to specify to your media player just what content you don't want to watch. If this stuff gets popular, then the publishers should feel less pressure to censor themselves.
Citus owns the copyrights, and the CLA ensures that they will continue to. That means that they can reassign it under a different license if they so choose, and they could at some point choose a liberal license.
All right. This I can agree with.
Thanks, twists my head but as far as I see it could work.- IANAL
I wasn't planning on signing up at all—to my knowledge, nothing about this single-page-app requires a session at all.

The risk here is that I don't want the app creator to know my name. It's that simple—I don't know them, I don't trust them, I trust them less now that they ask for completely unnecessary information. Let's say traffic to this site is linked with lower credit scores: it's naturally absurd that the two are causally related, but it's a reality that I have zero control over how my traffic data relates to how companies use it. All I can do is reduce my traffic data from getting into their hands where I can help it.
Terrible, terrible practice. But I think a lot of people got caught out as left pad was usually an indirect dependency, and using npmjs in your build is the quickest way to satisfy your dependency graph.
i'm not particularly experienced with go, but it does work directly with pointers iirc. all it lacks is an explicit memory free function, i think. is there more to it?
Exit value volatility was a known risk when the hedge funds started investing in the Valley.

Exit timing volatility is a new phenomenon. It's one thing to say, "within 5 years they'll be publicly traded/acquired and I'll have liquidity at an unknown value." It's another entirely to say, "in an unknown amount of time the company will be publicly traded/acquired and I'll have liquidity at an unknown value."

The latter prevents the hedge fund from actually creating hedges.
So are many non-military technologies. I don't see the link here with google building assassination machines.
The entire point of this project is, as shown in the title of this HN submission, that it provides you with the freedom to filter. No censorship forced upon you.
I'm running a Lenovo S540 (the line has been discontinued but it is an ultrabook). It's processor isn't as good as the 4th gen X1 carbon you can check the comparison here: https://www.cpubenchmark.net/compare.php?cmp%5B%5D=2608&cmp%...

My S540 has an SSD,16gb ram and the slower processor and it churns through work fine, I mainly do Java development and on top of that I use the Play Framework which compiles to both Java and Scala so it's more CPU intensive.

I can easily run one or two IDE instances alongside 10+ chrome tabs,several terminals and mongo/mysql db GUIs.
You have a point but it's also ridiculous that mobile game consumers expect every game to be free. Game studios often spend tens of thousands of hours developing a mobile game, why should that be free? The freemium model is just an unfortunate consequence of this cultural shift towards expecting all mobile apps to be free.
How physical violence is possible in US schools?
- As I know US has very strict laws against physical violence
- Students in US schools can be suspended not only for actual violence, but also for thread of violence and even for gesture: http://www.nbcwashington.com/news/local/Montgomery-Co-Studen...
You think that the fundamental principle behind the First Amendment and Enlightenment philosophy was that we really needed a natural rights justification to have people whose politics we disagree with ostracized from public life and prevented from earning a living?
Altman's Playbook is probably a popular reference: http://playbook.samaltman.com/
Exactly, thank you!

And, in consequence, reducing the level of censorship that is forced upon you without your consent.
I moved from OMZ to Antigen, how does Prezto compare to Antigen if you've tried both?
Has anyone actually gotten to download the thing? I just get a we'll be in touch.
Book does not understand its audience. "An editor is the program that you use to edit source code." No "advanced" programmer needs to be told that. OK, maybe if all you know is an IDE, you don't know this...but the book says it's assumed that the reader can do basic command-line stuff. If you can do that you must know what an editor is.

Also I saw "GNU/Liux" in the front matter.

[edit] Next section started "A compiler turns human-readable source code into machine-readable object code that can actually run."
Wrong, it really does mean that it takes energy input to fuse iron and hydrogen. Naturally existing heavy elements are the result of supernovas, where a percentage of the energy of the dying star is converted to fusing elements beyond iron.
Any clue as to how this will be priced? Before I even consider putting time into this i'd like to know how competitive the pricing is going to be if this graduates.
Would you mind submitting this documentation to CMU? I get the feeling they'd love to at least host a link to them or something to enhance their own documentation?
What if they wanted to host a conference about technology? Are they allowed to do that?
The glaring security hole in Docker is that it has not designed a solution for keeping secret data necessary to build an image from being in the image at run time.

They also haven't solved the general case of keeping transient build data out of the final image either, but that's a broader problem that doesn't necessarily involve security concerns.

For now not a lot of people are concerned about either problem so it's not getting the attention it deserves. But they've been steadily peppered with inquiries about these issues for a year or two now and they still don't have an answer, which is concerning. I believe this is one of the reasons the CoreOS guys wandered off to do their own thing.

Fortunately for us and unfortunately for them, they have the design aesthetics of the Marquis de Sade, and until they start giving even half a thought to ergonomics, Docker is perfectly safe.
So... no, then?