skysight-inc/HackerNews huggingface dataset:
I've only seen one thing actually use it in Go:

func Polar(x complex128) (r, θ float64) {
return Abs(x), Phase(x)
}

It seems to be good for documentation reasons.
Cap'n Proto (Protobuf Replacement)
SEEKING FREELANCER (remote)

I need a Lua developer or someone with similar experience (Ruby, Python, etc.) who wants to pick it up as they go.

I have an almost-completed Adobe Lightroom Plugin that I need completed. The SDK uses Lua. After that, I have a second plugin I need developed (likely more of a fork of the first).

Email is in my profile.
Just to echo Brad from the tech side specifically - HN has been a tremendous source of help, advice, network and everything. It really has made much of what we built possible in that I cannot imagine doing this without HN and the people we have met here.

From having Jedburg reach out when I had some foolish question about high-concurrency applications, to the number of folks who helped us trouble shoot a burgeoning Mongoid/Ruby memory problem at the very beginning - Thanks a million!
>Why not use Ruby, or Python, or JavaScript -- or even Go, Rust, Clojure, or Scala? (Yes, I realize that the latter two run on the JVM, which would have been problematic in other ways.) Heck, they could have bought RubyMotion and made Ruby the high-level language of choice for development.

Because OBVIOUSLY none of them solve the problems they wanted to solve (interoperabillity with Objective-C, fast, native, IDE integration, etc. Including RubyMotion which is a half-arsed implementation.
Scratching the beta of OS X Yosemite
There is a convention of providing concise documentation of options in `<command> --help` and more verbose documentation of options in the man page. When you look through a variety of common tools' documentation, you will notice that there are conventions that could almost be called a standard. But when you look carefully, you will find minor but important differences in how various tools write the options documentation -- enough to inhibit parsing it automatically.
Not sure the date. I first noticed the change back in April, when I was profiling some code. Ask vegorov: http://mrale.ph/blog/2012/09/23/grokking-v8-closures-for-fun... .
Haskell is an interesting playground for this since it tries so hard to make "pure" practical. Interestingly, they achieve this to a large degree using monads. I think that idea is fairly generalizable, though, that pure formalisms can embed impure ones as models and then have those be executed by an RTS.
Did you really link to material on an ad company's website in order to provide evidence that advertisements are effective? Would you expect anything other than "ads are useful and effective" from an ad company?

More importantly when OP said the slogans were annoying/disgusting, it was a statement of OP's personal opinion. OP never said in general the public finds these slogans disgusting/annoying.
Yet another special Apple-only lockin mechanism.
Or Scala worksheets in Eclipse, or any Lisp implementation.
Isn't Microsoft just supporting them to counter Google? I read somewhere (I have tried to find it again but I have failed so far) that Bing's cost of operation per search query was more than ten times that of Google.

I understand that DDG does not have to fulfill every Google use case. However, I don't see it likely that they're going to be number one any time soon. There are multiple discussions on HN where people say that if you can't be number one, you must shut down and walk away (I think we said something similar about Spring pad). Here we are encouraging DDG even though we know it will likely not be number one.

I am confused.
I'm not actually familiar with the context in which this checklist was originally written. But I really love it for two reasons:

First, it demonstrates how programming languages have been making the same tradeoffs for years, to the point that someone was able to make a checklist of what's wrong with any programming language that still works years later.

Second, you can fill this out for any of the big programming languages and many will do very badly. It shows how whether a programming language succeeds is unrelated to how good it is. An actually accurate checklist would have one item:

You're programming language will succeed because:

[X] It is tied to a popular platform.
African programmer here, and left the country I was born in decades ago to find somewhere that had a demand for my skills.

You'll find there's a direct correlation between available jobs for a career and people qualified or qualifying for that career that remain there. The only places in Sub-Saharan Africa that need programmers are of the scale where they have a regional head office elsewhere in the region (ie. South Africa, where they centralise support services like IT, development, analysis etc.)

Combined with the fact that the power houses of development in Africa are about as immigration friendly to other Africans as some of them would have been to people by virtue skin colour not so long ago. To clarify, "African from a poor African nation" is the new black in South Africa/Namibia/Botswana I can't speak for anywhere in Central or Northern Africa as I've not tried them.
I think this is worth hammering home.

People want analytics information, and the only way we can do this now is by adding things like this. (Not strictly true, but ease of deployment, etc).

Unless you shut down the only way to do something, the people who want this service will work around whatever restrictions have been put in place, and the solution we get will probably be even uglier.

The real way to get rid of this is to provide a mechanism that addresses everyone's desires.
From post down the page by tekp2 - https://news.ycombinator.com/item?id=7836326

http://phenomena.nationalgeographic.com/2014/06/02/why-have-...

"But Lazo thinks that neither the archival analysis nor the psychological experiments support the team’s conclusions. For a start, they analysed hurricane data from 1950, but hurricanes all had female names at first. They only started getting male names on alternate years in 1979. This matters because hurricanes have also, on average, been getting less deadly over time. “It could be that more people die in female-named hurricanes, simply because more people died in hurricanes on average before they started getting male names,” says Lazo.

Jung’s team tried to address this problem by separately analysing the data for hurricanes before and after 1979. They claim that the findings “directionally replicated those in the full dataset” but that’s a bit of a fudge. The fact is they couldn’t find a significant link between the femininity of a hurricane’s name and the damage it caused for either the pre-1979 set or the post-1979 one (and a “marginally significant interaction” of p=0.073 doesn’t really count [this is a link in the actual article - http://mchankins.wordpress.com/2013/04/21/still-not-signific... ]). The team argues that splitting the data meant there weren’t enough hurricanes in each subset to provide enough statistical power. But that only means we can’t rule out a connection between gender and damage; we can’t soundly confirm one either."
This is an honest question: Why do you seem to care so much? Rust is in my view a great project, that yes isn't quite there yet but is making great progress. I'm looking forward to using it when it is stable, and pcwalton and the other contributors are developers that I've looked up to for a number of years: I have nothing but faith in them.

At the end of the day, if Rust fails, well that will be a shame. But I'm seeing nothing that shows that it might, so I'm truly struggling to understand why you seem so upset by a new modern language trying to tackle big problems in ways that have never been done before. That's a good thing, as far as I'm concerned.
But you can't replace the GPU and Apple has full source code to the driver stack (and probably wrote most of it themselves instead of using the source from ImgTec).
I think it has.

Visually, the contrast is worse now than it was before. While this may be "trendy", it does harm usability.

The default coloring of the old results page was much easier to look at, as well. It made it easier to differentiate between the different types of content.

The fixed red bar at the top is distracting and pointless.

The auto-suggest is also wasteful and unnecessary. I find it contrary to the simplicity that DDG used to offer.

Yes, they're relatively minor changes, but they add up to result in an experience that just isn't as good as the previous experience. These types of minor, but harmful, changes can build upon one another over time, amplifying their negative effect.
> If you flip a coin a thousand times and it always comes up heads, it's fairly safe to assume it will come up heads the thousandth and one time.

Unless you have reason to believe that it's a fair coin.
The Case of the Evil WinMain
We already have run-anywhere applications. They are called web applications. I don't see how Apple might improve something here. I can start creating email in GMail on iPhone and continue to edit it on PC and many other web apps have similar functionality.
Quick guide to creating a OpenStack bootable image
Mountain View stuck in past when it comes to housing policy
Why Coffeescript
Disgust includes a "feeling of strong disapproval". I didn't physically throw up reading them, but I did read out a couple aloud in the office and scoffed. They're so smug and grandiose that it's very off-putting and I wish they'd just let the product speak for itself. (I use an iPhone, iPad and MBP.)
Yeah, in general, the contextual bandit approach seems to be a better strategy.
It's possible that not giving hurricanes easily-recognizable names would cause even less preparedness and risk estimation.
Well, I think the concept is to force you to write documentation by holding your code hostage. :)
I've used two different washer dryer combos.

Never again. It's terrible at both tasks, is ridiculously slow and never dries things completely

There is a reason the inside of washers and dryers look different
My hat is off to you gentlemen. Such civility. Good day to you Sirs. Good day.
I can't imagine in what situation using XMPP could be construed as "profitable". Maybe for paying Google Apps users, but I don't think too many of them depended on XMPP integration (either they have their own enterprise chat solution or they're just using Google's. Or they're not allowed chat)

What would be the revenue source there?
Especially in an era with Touch ID. My kid should unlock it and see their apps and not go about accidentally deleting mine. I should unlock and have access to mine, private email and so on.

Of course, with the new family features, they want you to have a device each rather than share. Wasteful but drives up their earnings.
They used to offer free student developer memberships, but I think they stopped that a while back. Now you have to be part of one of the paid programs (or be part of a university that's signed up with Apple).

It is pretty disappointing that Apple is walling in Swift like this. I was excited about it to begin with, because it looks like a great language, but apparently as Microsoft moves toward openness, Apple is doing the opposite. Now I'm not really sure what to do with it.
Can you post a screenshot? Really love to see what a designer can do with Openbox.
Awesome, I must have missed this, thanks for the link!
Indeed, I never thought I'd be authoring a post like this, but I really think dating is one area where Facebook holds a monopoly like grip
One other point, probably unrelated, but definitely relevant to me:

Being a geek, it's hard to live somewhere where hardware, a dead hard drive for example, costs several months salary to replace. Especially when the environment (heat & frequent loss of power) is conducive to dying hardware :)
I'm having a hard time understanding why she let herself get into debt and complain about it. 1st she could have gone to community college for 2 years and transferred to a 4 year school. Also, living at home would have saved her a lot. There are other option she should have done if too much debt was a problem for her.
If I decide today that I'm going to stop working and do something without an income I need to be ready to finance it somehow, debt or saving. That's reality!

On the other hand, the full college experience is something that nothing can replace but you got to understand that it going to cost. This was choice. The reality is that without debt she would have not gotten a chance to go to school. She should look at the bright side. She got what she wanted and in time she will be done with the debt but she will always be a CPA.
Now I wish I knew of a tool to filter out HN comments older than x hours.
How we're on the verge of an amazing new open web
> Meaning that if this dubious research is accurate, they saved lives.

That doesn't necessarily follow. It could be that people have on average a fixed amount of "preparedness" per unit time that they will spend on various events as they see fit. Switching from all female names to half female half male might have simply caused more of this preparedness to be spent on the half named after males, but the total amount of preparedness would be unchanged.
That's the normal use case for QoS 1 and 2 messages: the client must acknowledge each received message otherwise the server will try to resend it. From the MQTT V3.1 Protocol Spec: http://public.dhe.ibm.com/software/dw/webservices/ws-mqtt/mq...

What you don't want to do is read everything offered into memory faster than you can write it to disk / database. You could potentially fill the memory until you run out and crash. Instead control the flow by not reading until you are finished with the previous message (or better, allow N unacknowledged messages to be read, where N is just enough so that the application is as fast as it can be).
Sure, if you read through the entire diff it's a lot noisier, but it's still one commit.
> But that's a very important use case.

For Rust. I didn't make the comparison to Rust, I merely was intrigued by the choice of features and in which order to defend the comparison made by someone else. I see Rust and Swift as targeting entirely different things, at least at first (which means that Swift can certainly evolve inline assembly if it is so needed), and any comparison at this stage is pointless.

> It's all over the place in the Linux kernel.

Cool, that's one piece of software. I'll save you the next few: drivers and a couple files in a game engine. You're disputing my point how, exactly?
You mean that DDG offers the illusion of privacy, right? It's more than a little naive to think that the NSA won't be able to pull data without needing the cooperation of DDG (and they're obviously not dissuaded from doing so by any laws). We also don't know about any secret court orders that may or may not have been issued to DDG compelling them to turn over data. And how are we supposed to know that DDG haven't done a deal with Microsoft to pass on data under threat of being closed down, or even that they follow their stated privacy policy?

I'm not suggesting that any of these scenarios have necessarily taken place, but we'd have no way of knowing if they have. Also, the more popular DDG becomes, the more tempting a target it becomes to the NSA et al.

So by all means use DDG if you like its other features, but try to be realistic about privacy.
Cool! Will share this to my son coz he loves trains..
Wait. Why is that bad?
WWDC 2014 live feature voting site
Vote you favourite features and see the others live votes. Powered by meteor.js and Microscope.
I get the link-rot concern (and 7 re-directs as showcased in the FA is absurd) but these are services are mostly used on twitter and social media where the life-span of a post sharing a link is hours to a day or so, at most.
You are not alone but you are probably in the minority.

(quick edit: You saw a lot of Apple news because the WWDC keynote was today)
I wouldn't be surprised if Apple ends up open sourcing Swift after it cleans it up, perhaps even making it an LLVM project. I see it similarly to how they handled their own AArch64 backend -- proprietary at first, but mostly for secrecy before it was announced and then merging it with the preexisting backend after it was announced.
I'm thinking about starting the "Rust contributor points out how Rust is a systems language and $language is an applications language" drinking game. At least now they'll focus on Swift instead of Go. I don't mean this to be rude; I've just noticed a similar set of usernames in threads about certain !Rust languages playing the underdog position and always feeling like they need to compare.

Given Rust's PR, speaking of that -- not a thread about Go passes without at least three pcwalton comments these days -- I actually broke down and gave it a try. I wrote a little Hello World server and then got lambasted by a friend of mine for not working functionally, since, in his words, "Rust is a functional language and the fact that it supports other paradigms is a mistake." I rm -rf'd and ignore it for now, but I look forward to it stabilizing and maybe coming back to it.

Rust has potential but the PR needs to ease up just a little. There is room for more than one language in the world.
Tell the FCC to save net neutrality before it's too late.
Tried http://macruby.org/ ?
Yeah ... after I posted I did a bit of mental math and decided those "tens of thousands" could push "hundreds of thousands". Not a bad outcome!
Having been in industry for a long time, I think that something like Rust would be hugely beneficial. It very well could solve some very real problems.

I bring this up again and again because I'd rather not see Rust fail. I'd much rather see a slightly flawed Rust that's actually usable in the short term, rather than a continually changing Rust that nobody will seriously adopt.

Rust has been in development for years now. That's a very long time in the software industry. A few years of development time without a stable release is understandable. But it's getting beyond that now.

Rust isn't quite there yet, but each day it edges closer to a Perl 6 type of disaster. Perl 6 offered some intriguing ideas, but it just isn't usable, and that's a shame. Meanwhile, other competitors have arisen and blown past it, rendering it far less useful were it ever properly implemented.

Given the increasingly stiff competition that Rust is facing, I suspect we'll see it end up like Haskell or D. Something usable is eventually produced, but it never sees the truly widespread adoption that it could have seen, had it been usable earlier on. It's not as bad as Perl 6's situation, but it is still unfortunate.
Thank you, kindly.
ALWAYS wondered this...
Why do we have to wait with submitting apps that uses Swift until fall when Swift works with iOS 6 and iOS 7?
How much cleaning up do you expect at this point? It's already both announced and released to developers. Obviously it's not 100% finished, but if they intended to open-source it, I wouldn't expect that announcement to come after publicly releasing it.
I agree, it seems to be heavily influenced by C#. I am primarily a C# dev and reading through the code and docs I seem to have no mental friction, as opposed to ObjC which seemed to make me bang my head on my desk.
Apple needs you to know that it offers every service Google does – only better.
I think any attempt to precisely pin down where a particular language feature has come from or where a language draws inspiration from is pretty futile.

Many language constructs were invented simultaneously under different names in different languages.
I find it hard to believe a "stand-up comic, writer and director from Astoria, NY" that "hangs out" in the night scene has not met friends that will sleep with him just for the sake of giving him some experience -- out of philo-love motivation, because having spent a fair bit of time in the area, there are quite a few people who would feel sleeping with a friend in this need is just the right thing to do.
Increase the performance of your Redshift queries
How is Swift safer than Obj-C?

I'm not sarcastic or anything by the way, I just don't understand yet the foundation behind that statement.
Crucial's MX100 solid-state drive reviewed
I don't know that there is much question of replacing Rust when it isn't in use except as an unstable experiment with a lot of interest. You could replace Rust with outright vaporware.
EAT Club -- Palo Alto, CA -- San Francisco -- Bay Area

We're hiring: DevOps, Full-Stack Engineers, Front-end devs

EAT Club currently delivers lunch to thousands of hungry employees at startups and other tech companies in Silicon Valley and San Francisco, and we're ready to grow!

We're different than any food delivery or catering service you know. We work with employers, and give their employees a custom menu daily, via the web and mobile, from several great restaurants in the area. Each employee has control of what they order, and when. Employes get their customized lunch with their name on it delivered fresh and ready to eat.

There is a lot of technology, order forecasting, and service ops, to make all of this happen. This is where you come in.

You'll get the chance to work on:

Delivering personalized dish recommendations
Food discovery engine
Demand forecasting
Real-time delivery tracking

What we're looking for:

B.S. in Computer Science or equivalent
HTML/CSS/Javascript including a framework such as BackboneJS
Familiarity with Python/Django or enthusiasm to learn
SQL/Memcached/Redis
Knowledge of building reliable scalable systems
Comfortable using a shell/linux environment
Love of food

Bonuses:

AWS knowledge (EC2/S3/RDS)
Good UI/UX/design sense
Competitive compensation + free meals + endless stream of food samples

To apply, please send your resume/github/dribbble/linkedin to engjobs@myeatclub.com
Full-time, no remote

http://www.myeatclub.com/careers
Plus 'metric' must only accompany 'shitload' or other potty-mouthed quantifiers. Troll fail
It's feminism's fault that this guy couldn't think of a coherent way to blame feminism for this. Ever notice how "mean" is an anagram for "a men" (an abbreviation for "all men")? After all, they don't call it the "womean". Therefore, statistics have a misandrist bias. #notallmean
> one of the obnoxious things Apple has done recently

AirDrop pre-iOS8 (iCloud Drive, Extensibility) would have been almost totally useless or at minimum required developers to waste time supporting a temporary solution.
What have you been pointing out for so long? That Rust is unstable? That many people/companies won't use Rust while it is unstable? That there are other languages people can use instead?

All of those are highly uncontroversial and universally acknowledged by experienced Rust users.

Also, I don't understand how you have lept from Rust being unstable now, to Rust never being stable.

A 1.0 release by the end of the year doesn't seem at all unreasonable to me; I think you are expecting more from it than what the Rust team is looking for (and have stated publicly repeatedly): stabilising the core language.

Of course, a stable release of that form will still mean some libraries may be unstable (and so that Rust would be unsuitable for many corporate developments). These libraries will be stabilised progressively and iteratively.
I think it's been mine, but I don't have the monies to have gone to fancy hotels all over the world.

Where all have you found the expensive hotels to consistently have free wifi?
> you can't replace the GPU

You can't replace the GPU on any current Mac either.

> Apple has full source code to the driver stack (and probably wrote most of it themselves

That's pure speculation, and I doubt it.
Cool use of Microscope! :)