skysight-inc/HackerNews huggingface dataset:
Saturn's Children, by the same author, also has people as corporations. Said people are all robots, though, because humanity has become extinct.
Sounds good enough to me. +1.
Yeah, that’s a good way to look at it.

Now only if my medical premium would decrease like how some car insurance companies reward customers for good driving.
Half of it certainly does not look like a U

That depends on your handwriting and/or typeface.
I'm cofounder of Scripted.com and we're probably subledger's first major integration. We did it because we didn't want to put an engineering FTE on dealing with money in our app. Timing was good so we went for it! And I'm glad we did. All told I think we deleted some 9,000 lines of code.

Great team but integration needs some work. I'm sure they'll get there and I'm glad we could be the guinea pigs. Go ahead, AMA!
Ask HN: What are your opinions on domain hacks like ViewSto.re or affordabl.es?
Are there any studies done that show if visitors trust or distrust domains without .coms?

All the .coms are taken for a domain I want but the domain hack version of it is available.
I haven't used d3 but I used chart.js a little while ago. At the time is was relatively simple but lacking some features (like support for interactions). Looks like this newest version has added some of that which is great. My guess is that it's still lighter-weight & simpler than d3 which makes it good for some use cases but not others.

Edit: I've only had good experiences with chart.js (not sure if that was clear)
I'll try to respond to the points you've made here and upthread.

I posted the article because it surprised me. Also, of all the classic components of HN, history is by far the least represented. HN needs more high-quality historical articles.

Is this article high-quality? I take it you don't think so, but it seems to me as good a bit of intellectual history as we can hope for from major media these days. It manages to be serious, not overly tendentious, and packed full of information. To pick just one example, the fact that Bentham's writings on sex were kept out of Bentham scholarship as late as the 1960s is remarkable. So I'd say the article easily clears the bar for a good HN post. It's also news, of a sort—a pretty dramatic revelation about a major thinker.

The thread went bonkers, but we should hesitate to overinterpret that. There's a lot of randomness, and the threads are sensitive to initial conditions. It's not hard to imagine a sensible discussion of this article on HN, though the dice came up snake eyes this time.

As for off-topicness, sorry to put this glibly, but yes: responding to something off-topic with something even more off-topic is certainly off-topic. Triply so when it's a fast track to a flamewar.

An on-topic discussion is typically about the specific content of the article—the things that make it stand out from other stories. Going on a tangent is fine if it's something surprising, i.e. if the tangent adds information, like this one did: https://news.ycombinator.com/item?id=7962077. But when a thread breaks away from the specific content of a story and makes a beeline for some generality, no information is added. The worst kind of beeline is the predictable ideological tangent. That's not only off-topic, but likely to fuel an agitated argument, and those are the lowest-quality discussions on HN.

So the rule of thumb for on-topicness on HN is something like this: story specifics good, predictable ideological tangents bad.
That’s interesting. Hopefully it doesn’t get abused too much.
So why not just use Haskell? Why didn't Haskell take over Go's niche?
So, years ago I felt trapped by the success I had built to that point. But I also felt that it was all meaningless and I wanted to something more important. I needed a mission.

I gave up everything to go pursue that goal. (It turned out that I was giving up much less than I had thought.) My new career didn't work out like I had hoped, but I was doing something that I felt was meaningful. I was about something.

I met my wife when I was about something. And she married me even though I was poor. But I was a hell of a lot happier and that was attractive.

I came back to tech but with a whole different outlook. What am I about now? I am a family guy, everything I do is for them. I don't think my adventures are over (sure hope not!) but they make even dealing with daily bullshit at work meaningful.

We are lucky that we can apply our field to other industries. We can choose nearly anything we want to go into. We have enormous privilege. Life is a fucking playground. Want to help cure cancer? I'm sure they need tech guys for something. Believe in libraries or helping poor or veteran's care or internet access for rural areas? It's a choose your own adventure game. Even those billionaires you mentioned didn't set out to make billions. They had a mission, computers in every home, connecting social graphs online, etc.

Finally, I would just say that those people that you feel are so shallow are probably trying to fill the same hole. They're not terrible people, they're just doing what they think will make them happy.

My email is in my profile if you want to chat. Just know that everything ends. Good things and especially bad things. This time you're going through will also end and something new will start.
Funny how Seattle was left out of the comparison to other PNW cities. I'm not surprised... Seattle's transportation situation is abysmal.
> Can you safely replay arbitrary C, C++, etc.? No, because side-effecting code could run at any time and occur in any context. So that is one problem that has to be solved first.

I spend my time solving this problem. You can do it with a programming model especially designed for it. Functional programming is not required, though can be convenient.

> Well, now for a distributed system, you need to make STM talk to STM. Make one module talk to another over a network, or a filesystem, or another database, or a client browser. Do you have STM working in the JavaScript running on client's machines? And even if you managed that feat, do you have end-to-end STM from your datastore to your client's actions?

STM is the wrong way of thinking about this problem, mainly because replay is not an intrinsic part of the paradigm (instead, users manage that themselves). Rather, go back further to Jefferson's virtual time/Time Warp system [1], which was designed specifically in the context of distributed systems.

[1] http://dl.acm.org/citation.cfm?id=3988

There are also many related systems like Concurrent Revisions, LVars, Bloom, and so on...
It looks like this version includes a chart legend for pie/doughnut charts! Unless I am very mistaken, the old version, which I am using in my latest product, did not :(.

Hooray chartjs people, I love your product :) -- it is definitely my favorite charting library :).

BTW, does anybody know of a charting library that will make nice 1D scatter plots? (Like this: http://i.stack.imgur.com/LGBAG.png).

These are very useful visualizations for event frequency, but I can't find any libraries that make them.
Yes, concurrent with a writer. If there is more than one writer, the writers must use a mutex, but the single writer and readers don't block each other. I updated the text to make it clear.
I've been working on something similar for teaching graphics programming to our undergrads. Uses esprima to parse the input JS and add some runtime error checking with line numbers, including unidentified variables and timeouts for loops:

http://www.cl.cam.ac.uk/~ls426/graphicstutor/
Because Go is pretty good at its niche, and it has a huge amount of corporate support (from Google), which can make even a mediocre language seem very attractive.
In Europe it's entirely feasible, if your whole goal is to more or less keep the same post-tax, post-welfare distribution of income. You just do away with the traditional combination of means tested welfare and means tested taxes, and replace it with means testing for the taxes only.

In the US that would also be possible, but the level of basic income you arrive at might be bloody low. I don't know the data. At least, you'd save on bureaucracy.
Reading this article and the HN comments made me realize, how people want to use the same language for everything. Unfortunately, this is not possible, since each language was design with certain use cases in mind. I too, am guilty of wanting a language to do everything, to be fast, memory efficient and also easy to program in.

Perhaps our ultimate quest in terms of designing languages is to design one smart enough that can be used to program toasters and clusters alike. Until then, we might as well use the right tool for the job.
Android Wear is for a mass market consumer products, it better have clear use cases and be embodied in devices that are affordable for millions of people.

Glass is a prototype that happens to be available to consumers. It's useful in giving one a chance to explore wh what a head mounted computer is like, in the same way that a Nokia 770 gave you a sense of what the smartphone world would be like a few years later.

That being said, Google ought to figure out and communicate what's next for Glass. Or end the experiment.
For robots, Haskell is not used directly, but can be used as a DSL to generate the appropriate C code. Here's one example: http://smaccmpilot.org/languages/index.html
36 is starting to show a lot of progress for the dedicated bus lanes and the train tracks which will eventually go to Longmont. It was always the plan that the south and airport would go first. The north is scheduled to be done in 2017 I believe.
Be the expert/guru/magician/cult-leader/rock-star and grow an audience through the power of 'cult of personality'.

Let's take an automotive analogy.

Supposing you wanted to have a Q+A site for people wanting to get the most out of their Model T Ford cars, get writing and become the authority on the subject. Don't shy away from injecting a bit of personality in there and use your superior web-saviness to get better SEO, page-load times, responsive-ness and so on than what others already writing on the subject can do. A simple blog will suffice for the purposes of getting initial interest.

After a while a regular audience will materialize and they will start talking to each other in the comments. Some might even start offering spare parts to one another, uploading pictures and posting links to videos. Ideally they are drawn to your site to see what you have to say this week however they stay for the comments.

For this automotive analogy you would probably want real world community things, e.g. meet ups, galleries, a way for people to enable film-makers to hire their Model T's, a supplier's directory, a 'wiki' and so on.

Once enough 'user generated content' arrives you can move the 'forum' (or whatever) to the homepage and relegate your original articles to some archive buried somewhere in the site. By now some users might have branched out from 'Model T' to things like 'Fordson Tractors' and make the site the place for discussing everything 'Fordson'.

The need being met might be people wanting to show off their cars to others that truly appreciate such things combined with a need for people to get specialist parts. This arrived at set of needs is very different to what the site started as, e.g. the best resource on the topic. A deliberate pivot is made and the original specialism broadened.

There are many sites that have grown with a variation of the above. Cult of personality works for many writers, rock stars, diet experts, politics pundits, celebrity bloggers and probably even z-grade porn stars. Assuming you are none of those things and don't have a fan club, just by writing stuff people enjoy reading you could create a name for yourself to be someone in your field. You could become the expert in Model T Ford cars, respected for that for people that care about that particular car. Clearly in this example the market is only so big so interest might not be exactly huge, however the principle is the same. Just serve a poorly served niche with something better and grow from there.
Depends on your particular value of "better." If you're optimizing for programmer time, writing a language in Go is not a bad tactic. You get out of having to write your own GC, you can incorporate a few nice concurrency features with little effort, and you still get pretty good performance. (Admittedly, far from the best performance, though.)
Not that they can easily solve this, but unless you live very close to a station or do the park n ride thing (no good if using for parties) - the southbound rails leave you in the middle of dark suburbia. So yes, you can skip out on a bit of driving down I-25. It's neat but I'd be surprised to hear that a significant percentage of the population is "well served".
Rust has `unsafe` blocks in which you're allowed to do all nasty hacks you want.

Rust actually isn't that complicated. Don't get discouraged by comparisons to Haskell — it's still a C-family language where you can play with pointers and mutable state.

To me Rust still feels like a "small" language (similar size as Go or ObjC, not even scratching complexity of C++). It's mostly just functions + structs + enums, but they're more flexible and can be combined to be more powerful than in C.
A company I used to work for allowed its staff 12 sick days per year. These were used as ad-hoc no-notice holiday days. That was sub-optimal for colleagues.

The company also introduced a rule that any sick days taken on a Monday; or on the day before / after a bank holiday weekend, would need a doctor's note. Legally self certification was all that should have been required. So, this required a visit to a doctor to get a note. Since, at the time, it was hard to get an appointment within that time frame the person would require extra time off to get the note. And by that time they were uealthy and just asking their GP to write a letter to say that they had been ill with some unspecified illness; which the GP would do for a £60 charge. So it didn't stop anyone abusing the sick leave system and increased costs dramatically and made people take even more time off.

That was a lousy place to work.
If you're making up imaginary partners to get someone to give you money when they wouldn't otherwise, you'd be committing fraud. If the investor found out, they could press criminal charges[1] or sue you to get their money back. (They'd be especially likely to do this if they lost money on your company.) Once the case ended up in court, you'd have no way out, since continuing to assert your lie would be perjury (a felony).

[1] https://en.wikipedia.org/wiki/Fraud#As_a_criminal_wrong
Many mutual funds actually bought shares of Facebook before the IPO: http://money.cnn.com/2012/05/18/markets/facebook-mutual-fund...
Ah cool, that's good to hear (so long as flows are sustainable, unlike some of our proposals for 'harnessing all that wasted water')
would you say that helping someone find what they want is a big part of it?

Absolutely - in fact, that's one of the few topics where pure coaching really can help, and it can usually be reached in 1-2 meetings (rather than signing up for a long course - see that first article for some lock-in rip offs).
Metro/ST isn't that bad, I take it rather than rent a car when in Seattle, but I don't venture out of the West Seattle-Seattle-Bellevue core where service is pretty good.
Type classes are so good at error messages that they were proposed as the solution to the error message mess in C++ in the form of Concepts.
Voice recognition software might be good enough to create the index.
>You get out of having to write your own GC

You also don't have the ability to write a GC-less language, because there is no practical way to write non-GCed Go code.

>you can incorporate a few nice concurrency features with little effort

You also can't implement any custom OS-level concurrency features.
People generally applaud things they already agree with, be it Jon Stewart's audience or Marc Andreessen's.
It's called Guaranteed Minimum Income, which is what this article was talking about, in contrast to Universal Basic Income.
Sure: your point feels right logically and politically, but in fact it doesn't quite work that way: for Latin script-based languages like Portuguese, non-ASCII letters are extensions (diacritics or liaisons) of the basic Latin alphabet that are often left out in informal writing (eg by grade students, when texting/chatting, or by "uneducated" speakers) when the context is clear and a romanized phonetic approximation is available. As a result, native speakers are well used to homonymy in daily use, even though it might appear quite confusing to a non-native.

So, in practice, ambiguities like the one you point out are more likely than not to be as constraining to Latin script-based programmers as common English homographs like "bank" do.
You can probably get pretty far with machine learning.
Yeah, I was particularly amused by OP's statement here.
"But, for systems programming, abstractions suck. [...] But for tools that only need to do one thing and do it extremely well, it's either that or C."

C and Go are just two particular piles of abstractions. The tools work better for some problems, but that's not because "abstractions suck" for those problems.
Whether or not you can scale across machines has nothing to do with the thread model you choose. It's just about whether or not your server is stateless across requests, but you can do that with both async and non-async servers.
A friend of mine swears by Swiftkey, too. They seem to have taken a turn for the evil on Android recently, though: still usable as ever, but bugging you every once in a while to try out new themes, or asking for overly broad permissions.
https://www.surveymonkey.com/s/7LK8Y9D
https://www.surveymonkey.com/s/7L9XB75
https://www.surveymonkey.com/s/7LX2YHN

http://brisbane.craigslist.com.au/res/4545319742.html
http://brisbane.craigslist.com.au/res/4545208580.html

https://www.surveymonkey.com/s/V69DRSN
https://www.surveymonkey.com/s/VZ2JNKY
http://www.surveymonkey.com/s/VS858TD
I don't want to apologize for the existing callback-oriented APIs, because I agree it's easy to create some pretty hard-to-follow code in them. But there's something to be said for using non-blocking I/O calls. Threads aren't free, and spinning up a lot of them can tax system resources and impede performance. Allowing a number of execution contexts to share a single thread, automatically relinquishing control when they initiate an operation whose result won't be available for a while, can be a more efficient approach in certain circumstances.

Given that, I do respect what Microsoft was trying to do with async/await in C#. I'm not convinced they were entirely successful, though. The sales pitch is that you can happily bang out asynchronous coroutines as if they were just sequential code, but the truth is that if you actually try to do that you're liable to run into some nasty bugs.

I'm somewhat more intrigued by what some functional languages have done with the dreaded M-word to attack the same problem. The sales pitch is similar, but it's rather easier to deliver on the promise when "Just code like you normally do" being directed at someone who's normally writing in a functional rather than imperative style.
I will always remember what Bret Victor said about these kinds of projects in his Learnable Programming essay:

> As you can see, live coding, on its own, is almost worthless. The programmer still must type at least a full line of code before seeing any effect. This means that she must already understand what line of code she needs to write. The programmer is still doing the creative work entirely in her head -- imagining the next addition to the program and then translating it into code.

(To be fair to yaxu, its not live coding that he is talking about, but the feature of live update in isolation.)
>$.tenth
why, just why?
Another approach is to make it backward compatible with something else. For example, if you wanted to make a new site/network similar to StackExchange (but presumably with some revolutionary changes; not just a "me too" copy), you could start by adding an interface layer using the StackExchange API and adding some of your new smarts to give your users some of the benefit of your tool, on top of the StackExchange content. Most likely you wouldn't be able to add all the new goodness there though, so you would also do as other comments have suggested to build up your own content. Maybe even incentivize users to add stuff based on StackExchange answers they find (assuming some manual intervention is necessary to make the answers suitable for your site - and also assuming you comply with terms of use and such).

It's hard to give exact examples without knowing what you plan to do of course, but that's the general idea. Make it backwards compatible with whatever the closest thing is out there already, so that even in cases where you don't have any of your own content to return for a user, you at least have something. Then do everything you can to ramp up your own content asap.
It depends on what type of BI is implemented. This is around current minimum wage rates, so it could easily mean doing away with basic disability, welfare, and the government pension.

I would say you're naive of the costs if you think the system change would only be negligibly beneficial. There's the distribution costs, the evaluation costs, then there's the investigators to make sure people aren't scamming the system. For every system. You've got disability, welfare, unemployment and pension investigators to make sure everyone is getting what they're supposed to and to make sure no ones scamming the system. You can't scam basic income.

It removes disincentives to work, in that without welfare systems there's no disadvantage to work, and there's no advantage to trying to scam the system.

It does also do the contrary. It incentivized people not to work, at least for shitty employers. You can't be an assholr to a minimum wage employee when they can leave and still afford rent and food.

It also provides income for people to start up businesses (this has been shown in BI trials currently ongoing in India), which when we have high unemployment rates amongst youths I can only see this as beneficial.

What's better for society, an 18 year old doing busy work making coffee for people too lazy to make their own or do you want them writing apps, starting lawn care companies, etc.
Nice! Redis really does have a great code base to work with. I previously wrote on article on adding a custom datatype, essentially walking step by step through each necessary modification.

If interested, this article can be found here: http://www.starkiller.net/2013/05/03/hacking-redis-adding-in....
Agreed. Not sure why more people don't question when someone says something will benefit the "middle class" are they just saying that out of their own self-interest?
I agree with most of the critisisms, but Microsoft is also seeing those problems and is actively fixing them in ASP.NET vNext[1]:

- It's really crossplatform and open

- It does away with the IIS / System.Web dependency

- It has clean json based project files that can reference project dependencies locally and also on nuget and github

- It unifies the ASP.NET MVC and Web API frameworks and other good things like SignalR

Which only leaves the traditional mindset of .NET developers (SQL Server and Entity framework as the default data technology) as problems. In the right environment those remaining problems can be worked around.

[1] http://www.asp.net/vnext/overview/aspnet-vnext/getting-start...
The whole point is to enable the browser to be a full proper app platform- that includes enabling web apps to work OFFLINE. The behaviour of a browser without app cache is to fail to display content even if it is cached if your connection happens to be offline. the html5 app cache addresses that- and is the "standardised" alternative to google gears' local "offline" web server.
Facebook run experiments to manipulate users' mood
Optimisation with Continuations