skysight-inc/HackerNews huggingface dataset:
More than getting a specific job, I'm insterested in gaining some perspective on the types of roles I might be suited for (Still internship material? Some intermediate position?) and what I should expect in return from a quality employer.

Beyond casting a wide net and 'shopping around', I'd like to learn from others' experiences.
How I Came to Write D
> With JITs you get devirtualization as well, so no need for vtables.

That's what I referred to with "inline caches". The problem is that for Ruby you need fully polymorphic inline caches, with guards all over the place, because unless you do tons of analysis upfront, you will have problems knowing whether or not the world has totally changed on you after any method call, and almost anything is a method call. (call into code you have not verified can't possibly call "eval", and you might find that adding two integers afterwards does in fact not add them, but returns a string and changes global variables, and what-not)

The upshot, is that compared to vtables, you're not actually saving all that much. E.g., take "1 + 2 - 3". You could inline Fixnum#+ (and could reasonably do so with an AOT compiler too). But you need to add a type guard before the inlined fragment to verify that Fixnum#+ still is the Fixnum#+ you inlined, which at the minimum costs you a comparison and a branch or you need to record every call-site with inlined code and be prepared to overwrite it with fixups if the implementation changes.

And if Fixnum#+ has been overridden, or the Fixnum#+ implementation has method calls, chances are you will need another guard before "-" too, because you might not even know for sure whether or not the object returned from "1 + 2" will be a Fixnum, so you might find that the inlined method suddenly is for the wrong class.

I'm planning on benchmarking inline caching for my compiler against vtables, but absent evidence to the contrary I'm expecting that there will be a very substantial number of cases where the complexity isn't worth it, or where they might even turn out to be slower.

> Something possible in AOT as well to certain extent, but it requires a mix of profile guided optimizations coupled with whole programm analysis.

It does if you want to do everything upfront, but you can pull things into inline caches with a mostly-AOT compiler relatively easily with just a little bit of extra information, and a few guards thrown in to do some basic tracing.
He was involved in Mozilla from the beginning. My gut tells me he did what he thought was right to allow Mozilla to move forward once he realized the bad PR was not going away no matter how hard he tried to fix or assure folks they had nothing to worry about. Obviously this is conjecture on my part.
Heartbleed vs malloc.conf
All it can do is take away what could have been a potential customer.

You don't want every customer you can get.
> will ever be made

And yet they've been made in the past. It doesn't require any hard forking or incompatible changes, just some additional messages which can be ignored by old implementations. The Bitcoin community has made one soft forking protocol change per year for several years and will almost certantly make one and possibly more this year.

> Cryptocurrencies are not sets of abstract ideas, they are protocols that are implemented in code today and have to be judged on their merits as they actually are.

As I noted, Ethereum doesn't implement this yet, if you'd implemented and worked out the gnarly engineering issues in actually implementing it I'd have credited you for that.

But right now, it's just an idea. One which is equally applicable to Bitcoin and which was described by the Bitcoin as an ecosystem improvement for Bitcoin years ago. And not just as armwaving, I at least went as far as enumerating the things we'd need to do before I got mired in the problem of how do you make it not an extreme risk in the face of alt implementations— something which isn't solved even absent almost-never-executed anti-fraud code paths. It'll be super awesome to see you implement it, if you do.

But it's hard to respect your good work when it results in a lot of people being misinformed about advantages because you've been sloppy about talking about the attribution. The end result of these is that you produce armys of technically unsophisticated people who believe that it's the gospel truth that Bitcoin can't do this.
An estimated 50% of desktop PCs in China are still running Windows XP; so that seems reasonable.
What are you talking about? I've read lots of articles on HN with those items on the front page.
The data being read is the plaintext password being sent from the client. The standard login procedure goes like this:

1.) Client sends Plain text user/pass over SSL -> 2.) Server reads that info to memory -> 3.) Server hashes password and tests hash -> 4.) Server discards plaintext memory.

Whats happening here with heartbleed, is you are reading the RAM of the server, so before Yahoo even has the chance to hash the password, this exploit allows you to read the password.

Remember, even though Yahoo may only store the hashes in the database, your password (for any service) is still being sent effectively as cleartext.
Poachbox – Recruit Startup and Tech Talent
I agree. What John's describing as the web is more like the Internet. The "web" is Tim Berners-Lee's "World Wide Web" (ie. hyperlinked documents rendered in a web browser).
A 128bit address space would be fun. Of course as the page mentions, if you want to use IPv6 for this, you actually want something more like a 196bit address space or just round it up to a 256bit address space.

Imagine all the world's computers running in a single unified address space. All network access is abstracted away, loading a resource is as simple as loading a memory address.

It would be like a new golden era for C! Rather than using URIs or some sort of XML addressing schema or whatever else people decide to invent, instead, all the world's information and knowledge from all around the world (solar system, universe?) is available through one unified address space.

Although I imagine we'd still need some sort of DNS system running on top. ;)
I would think that when they discover a superpower they compartmentalize that information.

You could make the inference that, if they did have it, they were not making broad use of it.
Exposing NSDictionary
What, you mean like this?

https://gist.github.com/hlein/10121981

What, praytell, is a script kiddie going to do with that, other than oogle at the word "vulnerable"?
I think the more important point to discuss is the trend of our "smart devices", specifically wearables. The software is becoming increasingly coupled with the hardware. Think about that for a second. Web languages have evolved within the browser. That is their native environment. What happens when the browser does not exist on a future device?
Twitter Ads: My Experiment and the Results
>US does not have anywhere near that many air to air missiles

That is true, however the US also possesses a large number of anti-aircraft guns, with plenty of bullets. :-)
The biggest feature at launch was the idea of "unlimited" storage (I think at the time it was 1GB) This was a huge departure from the existing Yahoo!/Hotmail models which had much more restrictive limits on storage.

That and the idea of one inbox and no folders. The concept of letting your mail flow into one box and not "filing" it was also a big change from the existing mindset.
Is that number from ls(1) or from du(1)?
netflix.com is another big one
Hi, do you accept H1 Transfer??
Is organic better for your health? A look at milk, meat, eggs, produce and fish
A spinal cord stimulator was suggested to me several years ago to help treat the neuropathic pain [1] associated with my (complete) spinal cord injury. I'm currently trialing Prialt [2] for this, but if it doesn't work (or the side-effects are too nasty) I might pursue the stimulator.

[1] http://en.wikipedia.org/wiki/Neuropathic_pain
[2] http://en.wikipedia.org/wiki/Ziconotide
The story of Dune, recreated with Gummi worms
Maybe we'll get a retro look. Say, the X windowing system in the 90ies... like Motif:

https://en.wikipedia.org/wiki/File:Plan_Open_Motif_screensho...

http://qt-project.org/doc/qt-4.8/images/qmotifstyle.png
There seems to be some confusion about the vulnerability on the client side, which I think should be clarified. The Heartbleed vulnerability seems to only affect OpenSSL clients and servers. The buffer overrun is only known to be in OpenSSL, so other SSL clients should be unaffected.

Client web browsers are not affected because:

Firefox uses NSS on all platforms.

Chrome uses NSS on Linux or platform libraries for SSL or uses NSS on all platforms for SSL, and then uses the system libraries for other cryptographic operations and certificate validation.

Platform-specific browsers (IE, Safari) likely use their platform's SSL code.

Almost every other mainstream browser is a derivative of one of the four mentioned so far.

Edit: As another commenter pointed out, client-side consumers of the OpenSSL library are likely affected as well. That means web spiders and server-side code that uses web APIs are likely affected. That may or may not be concerning, depending on the networks that traffic travels over and the method of authentication.
Nice and sensible.
What are you talking about?

The information I wrote is FROM the man page.
Why though? I'm of the opinion that the error should be handled at the place that produces the first NULL/None. Objects should be valid.
Thanks! We're using binary websockets to route the actual video frames. There's also an instance of haproxy sitting in front of everything. But our server is still choking every one in a while, heh.
Is there a separated-concern library suitable for large applications that'd fare better for 2048?
Looking at the kickstarter, there's something I think is missing. There's no point of reference for the thing's scale - I have absolutely no idea how big it is. Could you guys add a photo to make it clear?

EDIT: Thanks for the banana, that's a bit clearer. Though bananas have various sizes ;)
In this attack, data from the server process's address space is sent back to a malicious client.

Yahoo hopefully/presumably store only password hashes at rest, but just as in almost any system the user's real, clear password has to be sent from the user to the server to hash and verify against the database in order for the user to log in. Yahoo were following best practices by sending this password encrypted over HTTPS, but this vulnerability is a particularly insidious one because it actually punishes sites for doing the right thing in the form of encrypting traffic.

Because of the particular memory read using this attack and the memory layout Yahoo's service ended up with, other users' decrypted login traffic would get sent back to malicious clients with high frequency.
There's nothing to get, the hate is completely irrational. Those who belittle shared hosting, or the idea of cPanel have their head so far up their own tech-infused ass that they don't understand most people, hell even most techies don't want to manage their own web or email server.
Ask HN: Is Heartbleed a bug or a backdoor?
SmartAsset (YC S12) is hiring full-stack developers in NYC
The passwords did not come from the database (which should only have hashes stored) but from the http request send by the client during login (originally this was transmitted encrypted but leaked out due to the bug).
[Show NH] Weekly set of stackoverflow questions/answers in pdf
Angular.js, golang and Javascript - in pdf - https://github.com/Chemical-Web/stackoverflow-cookbooks/tree/master/output
Examples of a semantic interface, or changes that a "normal" person would make to their hosting that cPanel doesn't allow would be good to illustrate your point.
I feel like the more Apple is losing relevancy and market share, the stupider Gruber gets, in his quest to defend anything Apple does.

Saying Apple banning Bitcoin is fine, because Bitcoin will do well in other places anyway, is like saying banning freedom of speech in Turkey is fine, because freedom of speech is doing well in US.
Good call, adding that to the FAQ now. It's 12" tall and 3.25" in diameter.
Good point. Many (or most?) people do not understand the wide range of disability associated with SCI. No two injuries are alike.
The copyright and contact fields are usually the only ones not empty. The rest are pretty much irrelevant except to the magical thinking crowd. (Those are the people who believe that a particular camera, lens, or aperture/shutter/ISO combination will result in the "same" picture or the "same" image quality. For the most part, the fact that the photographer happened to be holding a D4, a 1DX or an 80-MP Phase One at the time doesn't mean the shot would have been substantially different - at web sizes, at least - from what an entry-level DSLR/MILC or even a decent point-and-shoot would have rendered.) Where provenance matters (particularly in things like the WPPA "Photojournalism" competition division) only the raw file counts. When the piece is part of a tutorial or "how I shot it", the actually relevant and helpful data appears separately as body text with an explanation.
Similarly, there are Japanese companies who have monetized a service designed to alleviate such problems.

http://www.japantoday.com/category/kuchikomi/view/business-c...
Web Apps in absolutely no way means 'requires an internet connection to function'
I found this comment very helpful. I'm still confused about how the nebulous term "consultant" is used generally, but at least in the (developer-specific) HN universe I understand it to mean something like "software developer who is paid as a contractor, with some claim to a specific expertise". For the record, this is not at all obvious to outsiders.
https://www.propublica.org/article/nsa-says-it-cant-search-o...
Check the feed. Banana for scale :)
> as countless third parties are granted remote access to corporate systems.

> 23 percent — of breaches were attributable to third-party negligence.

23 percent of countless is > infinity.

Leaving yourself exposed from third party equipment connected inside your firewall is your own negligence.
Download more RAM to make your computer faster
Agreed. I have a somewhat concrete example, the US credit card system. We know that GCHQ, and probably the NSA, knew about public-key encryption a long time before it was reinvented. Therefore, the US credit card system could have been made quite secure, instead of the amalgam of cheapest-to-implement patches that it is today. Very probably, the NSA could have prevented the largest part of "identity theft".

I guess we also have to ask ourselves if this was deliberate on their part, or did they just miss the emergence of the credit-card-as-electronic-money?
Good Eggs Software Development Manifesto
I have read about that but it doesn't seem to work for me ? I still get dozens of old conversations as unread whenever i log onto skype on my phone.
Can I ask why you agreed to spend "most of a work day" on a "sample"? I have heard others saying they spent a "few" hours on a technical test but I think most of a work day triggers alarms for me.
Depends on the app. Multiply larger size x1000s of images, x1000s of visitors, x days. For offsite backups, 2x the storage cost. My general rule is, any image over 40k is too big for a web page, unless your website is about photography/high-resolution imagery. And I hate jaggies and compression artifacts as much as anybody ;-)
Chicago Mercantile Exchange trading halts due to "technical issue."
Appeals Court Rules for Amazon in Rovi Patent Case (paywall)
My only knowledge of inches is from subway, but 12" means the length of a footlong sub, so I have a better sense of scale now :)
How is it that Google and Hotmail were not vulnerable? Were they using their own implementations of SSL? I would have figured Google would make use of OpenSSL.
HN punishes (punished?) the ranking of articles with those keywords very heavily.
"over a decade", heh - I was one 30 years ago.
Imagine this for our brains...
Do you feel the same about Windows?
Huh? The web is exactly what you are talking about. Google and Bing are things. Search on the web works and it's not very hard to get a decently ranking page on them.
"Every penny you save before you're 30 has a dramatically large impact on your quality of life after 60."

Either you're getting a much higher rate of return than the rest of us, or you're awfully excited about maybe 5 cents.

Or you're just being hyperbolic.
> Which in turn encourages people to abuse the operators...

In practice, very few languages have suffered problems from operator overloading. I can't think of another language where this is a problem (other than C++), which makes me think it's a cultural/code style problem, rather than a problem with the language itself. C++ seems to encourage abuse because everyone learns its IO library, and its IO has an API design so horrible it should make you retch.

By comparison, I'm not sure that adding more operators makes the resulting code any more palatable. Look at Haskell: libraries define their own operators, and the operators in Haskell have a steep learning curve. Can you tell me, without looking at a chart, whether $ or >>= has higher precedence, and what kind of associativity they have?
U+2297 CIRCLED TIMES is already the logarithm operator in APL, so you'd want to avoid that confusion. Phew!
Design can vary in terms of how "good" it is but even eras like art-deco will go through periods where it resonates more strongly with people. The factors for that can be any multitude of things.

Even using Steve Jobs as an example doesn't work. The design of the iPod/iPhone has changed drastically in just 10 years. I don't consider my 2nd generation iPod as "timeless". I can admit that it was great 10 years ago but today it's not so much.

That being said I do believe there's elements of science in design. The golden ratio perhaps or using concentric circles. It seems plausible that those could be less taxing on our vision to look at.

I don't know if that applies to flat design though.
He addressed this. It's not just HTTP, it's the inclusion of web views of browser content and linking between apps that makes something webby as opposed to just an internet-enabled app.
Maybe make it: theshirtcutts.com ?
> it does not go into any detailed analysis as to where that balance should lie

That's very much part of the point. From the article:

Without strict visual requirements associated with flat design, post flat offers designers tons of variety to explore new aesthetics – informed by the best qualities of skeuomorphic and flat design.
Atlassian is an anomaly amongst anomalies, but the timing is pretty normal. I find it strange that there is some kind of apparent value judgement being made on one company vs another.

The average time to an enterprise exit is 9.5 years according to http://pando.com/2013/05/21/memo-to-this-years-yc-class-its-.... So Atlassian is generally in line with the average. Talk to any person or VC that has built a large SAAS company and they will likely say the same thing.

Would every company love to grow >40% annually with spending 0% on sales and 15% on marketing...of course! The reality is that most companies can't do that. You can't look at it and say "I want to be Atlassian not Box." Box has a growth rate of over 100%, so commands a gigantic valuation. If I were starting a business I'd take either unicorn.
Both GMail and FastMail have had this vulnerability in the past. GMail had it when script was hidden inside SVGs. FastMail had it when script was embedded in attachment filenames. I'm sure lots of other webmail systems had/have these issues too.
"It also doesn't apply 100% of the time. Does anything?"

Yes. Either this maxim applies 100% of the time, or there is some other statement that does.
Styling a '70s-Inspired Look
What waste of resources? HFT revenues were estimated at 1B for last year. That's nothing in the grand scheme of things.
If some company could have built 10x better transistors than the competition they could have made billions, if not tens of billions. Yet no company did this. The simplest explanation is that it wasn't possible.
I'm not sure how exactly to quantify this, but I think it might be interesting to figure out what groups the NSA does NOT appear to report on.
Don't want to be that guy but 4-5 years for enterprise startups "to get to this point" which I'm assuming is either that market cap size or IPO is ambitious - Enterprise startups tend to take a while to get that flywheel spinning. The fact that Salesforce did it in 5 years (Founded: 1999, IPO: 2004) means that they are more the anomalie than the others. For example here's a list of Enterprise companies which have taken 7-13 years to get to IPO:

Eloqua - Founded: 1999, IPO: 2012. Years to IPO: 13

Qualys - Founded: 1999, IPO: 2012. Years to IPO: 13

Rally Software - Founded: 2001, IPO: 2013. Years to IPO: 12

E2open - Founded: 2000, IPO: 2012. Years to IPO: 12

Exact Target - Founded: 2000, IPO 2012. Years to IPO: 12

Box (Summer IPO) - Founded: 2005, IPO: 2014. Years to IPO: 9

Demandware - Founded: 2004, IPO: 2012. Years to IPO: 8

Fleetmatics - Founded: 2004, IPO: 2012. Years to IPO: 8

ServiceNow - Founded: 2004, IPO: 2012. Years to IPO: 8

Bazaarvoice - Founded: 2005, IPO: 2013. Years to IPO - 7

Workday - Founded: 2005, IPO: 2012. Years to IPO: 7

Marin Software - Founded: 2006, IPO: 2013. Years to IPO: 7

Marketo - Founded: 2006, IPO: 2013. Years to IPO: 7
Desktops do need better power infrastructure, though something like a NUC could be powered by a small solar panel. A Rpi or ARM-based chromebox is even lighter on the power needs. Haswell (or ARM) based laptops can do 10 hours on a charge and wouldn't even need a consistent power supply.

Not sure what you mean by connectivity -- desktops and mobile devices have the same options: wireless (3/4G, etc), and wired (via wifi for the mobiles). A desktop surely doesn't require buildout of a infrastructure-heavy wired network to have comparable connectivity to a smartphone.
"Bayesian flamewar detector"

Is that a Bayesian detector of flamewars, or a detector of Bayesian flamewars?
I know/have-worked-with too many MDs to believe that they are also hackers.

I am contending that the hacker is the missing part here.
gp said "intentionally"
How long is "a long time"? GCHQ had RSA a few years before RSA invented it. (About 3 years according to WP).

The story of it is interesting: Clifford Cocks was working on it, he went home, and had the realisation at home. He could not write it down because that's not what mathematician spies do, so he had to remember it overnight u til he went back to the office the next morning.
tl;dr

Milk: Organic milk has higher omega-3 fat levels, but probably not enough to make a difference. Exposure to pesticides, contaminants or hormones is not a significant risk in either organic or conventional milk.

Produce: While there may be no significant nutritional difference between organic and conventional produce, organic does have lower levels of pesticide residue. However, there isn’t universal agreement on the risk those residues pose.

Meat: There doesn’t seem to be much difference, health-wise, between organic or conventional meats. Grass-fed beef has a slight edge over grain-fed because of higher omega-3 levels, but the amounts are probably too small to affect human health.

Eggs: There are no significant differences affecting health between organic and conventional eggs.

Fish: There’s not enough research comparing organic and conventional fish to draw any conclusions about their health benefits.