skysight-inc/HackerNews huggingface dataset:
And in the US we're finding the same percentages as older workers replace younger workers in jobs like food services that traditionally employed younger kids.

We also have lots of stories of H1-B's replacing workers even in the youthful age brackets. That's the sort of thing that seniority rules also prevent.

It ain't unions causing the problems.

You would do well to cogitate on the real causes instead of just swallowing the anti-union propaganda.
Our service Wit.ai (YC W14) does just that.

Demo: https://labs.wit.ai/demo/index.html
Monoliths used to have specalists, people who know intricacies of cloud deployment, experts in db query tuning ect.

What happens to these people when ppl move to mircoservices. Now we have bunch of devs who are expected to be jack of all trades doing everything sub optimally .

I've seen some places move all database experts to 'db as service' team, but this arrangement is awkward at best and have strange organizational and management issues that were not present in monolith style development
I wanted to see if there was good speech recognition and could Google about Nuance... Now that its going to be "disrupted" I found out about it.. ironic.

Try Googling "speech recognition api"...
Yes - I was visiting India last year and used Uber (ubiquitous and cheap in major cities there) and noticed that the drivers had trouble finding me. One or two of them told me that they tried to call my number (a US number on T-Mo) and their plan didn't allow it.
> But if you really care about people who depend on you including them, it's obvious some measures must be taken to create a safe environment for the underrepresented.

Please be specific: how is Yarvin's presence making you unsafe? Are you concerned he'll physically attack you, or insult you personally or as a member of a group? If not, you have no reason to feel unsafe.

(And if you feel unsafe anyway and believe that's a reason to ostracize him, well, I have bad news: your viewpoints make me feel unsafe. So sounds like you're not going to be attending, either.)
I set the background colour in our team's shared iTerm config. Green for CI, blue for the test server, yellow for staging, and we don't have access to production!
PHP has had an extension module repository since 1999
Another explanation for the flourishing of these one function modules may be the fact that some people feel a kind of high/achievement from being able to say they have a published module out there. A sort of bragging rights if you will.
The GP is already using AWS, and successfully restored the system through AWS snapshots. In this case, that third-party with administrative control saved the day.
Tree shaking.
wholesale open sourcing of code from companies going out of business may be one such example of a circular tech economy
Obviously it's not possible to pick a sample size large enough to eliminate all bias. However it's important to pick a sample that doesn't inherently bias the effect that is being measured. This has to apply to both the original and the replication.

The response to the paper points out few examples where the replication was not judicious in picking a sample that minimized its influence on the measured effect. Even besides that, the original study had sampling and scoring procedures which contradicted its original aims.

Lastly, sensationalist headlines of "more than half of all papers are not replicable" are blatantly wrong and not what the original paper even states.

As to your point, I agree that only being able to replicate in one sample type is grounds for skepticism, but more replications have to be done to ensure the replication sample is not the one that is flawed. One can't really draw conclusions unless the replication is repeated a large number of times across a wider sample space.

Link to response paper in case anyone's interested: http://projects.iq.harvard.edu/files/psychology-replications...
There are definitely trade-offs involved when making decisions to inline vs import.

Strictly speaking, you're definitely right. Each dependency is an additional point of failure, but so is each additional line of code you inline.

The benefits of these small modules is that they're very thoroughly tested by the entire community. I'd say for most cases, they will be much more robust than any solution an individual developer can spontaneously whip up.

Of course, these modules don't exist in a vacuum, and infrastructure failures such as this one do pose another point of failure you wouldn't have with inlining code, but I think in this particular case it had more to do with the failure of npm to adhere to package management best practices to not include an unpublish feature.
A discussion about the breaking of the Internet - Kik on NPM events
Revenue is earning.

If you earn 200k a year, it doesn't mean you saved 200k.
The Battle for Picasso’s Multi-Billion-Dollar Empire – Vanity Fair
Considering the fact that Excel had to run on multiple versions of Windows and also run on the Apple Mac I can understand why they would hate hidden dependencies.

I've experienced the joy of trying to make sure Win32 code runs on Windows 3.11 (with Win32s), Windows 95, Windows 98, Windows Me, NT, 2000 and XP.

Generally it all works, but sure enough there are times when a small code change breaks one or more of those platforms.

Luckily these days things are much better as Win32 is a lot more consistent.
Deep learning solution for netflix prize
Show HN: Server Implementation for the Redis RESP Protocol
Doesn't work like that. They want to use a J28D engine modified for super sonic flight. That engine was designed to power MD80's.
Telegram has a great reply feature so you can respond to someone's message and give your comment some reference when there are either a few conversations happening at the same time or if you haven't been on in a while and want to comment on a message that was a bit back in the dialog.
The Amazing APL line editor (7.5 mins)
I don't entirely disagree, and I think this to be a quite helpful response to the poster, which was the point of suggesting your previous answer was just being flip.

Company to company the specifics certainly don't hold constant but one could argue that the progression from junior to senior involves more responsibility, autonomy, and accountability at most places.
> You have no understanding of the first amendment. It applies, of course, only to the government's response to speech.

Darn it, I thought we were going to get all the way through this discussion without someone wheeling out that old nag.

Once again: Attempting to ban people from unrelated fora based on their political views is not against the letter of the First Amendment to do this. But attempting to ban people from unrelated fora based on their political views is quite certainly against the spirit of the First Amendment.
With the advent of ES6 modules's selective imports and tree-shaking, that's definitely quickly becoming a better approach. With the old CommonJS modules, you need to be concerned about overall code size, which is where small, single purpose modules excel, and why this approach has proliferated to this degree.
> the really alarming events are more to do with having data you shouldn't have rather than not having data you should

the really really alarming events are more to do with your users having data they shouldn't!
Ask HN: I would love to be part of a founding team
Since YC application deadline is coming up and interviews soon as well, thought this might be a good time to get the attention of those up-and-coming startups. Maybe this could be a good thread (for companies) to pick up your employee #1 and #2. And for folks like me (no solid team/co-founders and no big idea at the moment but dying to work on cool stuff and be part of the founding team) and I am sure a bunch of others, this could be a great way to join the rocket ride!

As for my background, I have 15+ years of experience in Search and am in SF Bay area. Please let me know if you would like to chat with me and I can share you my resume and all details. Would love to meet up with as many fun startups / founders as I can (even if not anything else). Thanks.

PS 1: Wow, creating throwaway id in HN is very easy. No email needed or confirmation link needed. Kudos!

PS 2: What a pain it is go through the CAPTCHA - I am human! And it took me 20+ tries to get it right and that is only after I gave up on the damn images and resorted to audio. Boo!
You'd have a good point, if all of those tiny but probably useful modules were given the use you're describing.

Discoverability though is so poor that most of those modules are most likely just used by the author and the author's co-workers.

If a typical npm user writes hundreds of packages, how the hell am I supposed to make use of them, when I can't even find them? Npm's search is horrendous, and is far from useful when trying to get to "the best/most supported module that does X" (assuming that random programmers rely on popularity to make their choice, which in itself is another problem...).
This is it! Thank you!
Minimesos-spin up Mesos clusters in seconds on development laptop
Also no one uses it
If I were the heads of EU countries, and this actually happened (after the already huge refugee crisis happened and keeps on happening), I would be extremely pissed off at the US for creating this problem for Europe in the first place - if not in public, at least in backrooms.
I think it'd be great if there was a way to create different branches for a topic within a chat. Take that as you will and use your imagination.
Obama Has Gotten 3,000+ Tweets about Encryption. Let’s Double That
Reflecting on it, what I think I find most attractive about RStudio is two things:

1) the IDE like environment. Although I do a lot of work "literate document" style, there's a very fluid relationship between the one-off / throw away code that ends up in those documents and the code that ends up becoming reusable. RStudio puts the interactive environment into my hands but gives me tabs with full documents to work with so that I can take those ad hoc bits of code and seamlessly move them into reusable scripts, or even fully structured libraries and program code. Conversely, any piece of code in those scripts or libraries is trivial to throw back into my interactive console to use ad hoc as well. This fluid workflow perfectly matches my development style: starts with experiments to figure out how to do things which is very ad hoc, gradually matures and eventually ends up being a static solid thing that I want to capture as a reusable component. With Beaker and Jupyter I feel like I am always stuck in "throw away code" mode, and there's a high friction to move code between the two paradigms.

2) The plot display seems to work a lot better. With both Beaker and jupyter I find the inline plots are too static - always the wrong size or the wrong shape, etc. In RStudio I can drag and resize that window independently.

I feel bad because I'm not telling you solutions and I don't really have any - but these are the things I love about RStudio. Of course, the downside of RStudio is ... R.
I have no problem running my own mail server, I meant a platform to record, track, stats etc emails.
Apple might want to talk to IBM about OpenPOWER. The POWER8 chips and chipsets lack known internal micro controllers that have their own flash unlike Intel's chips that have the Intel management engine. Consequently, there is nothing there to flash with malware. Also, all of the system firmware is open source. That is the motivation behind the Talos workstation board, provided that they get enough interest for an initial run:

https://raptorengineeringinc.com/TALOS/prerelease.php

If Apple is concerned about tampering enroute, they could have the flash chips for the system firmware provided separately by a trusted party and transported like a bank shipment. Then flash and install them at the datacenter. That should thwart adversaries who cannot do their own manufacturing runs of modified versions of the chips, which is just about everyone. I guess the manufacturer/fabrication plant could do a custom compromised chip, but given that the costs involved are prohibitive, I doubt that would happen.

Apple could do the same with the firmware and flash for every other component in their datacenter that has a microprocessor such as the hard drives, the NICs, etcetera. They are large enough that part manufacturers would likely turn over the source code for their firmware in order to secure their business along with anything else that they need/want.
Ahhh job security :D
asm.js is proof that a compile-to-JS language doesn't necessarily have to discard the correctness of its number types. A statically typed language can do a lot. Integer values can be can to int32 via `| 0`, longs can be emulated with two numbers (GWT does this).

The tradeoff is speed, especially for dynamically typed languages. Having to check your operand types in JS before doing work is a performance killer.
One thought on talking about the weather: this habit arose when everyone's livelihood was directly or indirectly tied to local rainfall--so it was more like discussing the latest macroeconomic news or stock tips or latest web trends (in tech) than some pointlessly superficial conversation.
Ahh job security :D
I'm not sure dead code elimination works in that situation. Consider:

var obj = {
a: ...
b: ...
c: ...
}

If a, b, and c are functions, there is not necessarily a way to determine at compile time whether they will be used at runtime.

var prop = webrequest();
obj[prop]();

In that scenario, a, b, and c cannot be eliminated. But it would be worth testing Google Closure Compiler to see what it does in what scenarios.

I've heard ES6 modules solve this problem, but it seems like dynamic access to an ES6 module might still be possible, which would cause the same problems for DCE. Perhaps no one writes code that way, so it doesn't necessarily matter. But what about eval?

There are lots of tricky corner cases. It seems better to use small atoms than a monolithic package.
NPM modules can be used on browsers. On browsers, space is a premium.

Why would you want to install a 500kb dependency that has only one function you need, when you can install a 10kb dependency that has it?

Would you want each of your five 20kb dependencies to re-implement the same 5kb function, increasing the code you must send to the client by 20%, or would it be more optimal for each of those dependency to use the same 5kb function?

The author rants about practices of developers from different programming environment, without experience, without figuring how things came to be. If he did give an effort to think from the perspective from Node.JS developers he’d have addressed the previous two points.

This is like going to a friend’s house and complaining everything is put in the wrong place. It would have been wise to immerse in Node.JS conventions and observe for a while before making comment.

EDIT: Reply to scrollaway:

I've also understated the problem.

Let's look at the problem in the current Node.js environment, it's not uncommon for a web app to have 20 dependencies, each of those have 10, and each of those 10 have 5. That's a total of 20 times 10 times 5 = 1000 dependencies in total.

Let's say you were to remove a 10 line library function that's "standard library-like", used by 15% of those dependencies, and have each of the existing dependencies re-implement that in each of those dependencies that uses it.

15% times 1000 times 10 lines is 1500 lines of code.

So if you're going to troll a solid argument by nitpicking, do it properly and get the details right.
Hm. I'll take a look at Prezto then. For me a new shell takes approx .5 seconds and tab completion is instant, but I'm on a 2014 MacBook Pro and use iTerm2 instead of the native terminal (not sure if that makes any difference). I don't recall it being any worse on the 2012 MacBook Air + iTerm2 I had previously, but maybe I just didn't know any better.
>
I think it's likely they would have kept the code that valgrind didn't like if it was not a violation of the C standard. I don't understand why you completely reject that as a possibility.

It's highly unlikely that the maintainer of OpenSSL at Debian is a spec lawyer. The maintainer ran Valgrind because, as a general principle, reading undefined memory is bad. That is independent of whether the C standard says that it's OK. If I were the maintainer of the package in question, I would not ignore reads of undefined memory just because the C committee has declared that it has some kind of behavior. That would be silly.

Valgrind contains many tools that check for things that are not violations of the C standard: for example, memcheck checks for "fishy" arguments to malloc that are not C standard violations but are nevertheless usually bugs.

> Compilers may not turn functions that hit most kinds of UB into { return; }, but they can. As a general category, that's a bad thing.

Depends on the undefined behavior. For undefined behavior coming from the C preprocessor, sure, that shouldn't be undefined, and the committee should change the spec. For other kinds of UB, if compiler authors hadn't figured out those tricks, we'd have slower programs today. Undefined behavior is much of what has allowed performance of our programs to keep improving despite the language not changing over decades.
again pre-dating the strategy.

YC has been actively seeking to grow as fast as it could since 2009-2010, and was funding over 70 companies in a batch as early as 2012, then they scaled back in 2013 after experiencing growing pains.

Plenty of well-known companies have come through in that time eg, Pebble, Stripe, Firebase, Parse, Crowdtilt, Coinbase, Instacart.

Cruise went through YC in 2014, after the time you (inaccurately) assert was the beginning of the "growth strategy".

BTW when Criuse first hit HN, commenters were generally nonplussed or critical [1], just as they had been with Justin.tv (some dude with a camera on his head??) and then Twitch (watching other people play video games??).

From the dude with a camera on his head to Twitch's $1Bn exit took 8 years, and even at year 7 people didn't think it was a winner [2].

So, go easy on the new guys hey? :)

[1] https://news.ycombinator.com/item?id=7933045

[2] http://justinkan.com/the-99-percent
No. You just need a Chinese bank card. Though some services do require a Chinese ID number. But pay/send money in WeChat that's all that is needed. China Merchant Bank is the easiest to deal with: English online banking and their mobile app, while Chinese only, is pretty easy to use without knowing Chinese.
On iOS Keychain works relatively well for Safari, but needs to be explicitely supported for native apps, which means basically never.

Also as far as I know there's no first party app to directly view your keychain items in iOS, which makes it useless when the domain detection fails (it's the most painful when the same service has two clearly different domains for desktop web and mobile web, which is a pretty common case)

I use keychain but end up duplicating a lot of entries in a Lastpast like app just to cover these cases.
No saner alternative presented.
This thread is so long that I may be repeating what has already said, but ...

I converted to Linux from Windows about a year ago. An unexpected but great benefit is that I have been able to pull PCs 5 to 10 years old out of my garage and now they run like brand-new. I should be good for a while.
A discussion about the breaking of the Internet, by Head of Messenger @ Kik
What is a scotchman? My best guess is somebody made of sticky tape
Have you been so diagnosed by a specialist? If not, in your place I would visit a psychiatrist and a sleep doctor.
I... can't parse that sentence.
KiK's Side of the breaking-the-internet story
There is a recording available as well: https://www.youtube.com/watch?v=98LdFA-_zfA
Riiiight. Because cryptography is identical to an 12-line string padding function.
Yeah but at least they're FINALLY getting rid of add-ons in Firefox.

Priorities, you know.
> Now people will start wondering if a module with millions of installs in the last month is still going to exist tomorrow.

That's a good thing. People should be aware of it - and be aware of the fact that all awesomeness of the open source world is maintained by continuous - and often unseen and unpraised - effort of thousands of people. Who are mostly known when something breaks but not much otherwise. It's ok not to think about it every minute, but it's also useful not to forget about it completely - and that we shouldn't take it for granted as it is in no way law of the universe, it is a consequence of continued effort and continued good will.
Fair enough. I had an employer many years ago (~12) who insisted in spite of my objections that all of our servers be accessible via ssh (as root! On port 22!) with a shared, 7 character password on the public internet. Worst of all it was an (very small, working with other small businesses) IT consulting company, and my boss insisted on the same thing for client servers.

Needless to say, a number of boxes, both our own and belonging to our clients) ended up as C&C machines for various botnets and I learned a very valuable lesson about how to treat a machine serving ssh to the public internet (namely: don't listen to a boss who doesn't know wtf they're talking about with regards to security, don't allow password ssh logins _ever_, for fuck's sake don't serve ssh to the public internet if you don't absolutely have to, and bloody hell denyhosts!).

The headaches of dealing with pwned machines that were critical to the business in question while I was being paid 30k/year very much colored my opinion of how to handle ssh.

Obviously I quit that job as soon as I had a credible alternative and was able to double my salary twice in two years (amazing what you can do once you know what you're actually worth on the market).

I'm primarily a developer now, but do share some infrastructure management responsibility at the small (9 person) startup where I work now. Aws and opsworks has enabled us to run without a dedicated ops team, and I'm the most security paranoid person on the engineering team.
dang - I am fine with deletion.
> Seems to me that there's a big difference now, in that even limited as it is, current AI advances are finding many important practical uses.

Big difference? Do you seriously think that the entire field of artificial intelligence research produced nothing usable until today? For as long as there were AI algorithms there were also attempts to commercialize them (with varying success). The problem wasn't that all of those algorithms turned out to be useless, but rather the mismatch between hype and reality.

You should look into the history of expert systems for a classic example. With things being as they are, deep neural networks might very well go though the same cycle, which is not a good thing for the AI field in the long run.

Caution and skepticism are not the enemies of research and engineering. Hype is.
I'm not going to deal with the paywall, but is the "higher tax bill" the result of "actually paying taxes on your income"? If so, I'm not sympathetic.
Bash to audit your npm dependencies
> (it can include such a dist file for some people to use, but the npm package shouldn't export that)

I think that is exactly what the article is suggesting we do.