skysight-inc/HackerNews huggingface dataset:
> “When you use the word ‘accident,’ it’s like, ‘God made it happen,’ ...

I do not agree; this is just a bullshit word semantics game, a game which ends as soon as we crack open an authoritative dictionary.

"Accident" has a nuance of referring to a chance event, but that clearly doesn't apply in the context of an auto wreck; only a moron would insist that "accident" in "car accident" is being used with the same nuance as "cosmic accident".

The sense of "accident" used in "car accident" unmistakably refers to the lack of intent (in a situation where human intent could conceivably exist).

It has no sense whatsoever of absolving anyone of responsibility.

If someone does something by "accident", that in no way precludes the root cause being that they are a klutz, moron or reckless goon who could have prevented that from happening.

It's a perfectly good word that we can keep using, thank you very much.
The link I presented was aggregate government spending, it was not restricted to federal spending.
I did a book a couple of years back. Motivations were:

- I have been working in a particular speciality long enough that I felt I had something worth sharing with others, and was also lucky enough to be in a company that allowed me to write about the work we had done.

- Just having done it, being able to see a book with your name on it on the shelf, give it away to friends and family etc.

Some observations:

- I did the book with co-authors. I have other colleagues who are attempting to write books by themselves, and are struggling with motivation under the sheer enormity of the task. If you have coauthors you not only cut the per-person workload down, but also get the benefit of peer pressure to keep things moving along. Being the lead author, I also learned a lot about managing and organizing a distributed group with strong opinions and different approaches, which was an education in itself.

- You mentioned you have existing technical articles. Having a starting point is a great leg up versus a blank page. Our book came out of a conference presentation for which we had to write up detailed notes. So we effectively had about 30% of the raw material ready before we started on the actual book.

- As others have said, it is a lot of work. Hofstadter's Law definitely applies.

- It forces you to really know your stuff, and to double and triple check things before committing them to immortality.

- The first royalty check is surprisingly decent, I believe due to initial sales to libraries etc, but it quickly drops off. As others have said, you are almost certainly not going to be doing this for the money.

- Publisher quality varies of course, but don't necessarily expect too much from them. In terms of editing, they will pick up on some typos, but not much else. We did everything in latex so there wasn't really much extra to do. But if you calculate how much money they make from the book, it is not surprising they do not allocate a lot of resource.

- You will get completely sick of reading and rereading the text, while still finding more errors.

If I was to do it again I think I would go the self-publishing route, just to try it, since I honestly don't think the publisher did much for us in terms of marketing or editing.
The researcher states that they compared people in these generations when they were at the same age, so I would think the absolute values were used.
> Callbacks, promises, generators are all there to essentially make async code sync

I think they actually do quite the opposite: they keep async code async. JavaScript doesn't really have a (non-terrible) way to make async code sync.

Note that I'm assuming that by "being able to use return values of my methods without sweating," you mean "get the thing I want out of the return type somehow." Or, in other words, things like getting a value out of a Future. The problem with that approach is that it blocks the calling thread, so what happens if you have 50 connections? Or 200? Or 10,000?

The same reason I like that JavaScript and JavaScript libraries try very hard to keep things asynchronous is the same reason highly concurrent software tends to be event based rather than thread based: it's simply more efficient.

I think it can be a challenge to keep mental track of state in JavaScript due to the nature of async stuff, but it can also be liberating in a way once you figure out the right way to pack away your state for whatever problem your working on. It makes it easy to break things into small components and reason about pieces instead of the whole while maintaining decent efficiency compared to having tons of threads around.

There's also of course the incredible niceness of JavaScript being single threaded in that typical multithreading concerns are not a problem. If you want to update a variable in some callback, you just do it. You don't have to worry about locking or atomicity, etc. I can't tell you how many times I've ended up with a mess of Java code in which I'm not actually sure if it's correct or not. That's likely my fault, but still something I enjoy getting to not think about when doing JS.

In short, I suppose it just comes down to different preferences. I often find myself working on concurrency in Java and wishing that it were more like JavaScript :). Interesting, the JavaScript approach can be pretty easily recreated in Java (and sometimes a very useful tool), but the Java approach is much harder to do in JS, at least with Node.
We are biased by all sorts of things.

Right, so who makes the algorithms?
Go still has (slow, dynamic) unwinding for the express purpose of resource management. While I can't advocate for using it directly, it is enough of a concern to include in the core language.
Meteor Hunt
>Why isn't PERL more windows friendly?

That he probably didn't google hard enough.

On top of StrawberryPerl, there is also BerryPerl which is perlbrew for Windows.

http://blogs.perl.org/users/steve_bertrand/2016/07/berrybrew...
I think you're right that it's more productive to concentrate on increasing income rather than decreasing expenses. On the other hand, you will never be wealthy if your expenses rise faster than your income, and it's possible to easily spend any amount of income.
I thought that was the most unrealistic thing this season: a supposedly genius programmer who loves tabs and hates spaces.
I think there's pretty good evidence those safety features have helped a lot! People were almost twice as likely to die in a car accident in the 1980s than today [1]. I'm not an auto crash expert -- and I admit that safer roads and better traffic enforcement could be a portion of this -- but I'm pretty sure the lion's share of those gains are simply more crash-tolerant cars.

> and I guarantee my behavior changed due to it

But did your behavior change enough to make up for how much more dangerous it was? Would the median driver's in the same situation?

[1] https://en.wikipedia.org/wiki/List_of_motor_vehicle_deaths_i...
There’s one final catch worth knowing about. I said at the start I wanted everything I listed to be open source. Graal & Truffle are huge and very expensive endeavours written by skilled people who don’t come cheap. As a result, only some parts of what I’ve described are fully open source.

These bits are open and can be found on github or other repositories:

Graal & Truffle themselves.
The pluggable version of HotSpot they rely on.
RubyTruffle
Sulong (LLVM bitcode support)
The R, Python 3 and Lua implementations (some of these are hobby/research projects).

And these things are not open source:

TruffleC/ManagedC
TruffleJS/NodeJS API support
SubstrateVM
AOT support

TruffleJS can be downloaded for free as part of the GraalVM preview releases. I don’t know how to play with TruffleC or ManagedC, although as Sulong implements some of their functionality, it may not matter much.
If you have (created!) a job that closely resembles a work of dystopian fiction, laughing that off is absolutely lacking in human empathy. That's not even the first problem with this line of work, but since you're also laughing off the problem, it deserves a rebuttal.

If I said to you that I was going to create a network of surveillance devices that also serves as mindless entertainment and routinely broadcasts faith routines that non-participants will be punished for, and you told me that sounds like something out of 1984, and I told you were paranoid, you'd think I'm mad.

And the advance of technology unhindered is not a universal good. Algorithms only have better judgment than humans according to the constraints they were assigned. If there's a role for automation in criminal justice, that role must be constantly questioned and adjusted for human need, just as the role of human intervention should be. Because it's all human intervention.
AFAIK the vast bulk of Microsoft's revenue continues to come from software: OS, Office, and Server products. I've not seen a breakdown for some time.

Microsoft have been trying to get out of this for quite some time. Back when I worked for a very large revolving credit transactions processor, the stated goal was to get into the online payments game (this nearly 20 years ago now). Microsoft Passport was among the products aimed at this effort, which ultimately failed, attributed by many at the time with the lack of trust any other business had at getting in bed with Microsoft standing on their revenue stream.
How does RAII deal with reference loops? It is trivial to create a loop of owned pointers in memory that never decrement, and it isn't that unusual of a pattern not to be a concern.

Just curious; I used a combination of strong/weak reference counting when I dealt with this. It wasn't fast, but it did appear to be less prone to implicit leaking.
You can try to save people from themselves, but it's never quite as effective as you expect.
https://www.youtube.com/watch?v=_47utWAoupo

Imagine the ridiculous driving when people "know their car will stop before a crash anyway". Yeah, more people will be saved overall... but there will be a lot of "funny" results too.

Personally, I'd rather have strict penalties than being forced to do the equivalent of trading a linux laptop for an iPad Pro just so I can't hurt myself or anyone else. (I drive a stick shift of course, and can turn off traction control :)
I don't like Angular 1.xxx that much because in Angular 1.xxx building simple stuff in JavaScript is a no no. Angular doesn't play nicely with JavaScript. Instead you have to do Angularjs way and write the Angular specific code in your 50 Angular specific HTML attributes. Performance of data intensive apps is particularly lousy in Angular. In my opinion it's a framework written for people who like complexity for complexity's sake.

I don't want to be hunting all over my code base just to figure out what is happening in a controller or component.

JPs styleguide is awesome!
Makes sense. The pair seem to know what they're doing, so they probably checked city law beforehand to make sure everything is alright.
My background is physics, and I used to think that, but now working as a data scientist that has to deal with human data, I've come to think the opposite. The signal to noise ratio in human data is humongous, nothing is static, and there are zillion of moving parts. That means you need immense volumes of data to run well powered experiments that are designed to get at real causal factors. And there are ethics involved so you have to deal with potential early stopping in a statistically sound way. In some fields (like econ), you don't even really get to do experiments at all on most topics of interest, having to rely on the observations available.

But it turns out that it's worth applying the scientific method to these fields, so what you're left with are tough choices. To deal with these problems the way we would in a physics experiment would be prohibitively expensive, in the literal sense of prohibitive. You have to come to terms with the fact that you can only afford to get enough data that there's a non-negligible possibility of being misled. It's worth doing science here, and we can, but it's just plain hard. I didn't appreciate that before I started having to deal with it. Don't blame the subject for some practitioners' failings.
This project was built using code I wrote previously for this pure javascript fractal renderer: http://jonathan-potter.github.io/Mandelbrot/

Jamie Wong's post on hacker news earlier this week was a massive help in allowing me to switch to using WebGL for the rendering portion. His post can be found here:
http://jamie-wong.com/2016/07/06/metaballs-and-webgl/
Here's the paper, just in case others are like me unable to grok the punch-line: http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.40.4...
>I never understood such an upmarked Myntra acquisition.
Because it was a merger forced upon them by the common investors - Tiger & Accel.
Stating that method A is problematic does not automatically mean method B is better.

> The reality is humans are far worse

Citation needed - especially when comparing against a specific instantiation of a machine learning model. Papers published by the statistician in the article used only 516 data points. Most data scientists running an A/B test wouldn't change their homepage with only 516 data points. There's no guarantee the methods he is using for the parole model involve better datasets or models without deep flaws.

An algorithm or machine learning model is not magically less biased than the process it is replacing. Indeed, if it's trained on biased data, as you believe by stating "never ever trust human judges", then the models are inherently biased in the exact same way.

If you give a machine learning model a dataset where one feature appears entirely indicative (remember: correlation is not causation), it can overfit to that, even if that does not reflect reality.

I highly recommend reading "How big data is unfair: understanding unintended sources of unfairness in data driven decision making"[1], by Moritz Hardt, a Google machine learning researcher who has published on the topic (see: Fairness, Accountability, Transparency). It is a non-technical and general introduction to some of the many issues that can result in bias and prejudice in machine learning models. To summarize, "machine learning is not, by default, fair or just in any meaningful way".

Algorithms and machine learning models _can_ be biased, for many reasons.
Without proper analysis, we don't know whether it's a good or bad model, full stop.

[1]: https://medium.com/@mrtz/how-big-data-is-unfair-9aa544d739de...
One of the the few times where the inverse square law is helpful.
I find them more readable than the endless wall of indistinguishable text of pick-a-random-news-site. Of course all the text is readable, and there's innumerable ways of increasing the readability. But their art direction and effort to distinguish particular content helps it stand out and helps overcome the kind of fatigue that causes readers to drop off within a couple paragraphs and has plagued other content-oriented sites with horrifying "minutes to read" estimates.
Fukushima photography, Keow Wee Loong, and his completely fabricated story
Most humans can't magically triple their income. Personal accounting and living frugally is their ticket to upward mobility.
I remember playing Railroad Tycoon as a kid. I never realized that the train it showed on startup was copy protection. I just thought it was a stupid guessing game that they threw in as a bonus or something, like they wanted to make sure you knew all the locomotive types before you got to them in the game.
I did something similar in pay terms a while back and I agree with a lot of what is said. Here is my "how to"

I am assuming you have a job, but this should work if not.

Put aside every lunch hour and scan the want ads and job sites for positions that match your skill sets. Don't go for things clearly you don't match - but stretch a little too.

Apply for them all. Make sure it is easy to send from your phone. Reduce the friction.

Call the agent / hiring manager. Make sure they know you exist and what your special skills / unique selling point is.

Keep pushing.

Once you get a new job, repeat till you are at 100k

its very simple - but you need to do it.

Extra hints:
recognise you (as an HNer) have some valuable skills and need to fight the imposter syndrome. Start to collate the knowledge you have, in scripts, example apps etc.
4 things Search Engine look for on your website
Also, Podniesinski's own photographs of Fukushima: http://www.podniesinski.pl/portal/fukushima/
When you're earning $30,000 sure. Once you've achieved resonable success, you're likely to have serious diminishing returns on earnings without associated risks.

I'm at a good point in my career, whilst not impossible, I doubt there's a lot of growth without changing my lifestyle in a way that I believe would be for the worse.
Braid Code Cleanup (part 3)
I'm sad that anyone thinks this is hacking
> Surely you don't believe race is a strong predictor after controlling for all the hundred other things?

It can be if you select the right data, algorithms, and analysis method.

> Algorithms are not prejudiced

That's correct. However, the selection of algorithm and input data is heavily biased. You're acting like there is some sort of formula that is automagically available for any particular social question, with unbiased and error free input data. In reality, data is often biased and a proxy for prejudice.

> It still isn't treating a poor white person different than a poor black person.

I suggest spending a lot more time exploring how people actually use available tools. You seem aware of how humans bring biased judgment, but you are assuming that the creation of an algorithmic tool and use of that tool in practice will somehow be free of that same human bias? Adding a complex algorithm makes it easy to hide prejudice; it doesn't do much to eliminate prejudice.

> Its not treating the group of poor people unfairly.

Yes, it is. The entire point of this type of tool is to create a new way we can pre-judge someone based not on their individual behavior, but on a separate group of people that happens to share an arbitrary set of attributes and behaviors.

The problems of racism, sexism, and other types of prejudice don't go away when you target a more complicated set of people. You're still pre-judging people based on group association instead of treating them as an individual.
tbh at a glance this seems a tad bit intimidating to handle, but I certainly see a lot of possible benefit from this as well. I should defo take a look at "HTTP: The Definitive Guide". Also, what happened to [c] D:
But "crash" is also a perfectly good word; what's wrong with using that word instead, especially since some people don't like the word "accident?"
Is Docker ready for the Enterprise?
>Unfortunately the web development profession has decided to shoot itself in the face and make framework-oriented development mandatory

Frameworks are commonly used across many programming industries. It's also not any framework's fault that the PM (or you) chose the wrong framework.

>just don't expect to be able to get a job doing that and do expect to be mocked as some sort of luddite.

I've never heard anyone mocked as a luddite for using the simplest solution necessary to meet requirements, that sounds like something programmer's are complimented for (if they can show results). If you want a job where the employer uses a trendy framework... just learn the framework; it's either that or learn the company's hand-rolled framework, at least with a trendy framework you're also investing in potential future prospects.
Also available from Microsoft:
https://github.com/ReactWindows/react-native-windows

Seems to be only Windows 10 and xbox though.
Software security: Does quality provide a blueprint for change?
Nothing showing up on iOS. Is it missing some extensions?
Glad you liked the hack! With some bad stereo signals, I've found the audio dialog to be softer in one of the two channels, and the music in the other, so if you're watching that sort of film you might not get the best mix!
Algorithms _can_ be prejudiced. See [1]. Not being defined with bias or prejudice does not make them impervious to it.

If a dataset is biased, as you have stated by "not trusting judges" elsewhere, then the algorithm will follow that. If the dataset contains a feature that is highly indicative (be it racial information or otherwise), your model may come to depend entirely on it. The presence or absence of other data may be irrelevant, especially if you don't perform regularization or another similar tactic.

Racial (or specific feature) profiling is a very complex topic. If there's open legal questions as to whether policemen are allowed to use it, I don't feel algorithms should be allowed to.

[1]: "How big data is unfair: understanding unintended sources of unfairness in data driven decision making"[1], by Moritz Hardt, a Google machine learning researcher who has published on the topic - https://medium.com/@mrtz/how-big-data-is-unfair-9aa544d739de...
The actual statistic[1] says that the critical reason for the crash is attributed to the driver in 94% of cases. That does not tell you the percent of cases where the driver is doing anything riskier than "being human".

If you can find a source that talks directly about risky behavior, it would be appreciated.

[1] https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/...
I actually tried this initially, but unfortunately it did not work. And this way you got a (cool?) article out of it.
> In C++, the use of RAII means that exceptions can be made to free any dynamically allocated objects whose owners went out of scope as a result of the exception. In C, we don't easily have that option available to us, and those objects are just going to stay allocated.

In GCC and Clang, there is the "cleanup" attribute which runs a user-supplied function once a variable goes out of scope, so you can have scope-based destructors:

static void do_cleanup(char **str) {
free(*str);
}

void f(void) {
char *s __attribute__((__cleanup__(do_cleanup))) = malloc(20);
// s gets freed once the function exits
}
The Long and Epic Journey of LambdaCase (2012)
POKEMON GO DEATH?
It is kind of the general business attitude here, unfortunately.
QA Instability Implies Production Instability
> To be clear, yes

> (1 - 1) + (1 - 1) + ... != 0 + 0 + ... either

I don't see why. I understand the sets themselves are not equal, but the sum of the elements of those sets is at any given index.
Does it anything Slack doesnt? Except VOIP
And the happy conclusion: LambdaCase did go into GHC 7.6.1. https://downloads.haskell.org/~ghc/latest/docs/html/users_gu...
Why be sad? Define a "hack". I think this fits the bill, maybe you're thinking of "cracking" ? :)
Obvious fix: Count the length of the function without whitespace characters, so that both versions are equally slowed down by the optimization.

Unfortunately, this sounds like one of those problems where a non-fix like that is still the best you can really do. If nothing else, this should still be at least a more accurate representation of the complexity of the function.
It's mentioned in the wikipedia page under "further updates"

https://en.wikipedia.org/wiki/Dwarf_Fortress#Further_updates

Which refers to a brief mention here:

http://www.pcgamer.com/community-heroes-tarn-adams-for-dwarf...

but there are no details.
Knapsack multiple constraint
we are looking to apply a javascript/jquery algorithm for multiple constraint knsapsack for ecommerce project. any guidance where to source it is much appreciated - optimized, proven. thanks.
CGI prefixes environment variables with "HTTP_" (for HTTP headers), the problem is this prefix is not unique.