skysight-inc/HackerNews huggingface dataset:
This is exactly how I feel - SoundCloud is one of the best music services out there and I use it to discover the majority of the new artists and music that I enjoy these days. People are also posting awesome mixes and more lengthy content for free. Their mobile app is well thought out, too.

It would be sad to see an acquisition from Twitter, because I think they're going to make it whatever they think they need to compete, which will ruin what SoundCloud is now.
I use the hell out of that app. Thank you very much for making it.
> &utf8=✓

Ok, that got me to smile.
Having a low unemployment rate actually suggests it would be harder to hire a team there.

But on your bigger point, remember this guy was going to move to the US to do this work until he was told no by our government. I want him to work here instead of in Columbia because I care about the US economy and I want it to do well [1]. The question is really about whether this job in San Francisco should go to someone who was born in the US or elsewhere (with, like you said, everything else being equal). I find it really hard to have a pro-natural-born-American job bias when my (and I'm guessing your) ancestors also came here from other countries seeking work, and more generally, I just don't think foreigners are less deserving of good things than people who happen to have been born here. I guess you'd say that's not supporting my own countrymen, and if so, I'm OK with that.

[1] Wait, why do I care about the US economy more than the Colombian economy? I'm not sure, and I struggle with this. Selfishness, I suspect--I live in the US.
Report: Mars is Only Justification for Human Spaceflight Beyond Earth Orbit
Verizon threatens Netflix with legal action over network congestion alerts
#VISIONECTIDEA

I developed a Hospital bed booking system previously, but it did not work as it was tied to a pc (this was before the tablet). So I would like to pursue this idea with this dev kit.
I think the key term in your comment is "cryptographer". Not software engineer, but cryptographer. The actual encryption that goes on in openssl is very good, but the engineering which surrounds that cryptography - not so much.
Advantageous may be the fact that you can extend ElasticSearch with JavaScript, whereas I think as easy for someone who understands the Solr codebase, I've wanted to try that once, but I had to resort to doing the necessary computation in the language calling the Solr service.
Hopefully YouTube will follow the lead.
From a strategic perspective, I think paying off one of the ISPs in this case strengthens their case by showing that the problem is a shakedown for money. If they didn't pay up and the issue was never fixed then the ISPs could attempt to play it off as some larger-than-money issue. They've proven the problem is greed.
Context - error message:

http://www.washingtonpost.com/blogs/the-switch/files/2014/06...
Solving Visual Feedback Problem: Interview with Anton Shevchenko from TrackDuck
Interestingly, generative art is 50 years old, maybe more! Check for example the work of Vera Molnar, creating generative art with science computers and tracers back in 1968: http://dam.org/artists/phase-one/vera-molnar/artworks-bodies...
The national museum of modern art in Paris actually has 8 piece of a similar later work from 1976 in its collection : http://www.centrepompidou.fr/cpv/ressource.action?param.id=F...
> The necessary change is simply this. Exchanges would have to set a price at which orders are to execute. Whenever there are excess orders in one direction or the other, that price would drift up or down, slowly, until the order executes.

How would this even work? Understanding Market micro structure is literally my day job and I'm having trouble parsing your proposal.

Consider the market where I want to buy at a limit of 9.90 and someone else wants to sell down to a limit of 10.00.

What price would the exchange set? People have already said the maximum the market will buy for is 9.9 and the minimum the market will sell for is 10.

if there is no overlap you just cant' trade no matter what the exchange does.
https://news.ycombinator.com/item?id=7853603
Meet Pepper, Aldebaran's New Personal Robot With an "Emotion Engine"
See, as a true HNer (heh..), I would like nothing more than believing that a high tech software operation that makes money and is run by nerds is a force for good.

However, I'm afraid your proof-by-analogy does not work. If you actually know what you are talking about, why not explain the current financial system clearer and with more information?

In turn I promise not to burden this discussion with a dissection of your analogy, or even my own set of analogies which would beautifully fit my current bias, and which you would surely reject outright.
Swift: Apple's next-generation programming language 4 years in the making
Discussion: https://news.ycombinator.com/item?id=7853603
> why are some people so insistent on buying milk right now

Because NOW is when we have the most actionable knowledge.

If you don't buy now, what if the price never goes back down? You missed a buying opportunity.
Streisand Effect.
I use that chair too (at home). Just about everyone who's visited and tried it said it was one of the most comfortable chairs they've used. Only disadvantage (for me at least) is that the arm rests aren't adjustable, but they are removable.
I can't reply to that thread (maybe it's because it was too long ago), but you draw a difference between someone moving a large block (as described in yummyfajitas' post), and someone trading a small size (50 shares). So let's say that someone does want to trade 50 shares, in your example, and breaks up their order into 2 25-share orders. At the point at which a 25-share order is executed on the market, the sheer size of the trade is not very much. It's not likely to signify a market move. At that time, nobody has knowledge that there is a second 25-share order heading to the second market. It is possible that an HFT player sees the first execution and takes out the shares at the second market, but with such a small execution, they are pretty much guaranteed to lose money.
Apologies for flagging it but it looked good enough that I thought some real damage might come of it. YC being implicated in a thing like that would have looked really bad.

You really shouldn't have used a real persons by-line there, that made it much more believable. Still, kudos for the prank, it was funny, especially the insane valuation.
It could be so that the ISP can't claim "if you had peered with us, we wouldn't be so congested" or some other BS.
Wow, what a stupid move on Verizon's part. I have to believe the Streisand effects will far and away outpace any remedial action they might try to achieve here. While I get that they are irritated by their customers calling them up knowing more about how broken their network is, than the tech answering the phone, but this is going to be the new reality. With Google, Netflix, and no doubt Amazon providing more information to their customers about exactly why their product is having issues.
Irresistible El Greco
What is the point of Verizon sending such a letter?

Do they think Netflix will comply? "Oh Jeez we hadn't thought this through but now with this letter and all, we understand! We'll just start blaming our own servers instead. Thanks."

Or is it simply a necessary step before they sue? But if they sue, isn't it likely they'll lose? (Sue over what anyway?)
In that context, what do you think about and where do you place the success of feminism?
> But if Snowden violated the Espionage Act, then didn't the small number of reporters he gave the NSA docs to? And the larger number of reporters who reproduced them? And anyone forwarding a Glenn Greenwald article with embedded PDFs? And sites like HN that "make available" classified documents by allowing links to the docs to be posted here?

Prosecutorial discretion is still a thing, even if "common sense" has disappeared.

Nor has competing interests gone away; there is a natural tension for the American government in maintaining freedom of the press while enforcing the law which would (and should!) act to make the question of suing the NYT, WaPo, etc. not as easy as you make it sound. But for Snowden there is no such dilemma. On the contrary, he even explicitly promised he would not do what he did, something the press has never guaranteed.

Either way, surely you're not trying to claim that there are not gradations in severity, or that the law (even as it stands today) should or does treat crimes apart from their severity. Even our drug laws, abusive as they are, understand the concept of possession of large amounts or small amounts of a given drug, severity categories, etc.

Hell, even murder and rape carry different charges for different levels of the crime, so I'm disappointed that you'd try to undermine the logic of a law against espionage by such shoddy reasoning.

If Carmen Ortiz declines to charge the HN webteam with espionage it says nothing about the logic of charging Snowden with the same.
Not so sure about "backwards compatibility" part.

From Protocol buffer python doc: https://developers.google.com/protocol-buffers/docs/pythontu...

"Required Is Forever You should be very careful about marking fields as required. If at some point you wish to stop writing or sending a required field, it will be problematic to change the field to an optional field – old readers will consider messages without this field to be incomplete and may reject or drop them unintentionally. You should consider writing application-specific custom validation routines for your buffers instead. Some engineers at Google have come to the conclusion that using required does more harm than good; they prefer to use only optional and repeated. However, this view is not universal."

So basically I will be in trouble if I decide to get rid of some fields which are not necessary, but somehow were defined as "required" in the past.

This will potentially result in bloated protobuf definitions that have a bunch of legacy fields.

I will stick to the JSON, thanks.
Your case shouldn't be generalized either. Strangely, I'm getting a lot of 404's when trying to find the actual stats on the Dept of Labor website.
Thanks for throwing the ageism in there. It's cool to judge people like that.
"Click here to show your interest in Google Fiber".
Andreesen and I have the same perspective that Snowden's leak was definitely not a "revelation." We both already assumed the NSA was spying because it's a spy organization. So, without any benefit, the only affect of Snowden's leaks are harmful to the US.

I took a venture capital class at Berkeley where I got to meet government groups from Russia, China, Poland (and a few others that escape me right now). They all shared a common goal of learning how Silicon Valley works so they can setup their own technology hubs in their home countries. Right now, Silicon Valley is a magnet for the best and the brightest in the world. Why wouldn't you be concerned that we're loosing that edge for no benefit?
I saw that our artists recently (or might've been longer ago that I knew) started using PSB files rather than PSD - Haven't checked on the actual differences.
I want to shed some light on this topic. As a former HFT quant, I find the general "Main Street" sentiment toward the profession to be misguided.

1. HFT does NOT take anything from most investors most of the time. Most investors trade on a much longer investment horizon than any HFT firm. If you are a normal investor, you can lump up most of HFTs into the same bucket as the exchange itself. Most of them engage in some combinations of (i) pure arbitrage (ii) very short-termed statistical arbitrage (iii) market-making based on (i) and (ii). None of this is really that relevant to most investors. The only time HFTs can screw over a lot of investors is when their software goes awry. But this is a risk that any computerized system has, high frequency or not. If there is a major bug in Chicago Mercantile Exchange's matching engines, that would be a total disaster.

2. HFT firms do have huge execution risks: if you are making a two-sided market, there is a chance you can get "swept", meaning when the value of the underlying moves faster than you can react, you get filled on one side of the order without a realistic chance of hedging for a profit. HFT firms do a ton of research into estimating their execution risks. (edit: This point is often glossed over, making HFTs look like this evil superpower group of nerds exploiting other investors. That's not the case)

3. Finally, most HFT traders don't go into the profession solely for the money, just like most people do not apply for YC solely for their passion. Most of my former coworkers weren't that greedy and led pretty modest lives despite making hundreds of thousands of dollars. For them, high frequency trading had a locally optimal balance of tackling intellectually challenging problems while getting paid handsomely.

I won't say HFT is the most valuable thing that its practitioners can be doing. I think the (trading) world would operate just fine without all these micro-second level transactions. But they are NOT the next subprime mortgage, and I just hope folks stop commenting on stuff they have no clue about.
The irony is they are likely using LayerVault's PSD.rb http://layervault.tumblr.com/post/56891876898/psd-rb
Came here to write this. Promise pipelining is an especially interesting attempt to solve latency in RPC (although it doesn't always work).
There is a (false) assumption among laypeople that limit orders "no longer work".

This (false) assumption is propagated regularly by articles and books wherein the same pattern repeats itself:

1. limit orders are defined

2. "... but on that morning Joe Trader was shocked to see that his limit orders weren't working!!"

3. description of Joe Trader NOT using limit orders ... or using them and canceling them and chasing prices ... or whatever.

I've seen this pattern in a lot of media since the Lewis book. In reality, limit orders haven't changed and you can set a limit and go to sleep / go on vacation, just like you always could.
sweet feature, stoked to start using it
You should also check out the excellent http://tosdr.org/ project.
Right after they launch their 64 CPU, 256 core ARM64 X-serves.
The 30-year mortgage is mostly a product of government. And in supply-constrained markets (most of the American coasts), low mortgage rates have mostly resulted in sharply higher-priced houses/land, which isn't good for anyone wanting to actually own a house. And that's one of the more benign results of mortgage securitization.
Missouri Principal Kevin Lowery finds way to thank God during graduation speech
I never thought of this, but it's quite genius when laid out this way.
Firstly, you don't have to experience something first hand to know about it. Secondly, my girlfriend is an immigrant, and she has no problems finding work. Her parents were immigrants too for that matter, and even owned their own business here before moving back to England.

So no, the system isn't broken.
Just make everything optional (like suggested) if you're worried about it.
Audio tweets?
Why bother? They already produce machine code.
Easy language interoperability as a reason to choose Protobuf over JSON ? Mainstream languages support both JSON and Protobuf equally well, and the others tend to support JSON more often than Protobuf.

Free backwards compatibility ? No. Numbered fields are a good thing, but they only help in the narrow situation where your "breaking change" consists in adding a new, optional piece of data (a situation that JSON handles as well). New required fields ? New representation of old data ? You'll need to write code to handle these cases anyway.

As for the other points, they are a matter of libraries (things that the Protobuf gems support and the JSON gems don't) instead of protocol --- the OCaml-JSON parser I use certainly has benefits #1 (schemas), #3 (less boilerplate) and #4 (validation) from the article.

There is, of course, the matter of bandwidth. I personally believe there are few cases where it is worth sacrificing human-readability over, especially for HTTP-based APIs, and especially for those that are accessed from a browser.

I would recommend gzipped msgpack as an alternative to JSON if reducing the memory footprint is what you want: encoding JSON as msgpack is trivial by design.
Looking at their language design – probably not.
Market makers are licensed by and incentivized by the exchange. They will usually have cheaper or no transaction costs, be given order priority over other market participants, have more relaxed rules on quote display times, or any other combination of advantages over all other market participants. In return they are required to take both sides of the market (eg: buy when everyone else is selling) and respond to a minimum percentage of quotes (eg: trade when no one else wants to). For the exchange the advantage is that they provide a minimum level of liquidity at all times which is what attracts traders to the exchange.
Verold
If you don't currently have protobuf definitions, you can just not use required fields in any new ones you write, like the quoted passage suggests.
> Schemas Are Awesome

No reason you can't implement schemas over JSON. In fact, you typically implicitly do - what your code is expecting to be present in the data structures deserialized from JSON.

> Backward Compatibility For Free

JSON is unversioned, so you can add and remove fields as you wish.

> Less Boilerplate Code

How much boilerplate is there in parsing JSON? I know in Python, it's:

structure = json.loads(json_string)

Now then, if you want to implement all kinds of type checking and field checking on the front end, you're always welcome to, but allowing "get attribute" exceptions to bubble up and signal a bad data structure have always appealed to me more. I'm writing in Python/Ruby/Javascript to avoid rigid datastructures and boilerplate in the first place most times.

[EDIT] And for languages where type safety is in place, the JSON libraries frequently allow you to pre-define the data structure which the JSON will attempt to parse into, giving type safety & a well define schema for very little additional overhead as well.

> Validations and Extensibility

Same as previous comment about type checking, etc.

> Easy Language Interoperability

Even easier: JSON!

And you don't have to learn yet another DSL, and compile those down into lots of boilerplate!

I'm not trying to say that you shouldn't use Protocol Buffers if its a good fit for your software, but this list is a bit anemic on real reasons to use them, particularly for dynamically typed languages.
Yeah, I considered throwing a bunch of CYA verbiage but then opted for succinctness.
Until the law firm responsible for their client getting Streisanded suffers significant and public repercussions for doing so, they'll continue to advise this kind of action because billable hours.
Mirror neurons are essential, but not in the way you think
This is a non-criticism. Just use optional for everything, or make sure that all your clients and servers have upgraded. If you had a JSON library that supported required semantics, you'd have exactly the same issue on your hands.
HFT is completely distinct from front-running.[1][2] Front-running means that you (as an investment bank or other trading company) buy and sell stocks according to the orders you have received, but not yet executed from your clients (usually large institutional investors). HFT just means that you are quickly executing trades based on some algorithm(s).

[1] http://en.wikipedia.org/wiki/High-frequency_trading

[2] http://en.wikipedia.org/wiki/Front_running
In the case that he cited, that is why the named defendant was acquitted and sent back to Mexico. They didn't have a case that stood up in court.
Ray Kurzweil: “Get ready for hybrid thinking” TED Talk 2014
Looks like Swift will be open source from a few tweets. I imagined as much with Apple's work on LLVM. Though the big issue is like Objective-C, it's near worthless without Cocoa and all the stuff Apple keeps closed.

https://twitter.com/mxweas/status/474581160454942721
Verizon fios customer here. There has been a noticeable drop in the quality of streams in the past couple of months. The picture went from excellent > barely functional(after the FCC ruling) > watchable(after the peering agreement) still not great. Kudos to Netflix.
Listen to his statement again. He believes that foreign governments -- who already knew about US spy operations -- are using Snowden's leaks as political cover to enact protectionist policies. After all, every other wold power engages in exactly the same type of behavior. But, without a Snowden of their own, they don't have the PR problem that the US does.
Netflix is angry because Verizon isn't giving Netflix the bandwidth that Netflix paid for[0]. Netflix should ignore this C&D on free speech grounds, and tell Verizon to get lost, because corporations are people[0] and have free speech.

[0] I wish I was joking about that.
The biggest thing HFT provides: liquidity
Here is how to do it in .NET: http://stackoverflow.com/questions/3087595/values-of-local-v...

Figured it out a few years ago. Sadly requires binary rewriting...
What do they mean WiFi won't work? How is that anything other than a blatant lie?

Reminds me of the late 90's when my ISP told me I couldn't get cable Internet because I didn't have a 486. I lied and told them I did to have the modem sent to me to hook up myself. It's a computer network, once it's in my house I can expose it as I like.
Maybe Verizon would prefer the more accurate "Verizon is deliberately slowing down your Netflix experience."
One thing that bothers me is when a commit has multiple changes that aren't related. A commit message will say "Implemented feature X", and that's true, but it's also making a small change to feature Y, which isn't mentioned in the commit message. It makes reading the diff harder because you have extra noise in there and it also makes it harder to answer the question of "Huh? Where did this small change to feature Y come from?".
It all depends on how they can mine the data. Metadata is hugely valuable, and you can probably infer why people would potentially would want to encrypt based on who the parties are.
Reasons not to use protocol buffers (in C++ at least):

1) Doesn't support Visual Studio 2013.
2) Doesn't support Mac OS X Mavericks.
3) No "nice" support C++11 (i.e. move constructors)

(These can be at least partly solved by running off svn head, but that doesn't seem like a good idea for a product one wants to be stable)

With JSON I can be sure there will be many libraries which will work on whatever system I use.
I noticed that Youtube performance went up around the time the peering agreement happened.
Clearly they are just preparing ground for possible future legal actions against Netflix. I don't think on their sane minds that Netflix would ever comply to that.
I am the guy behind swiftlang.eu and I can pledge that there will be no nazi jokes ever. Why are you hating so much? I want to encourage devs like we all are to get into a new and promising programming language and help people share their knowledge. That's why I built a platform to make the devs community grow. I used the Swift logo, which you can see everywhere in the Internets, but hopefully it's not a crime. Please be more positive to the new bottom-up initiative, because it's always better to do something useful than to do nothing. Thanks!
Thinking about this more, it's not even that he hired a team abroad. They're friends, you can tell, and sometimes friendship knows no bounds. Or maybe he has some affinity with Columbians and specifically wants to help out the local people; that's honorable too.

My issue is how the article's framed, like it's somehow America's fault! I don't buy it!
Yes, that's what I just said. If OpenBSD hadn't included exploit mitigation, it wouldn't have not worked, and we wouldn't be here today.