skysight-inc/HackerNews huggingface dataset:
philsnow – thanks for at least couching your response in a framework that is not patently absurd. 4 for you, philsnow.

Allow me to respond to various issues with my initial call of “Party Foul” en masse:

The thing says “chubby” models on a “diet”. I know that could refer to males or females, but this article was not written in a bubble – it was written by a thought leader in a male-dominated industry using a tongue-in-cheek title clearly meant to attract attention and elicit a chortle by explicitly evoking body issues (and don’t give me “Rails is fat models and skinny controllers” – that stops holding water when you change the terms to “chubby” and “diet”)(And please don’t try to argue that society holds body issues over men as much as it does women – that sentiment is so patently absurd that it’s not even worth parsing.). There is no “conclusion” to leap to – it is laid out prima facie. I’m not saying this applies only to women, I’m just saying that society tortures women a lot more with body issues than it does men and invoking those issues for the sake of a “clever pun” is not worth it for several reasons, including but not limited to: 1. Reinforcing the perception that tech is a frat house. 2. Reinforcing the reality that tech is a frat house.

I love DHH and everything he has contributed to technology.

Nevertheless:

After further review, the call on the field of “Party Foul” stands. 15 yard penalty – still third down.

Doesn’t make DHH a bad guy. I know a lot women who are involved in tech specifically because of Ruby/Rails – DHH’s net effect on making technology a comfortable and inviting field for women to specialize in is vastly positive, IMHO. I don’t think he intended anything negative with either his post or its title. I’m just saying the pun he picked to put in the title of his post sucks. That’s it. For those of you whose knee-jerk response to this is “lighten up”: I respond in kind. I’m just calling a “Party Foul”, not trying to pillory your gods. Lord knows, I probably have and will say/write things that are much more insensitive than this… I just hope that when I do, someone will call me out for it in a thoughtful, non-reactionary way.

Because I don’t want to lose that much more HN karma over this (I don’t believe in this enough to sacrifice 50 points criticizing everyone’s idol.), this will be the last comment I make.
part of the problem here is that wil wheaton's price for "selling his privacy" is higher than that of many others (largely because he is a celeb and so has more earning potential there), but the current mechanism has no way to manage a range of values.

it's possible a more sophisticated "privacy market" could solve these issues.
I never said it can never be justified. I live in the EU and agree with most of our consumer protection laws. I'm just drawing an important distinction.

Not participating in a transaction is a personal issue, which doesn't need justification. Not letting others participate in it should need to be very well justified, at least in a State that is supposed to be democratic and just.

Personally, and in this particular case, I find the justification lacking.
Does it bother anyone else that to play one of the winner games ("Hotfix"), you have to download and install this "Unity Web Player" plugin? I also want to note that none of the other main winners had that.

Downloading a plugin to play seems counter to what HTML5 web games are trying to do?
> I'd say it's ridiculous to re-ship to a different address based on an unverified claim of non-delivery; especially for high-cost items.

It is. But Amazon is a ridiculous company that doesn't follow the rules of common sense. Amazon would rather lose a little (in the scheme of things) to fraud and continually amaze its customers than to stick it to thieves and Amazon customers. The customer is king.

It's especially genius with the Kindle because even if it's sent to a thief they will probably make money on it from the Amazon purchases of whoever ends up with it.
I don't think monopoly or not status matters to data protection law, which this might fall under. Sure, the USA (say) with anti-monopoly law but no data protection law, this might be an important point, but in EU we have monopoly law and data protection law.
Thanks.
We did include both the raw data and calorie count references[1] in the footnotes in the original article. We also encourage you to play around with the data in Statwing [2]. Appreciate the feedback and curious what else you can find in the data!

[1] http://bit.ly/U6JQ5c
[2] http://bit.ly/SMPeMZ
The Year Without a Santa... Hack.
Just a guess (and I didn't look at the link) but possibly the Akka library. http://akka.io/
Burst out laughing at the cricket section! Read the comment, then scroll through all the crickets.
I'm glad we do have a European law that mandates websites to delete personal data at the request of users.

No, that law hasn't come in yet. It's planned to come in. Current EU data protection law requires that companies delete/correct data that's incorrect, and they can only store information if it's proportionate to what they're doing, and if you've consented at the start. But as ar as I know, EU law/directives does not allow you (yet!) to be "forgotten".
Heh, 's nice to read about that and as a pinball-enthusiast i'm a bit saddened for it to be gone, even if it is more for retro-reasons as opposed to it being special in some way...

Maybe MS should team up with someone who understands making (digital) pinballs, like the guys that created Zen Pinball?
I'm trying to figure out how you managed to get matte outlines on your transparent PNGs. This is making the logos hard to read and the t-shirt illustration edges look cheap. If you're not sure how to remedy this, I'd suggest using a solid background, particularly when you know you'll be using logos.

I'm also more interested in seeing bigger photos of the actual shirts+swag produced rather than thumbnails and illustrations. They look well-made and do more to sell me than the rest of your site.
Because there's absolutely no economic incentive to ship on the estimated ship date, unless you plan to do more Kickstarter projects.

At a guess, funding will go up inversely with the estimated wait for shipping, and that relationship will be counteracted by some believability factor that is directly related to the apparent complexity of the project/apparent expertise of the project leaders i.e. people will not believe that you are shipping a flying car a week after the funding date, esp. if you don't have any pictures or graphs and you're three art students.

Unfortunately, the apparent complexity of the project/apparent expertise of the project leaders is going to be consistently way wrong, due to the credulity of the general public.

If you only plan to do one Kickstarter, fancy renders and other graphics + the earliest physically possible estimated ship date is the rational choice. Then just blow the date. There's absolutely no consequences. If what you get to the backers (late) turns out to be awesome, you'll still end up getting nothing but positive press.

The only time I've seen people get really irate about Kickstarter shipping late (but shipping) is when the backers' "exclusive" promos were also sold in other venues, or when retailers got a hold of stuff before backers did.
There are tons of different possible results, depending on what they measure.

Maybe the machines are dangerous for the people who work around them every day. Why aren't these people wearing dosimeters?

Maybe the machines have an effect that only appears in a very small percentage of individuals.

Maybe the danger only comes after the machine drifts out of calibration, while in a humid room, operated by poorly trained persons who misinterpret a control panel, when the person scanned has a given gene, that is being expressed because they have a viral infection.

Conclusion 3(that you listed) can only be considered crap. To arrived at it is to claim to have a perfect understanding of several very complex systems. No matter how many studies you perform that fail to find a danger, that is not evidence that no danger exists.

"The absence of evidence is not evidence of absence."

The most you can ever say is "We found no evidence of dangers."
Counting the years from the time the languages entered the spotlight might be a better metric of age. Even though Python is only four years younger than Perl, it feels so much newer because it spent more time 'in the oven'.

I'd peg Python's coming of age around 2001, although I could be wrong about that. Ruby is even fresher out of the oven, not really reaching the limelight until 2006.
Your examples only make a legal name important if you consider these things
important. I don't, and they aren't. Part of why we need to get rid of the
concept of a legal name is exactly for this reason. A government has no
business and no authority to decide who I am.
Landfill Harmonic Teaser
Can't comment for everyone, but as I tried to explain why on the readme: Essentially, none of the existing dashboards did exactly what we wanted, and it was fun to try to build something different. The task was made easier by using some elements and ideas from at least some of the existing dashboards, like tasseo, gdash and graphene (each worth a look in its own right and they might be more suitable for some people).
Pierre, my question: The income tax rate for high earners in France is crazy high. Have you considered moving?
Be the Problem
Well that was nice and useless..
I believe the only difference is in units. Left showing delta time. right showing FPS.
I have a beta acccount and was waiting for this until I started playing around with it. Thanks! I'm pretty excited about building something on top of this platform.

The Scratchpad.io tool that has been on HN for the last couple of days has really blown me away with what Firebase is capable of. Keep up the good work guys!
Thanks. My approach is actually pretty minimal. Just a read-print-loop (-n, -p), a few local variables (equivalents of $_, $~, $. etc) and a shorthand import syntax to take away some of the verbosity. There are other projects, such as pyp[1], that are more ambitious, but put you through a learning process.

By all means, everybody should use what they are comfortable with. Ruby and Perl allow you to write extremely terse and awesome one-liners, the likes of which will never be possible in Python. But if the first solution that pops into your head is a Python one, why not use that?

[1] http://code.google.com/p/pyp/
Made me look up the timeline of when languages were released:
http://en.wikipedia.org/wiki/Timeline_of_programming_languag...

Pascal is 42, C is 40. Lots of fun info on that page.
Zero Risk Web Prototype Creation
Off the top of my head, Immutability means less locking, which is big enemy of scalability; Actor Model support in the standard library also makes concurrency much easier to deal with. Wikipedia [1] mentions that Scala "actors may also be distributed or combined with software transactional memory".

[1] https://en.wikipedia.org/wiki/Scala_(programming_language)#C...
> Not the most focused article, but kind of cool that they wrote about such a thing

Why? GigaOm writes about that sort of thing all the time. (BusinessWeek is just syndicating here, it's a GigaOm article: http://gigaom.com/cloud/why-you-should-expect-more-online-ou... )
Yes, basically.

Less code? Yes. Cleaner code? Yes. Faster? Probably not detectably faster or slower.
Wunderlist 2 is out
There is no application window. Instead, each application shows one window for each document, plus tool palettes, etc in their own window. The application would take over the global menu bar when active.

This is in contrast to Windows 3, which had the "multiple document interface", in which each application had its own single window, with the application's main menu under the title bar, and containing a sub-window for each open document and tool palette.

There are pros and cons for each design. The Mac's document-based style is aimed at making it easier to work with several apps at once. This sort of drifted away with the modern one-window Apple apps. Now they even go fullscreen, which has been a decent way to use Microsoft MDI apps since the 16-bit days.
Windows is more of a monopoly in the sense that there is much heavier lock-in: It's not trivial to write an application in such a way that it works equally well under Windows and the alternatives. The lock-in to Facebook is much, much lighter.

But more importantly, being a monopoly (however such is defined) is not in itself illegal, and it's not a carte blanche for publicity-hungry politicians to hand-wavily demand to control random details of a company's operations.

What is illegal is monopolistic behaviour, to leverage your dominance in one market to unfairly gain an advantage in another. That is what Microsoft did and was punished for (rather than merely being a monopoly), and what Google might be getting in trouble for.
When exactly is a good time for Google to release code? Facebook? Twitter? These are global markets. There are over 1 billion smartphones in the world, alone, and less than a tenth are US; I'd gander most are used to interact with one of these or similar big guys that do "continuous deployment."
It’s not about HTML5, it just needs to be playable in a browser:

> All entries must be web-based, i.e. playable in a browser. HTML5, WebGL, Unity, Torque 3D, Node JS, Flash are all possible - just be sure the source is made available on your fork.

https://github.com/blog/1303-github-game-off
Maybe not DRM as DRM, but sure you can protect such things. Just not necessarily with systems in place currently. Conceptually simple solution: unique tokens for your phone / address that a routing system directs to you. Your info is never even in the hands of e.g. someone you buy from, and you can simply revoke the token to prevent any and all spam from now until forever, regardless of what they do with it.
Oldie paper but still a goodie. Some other algorithms to consider... Random Forests, Gradient Boosted Machines (similar to AdaBoost), Logistic Regression, Neurel Networks.
I agree.

I think picking the "top 50" projects is just asking for trouble. Those are victims of their success, and have to scale from 0 to mass production on a tight schedule.

Going from zero to a few hundred early adopters is much more feasible.
It's a great story. One of the things I'm curious about is the original use... What was it created for to begin with?
That sounds like a sensible idea. Thanks. I'll try to update the readme soon with perhaps a short snippet from dashboards.js.
It's easy to eat a stick of butter and a cup of sugar in the form of frosting.

It's really hard to eat the equivalent calories in butter alone.
The Dead Sea Scrolls Digital Library
This is exactly what Ping.it fixes. Read this for a quick intro:
http://ping.it/press
I had envelope issues with wedding invitations - a lot of people received empty envelopes.
I'd suspect that on the flip side, if Instagram does intend to do this sort of thing, they will have a well-curated list of "who not to piss off".

That being said, said celebrities, professionals and popular persons also agreed to the same TOS...
Here's a pretty good starting point: http://gilesbowkett.blogspot.com/2012/12/rails-developers-sh...
This is our game guys - http://khele.in/pappu-pakia/ and we won! :D
Raspberry Pi Gets its Own App Store
As far as I know, Scala can't give you _better_ performance than Java, but I also can't see it being too far off.

I've never really seen the benefits of Scala. Everyone whines about Java syntax, but it's really not that bad. Verbose, sure, but it just doesn't seem like time spent typing is where my productivity goes. Maybe I'm just getting old, but I no longer care about language syntax as much as I used to. A preprocessor to give me Java 8 lambda syntax would probably solve all the issues I have with Java right now.
It can't even do 25mph. That's a deal breaker for most car users, especially when it costs as much as a used car. This idea feels more like "How far can we extend a bicycle?" than "How can we make a smaller, cheaper, better way for people to transport themselves?"
Wow, that's cool! Thanks for sharing that. Does Perl also have something similar to Python's "import pdb; pdb.set_trace()", which lets you drop into a debugger at a predefined location in your code? I've been finding that really helpful.

Knowing Perl, it probably is possible, and I just never learned about it.
So, the idea of using json rules rather than a simple javascript function is for speed performance?
Ugh. Edit the title and try again.
The best time to deploy is the time with the best engineers at the ready. If you're updating component X, you should do so when the stakeholders of X are online. It sounds like Google was able to solve things quickly, I don't think deploying at another time would have been any better.
I accidentally did something similar. I ordered an item, and paid for overnight shipping on a Thursday morning. The item didn't arrive as promised on Friday, in fact it didn't arrive until Wednesday the next week. That weekend, I called in complaining that I hadn't received my item. The label was printed Thursday, but UPS never picked up the package. They assumed it was lost and re-shipped my package. Low and behold, I received both packages and ended up with a 2 for 1. I kept the extra still in the box for a month, figuring I'd get a call from Amazon eventually asking for it back - when I never heard from them I decided to sell it.
Too bad it wasn't open source, then someone would have fixed it for free.
I think the benefit is that people don't want to say they're Java programmers. It's like a hipster thing. Most modern scala programmers don't even use the language correctly, or couldn't write "hello world" if it wasn't in the play framework.
I've recently been experimenting with some HTML5 mobile app programming, and since that saves you from the problem of IE8 I've been doing it without jQuery. So far I've found I don't miss it at all, to my own surprise. I wrote a few short convenience functions for XHR etc but it's nothing at all like mowing a lawn with scissors.
Akka can be used in Java just fine :)
Lisp was invented 54 years ago. The Common Lisp standard is the capstone on an unusually long and fractured history of development. Fortunately many of those good ideas have trickled down over the decades, making mainstream languages steadily less terrible, and competing proprietary implementations are no longer commonplace.
I've always wondered how one would disrupt the ISP market. Can you only enter this market with huge capital expenditures to build out a network? Are there ancillary networks/pipelines/bandwidth that could be utilized that are not explored?

It seems like Google is going down the road with using huge capital but are there other ways? Republic Wireless is the only other "similar" product to disrupt the telecom market.
Gigaom conversation with Dan Hesse of Sprint
Get ready for the biggest duck face/bathroom mirror stock photo sale of all time
Overeating may be the big problem, but abstinence from overeating is not really feasible for most people (it's depressing, really) and the truth is there are better ways of tackling overeating at the core. For me the interesting question is "why" we overeat.

For instance by eating healthier foods, instead of sugars and snacks filled with fats and refined carbs, you tend to feel less hungry. The theory behind it is proven actually, because sugars and refined carbs burn too fast, leaving you either with an empty stomach that wants more or with fat deposits from all the food that didn't burn at the same rate.
Spotting neuro-fiction: A guide to dissecting overblown neuroscience headlines
Water weight may make it harder to track your "true" weight, but that shouldn't affect your eating decisions.

More specifically, your water retention will fluctuate up and down within a narrow band depending on your diet, but you will never put on 40 pounds of water weight.

It's similar to limiting your how much water you drink so that you don't have all the liquid in your belly making you heavier.
I'd even argue that the best time to deploy is during the best engineers' working hours. At least you guarantee they're around when/if things go bad.

And by "best", I don't mean all stars (a la Fitzpatrick, Norvig, Pike or other Google celebs), but the engineer who actually followed the whole project/patch from dev environment to production.
I have never used Facebook and signed up to Spotify yesterday with no problemss.
College Entrepreneur of The Year puts ads on toilet paper
More difficult to work with.

It's not a problem for the computer if you have a lot of code in a single file, but it is a problem for the computer programmer. If there's a lot of functionality in a single file, class, or other grouping of code, that makes it much more difficult for a human to understand and remember the details.

It's easier to work with a project if you can break it down into small pieces that are each individually easy to understand, so a goal of good project organization is to make your code out of small parts - small files, small models, a small number of lines of code - and have the parts be easy to distinguish and remember.

If you split one big "User" model into separate bits for billing, authorization, and user settings, not only is it easier to understand what parts there are, when you need to go in and make a change to the billing code, you immediately know that 2 out of 3 of the pieces can be safely ignored.

Similarly, if you take some very common functionality that models often have and generalize it, you only need to learn the general version once and then it applies to each of the parts. That's what the article describes. Many models are "Searchable" or "Taggable", but you only need to learn how searching or tagging works once, and the same search or tag code applies in multiple places.
Is the story consistent with the 5 year performance of the stock?

http://finance.yahoo.com/echarts?s=S+Interactive#symbol=s;ra...;

Quoting the article, "When Dan Hesse took over the reins of Sprint on Dec. 17, 2007, he had quite the mess on his hands. That fourth quarter, Sprint was getting ready to announce not just an exodus of 683,000 subscribers but also an astounding financial loss of $29.5 billion, one of the largest ever recorded by a major U.S. company.

Sprint’s acquisition of Nextel two years earlier was a heavy albatross around its neck. Its customer service had gone down the tubes, employee morale was low, and the company culture fractured; worst of all, Sprint’s once loyal subscribers were fleeing in droves. Hesse knew he was taking over a struggling company, but in an interview with GigaOM he admitted that even he didn’t realize the magnitude of Sprint’s troubles until he arrived. “When I took over the assignment the problems were more severe than I anticipated,” he said.

Hesse staring in one of many Sprint “Simply Everything” commercials

Fast forward five years, and it’s plain to see Sprint has turned several corners. "
Keeping them separate has meant that no compromises are required. The touch iOS interface can go in one direction, and OS X, still very much geared towards mouse-pointer and physical keyboard, can go in another.

Microsoft, by trying to unify not only power-user desktops but casual tablet and even XBox and phone interfaces under a single banner is making something nobody wants. A unified experience is like one-size-fits-all underwear, not comfortable at all for anyone.
From any one of the many security experts that hang out here - can you give us an assessment of how secure this actually is?
EBS Snapshot Copy
Living in Minneapolis/St. Paul, I'm thinking this is not likely to catch on here. 4-5 months out of the year, the roads are icy; the air is cold, limiting the effectiveness of the battery; and the daylight hours are short. Maybe it'll catch on in the more temperate states.