skysight-inc/HackerNews huggingface dataset:
There are two things that come to mind when we ask if dietary fat causes obesity. First: fat and carbohydrates sum to literally all of food. The caloric value of protein is (essentially) negligible. What is certainly the case is that we can point to people who are fat (preferred term) on a low-fat diet. We can point to people who are fat on a fat-intermediate diet (rough balance of fat/carbs). Can we find many people who are fat on a low-carb diet?

I suggest that if we do, most such people will not be found eating fat in its natural form, but as rendered fat and pressed oil. It is almost certainly the case that the way in which fat is consumed affects satiety: the body cannot see a caloric benefit from fat until it is beta-oxidized in the liver, many hours after it is consumed. So in order to estimate how much you have eaten, the body assumes you have consumed fats in their natural form.

This is key to most low-carb diets: fat is usually consumed in its natural form, since nobody drinks oil (eww) and fatty snacks such as potato chips are banned. It is also an intrinsic feature of the "paleo" diets, which ban processed foods.

So, it might not be too much of a stretch to say that fat as a naturally occuring part of foods like almonds does not make us fat.

The second thing that comes to mind is the balance of omega-6 and omega-3 fatty acids in a healthy diet. When this is tilted excessively in favor of omega-6, the body produces an excess of certain endocannabinoids (arachidonic acid) which contribute to overeating:

http://www.sciencedaily.com/releases/2010/07/100726221737.ht...

[NB: the mechanism is up in the air. The effect is real.]

The additional, final consideration is the alleged link (as stated in the article) between consumption of land meats and obesity. See https://en.wikipedia.org/wiki/Red_meat#Obesity

I've been harping on "natural", and meat is natural, so what gives? Weirder yet, the correlation is with meat protein, not with fats. And we do know, though, that people on e.g. ketogenic diets lose weight while eating lots of meat: http://ajcn.nutrition.org/content/82/1/1.short

The simplest way to assign blame is to cry confounding: while meat itself is natural, it is rarely consumed in a natural-food context. Instead, since meat is culturally considered unhealthy, it is often eaten on white bread or in a pack of Lunchables. Support for the confounding hypothesis would be a low r-value in studies that link meat consumption to body fat (i.e. total variation in body fat is only weakly related to variation in meat consumption); falsification might be a very high r-value, or a very well-controlled study.

[NB: I believe the confounding hypothesis.]
This is the one thing I don't understand about the GNU/Linux thing. Doesn't calling it GNU/Linux imply that it is derived from the GNU/FSF philosophy? To me it would make sense if another term can be coined to refer to systems that have a GNU base, yet go against GNU's goals, yet still credit the GNU project for its contributions. (I hope I'm not re-igniting the bad parts of the GNU/Linux debate).
I also said use. The primary thing I dislike about Twitter is that they now limit apps to 100K tokens. This past weekend Falcon Pro, the Twitter client I use, reached the limit and is now unable to offer it to additional users.

This also impacts me as a user because the official Twitter apps have special privileges that third party apps do not. I believe this is why third party apps do not support push notifications.
With all the recent attention towards startups that aren't doing so well, it makes me wonder what motivates the founders to continue moving forward? Is it from a lack of choice? Or maybe pride?
I don't know if there was much you could do with a product like that. I don't know who that would appeal to. Was it basically Google Hangouts for shopping?
> Obviously most, if not all men are rapists.

That's Marilyn French's view, as famously quoted from "The Women's Room":

http://www.amazon.com/Womens-Room-Marilyn-French/dp/03453536...

It's also true that to a hammer, everything looks like a nail.

> Luckily, they are also obsolete!

Maybe. I personally will suspend judgment until I see women open their own businesses and banks and refuse to do business with men any more.
While I agree with many of the sentiments expressed in the article, I think "never goes down" and "costs you practically nothing" only seems true while nothing bad happens.

When a hard drive crashes or a truck runs into your data center (here's looking at you, Rackspace) or you need failover for any reason, that's when you wish you had virtualized in more than one machine.

Want something that's always available and never crashes? Look at freenet. Distributed computing model. If we can failover the DNS, you can have the same thing on the web.
I'm sorry I said that strangely. The point I was trying to get across that you use Google logins a lot. For example I have 4 email accounts on 4 or 5 devices, in multiple mail applications along with service specific apps like the Google plus or similar apps. Which ends up with a lot of application specific passwords.
https://gist.github.com/wilkie/5032530

You naturally cannot use a microscope and come to a fixed, proven conclusion. However, I would say that all of the causes of attrition are very likely based upon a prevailing systemic gender oppression (sexism.)
Here's more of the back-story to why they created the ASP->PHP compiler in the first place: http://www.joelonsoftware.com/articles/FogBugzIII.html
This is getting long and probably not interesting for anyone else. Sure, much of the more extremes in the U.S. is simply that with a larger number of people, the extremes are also further away. But the extremes are there. Why there are not so many socialists in U.S. national politics is surely because of the first-past-the-post system, not because of lack of diversity in the electorate.

As to evidence about Gus Hall's parents, that again winds up a bit too far away from the point of this thread, so suffice it to say that I just read some memoir where this was covered, can't find a reference. But his parents came from politically active Tampere, and were founding members of CPUSA. (Incidentally, Tampere was also the place where Lenin and Stalin met for the first time, in 1905, but Okhrana was on their trail and Lenin fled soon after the Halbergs. This is just an anecdote that I find funny, not something that's really evidence about politics today).

I'll concede that I can't measure political diversity well enough to convince you without spending too much time and boring anyone. The ethnic diversity was already commented by someone else with some demographic data which is more readily available.
At least on iOS, the Google Authenticator app doesn't allow its tokens to be backed up or transferred.
What if you have to shoot someone and there are "pain-in-the-ass innocent bystanders" behind him? I.e. even if they get injured or killed, fewer will die?

Now, that's not likely to happen, i.e. ideally you can follow Rule 4 by changing your angle, but ... well, in the real world your alternative just isn't going to happen. Unless they take personal responsibility (and in anti-gun places like NYC that's very hard since there aren't many places to shoot), most police aren't good shots, don't have to shoot very often, and aren't well trained. At the Connecticut legislative hearing on this, the anti-gun police officer giving testimony had to admit training was on the order of a few hours a year. And then there's fire discipline, you have seen the picture of the pickup truck, wrong model, color and with two Hispanic ladies delivering papers, that was perforated by LAPD cops who were ... concerned that one of the own was hunting them?

However, that's not the main reason for using expanding ammo in self-defense. We, civilians and the police, are not allowed to kill per se, nor is that our objective. If in such a situation, we desperately want to stop someone, and for handguns "stopping power" scales with the diameter of the bullet, including expansion if that occurs, lethality with the number of holes you punch in someone.

For .223/5.56 NATO, Full Metal Jacket (FMJ) rounds have very iffy stopping power (details on request), so using them in self-defense if you have an alternative is a very bad idea.
That is so awesome. Thank you.
Top Muscle, Strength, and Fat Loss Exercises
If you want "anyone" to do it, why don't you do it yourself? It's an interesting and rewarding project and there are a lot of resources for this, plus a similar project that already exists.
Never shot a bolt-action, but did get to shoot an AR-15 and an AK once. The AR-15 was so smooth, had a holographic sight and a stock that collapsed to take off the recoil, felt like I was reaching out and poking holes in the target with a sharp pencil.
Well "compiler" in this case is really "high-level code generator" instead of "low-level code generator". So yeah.
I built this one night as a sort of example for GAuthify.
Real simple, just checks a user's email against a database, retrieves their unique GAuthify ID, and checks that against the GAuthify API.

http://zackboehm.com/dev/gauthify-phplogin/
My gut feeling too.

If I were living within 7 minutes walking-distance from work, I sure wouldn't mind coming in, especially if work is so flexible that I can come in at 3pm and nobody lifts an eyebrow.

My workplace is actually not that far away, around 25-30 minutes of public-transport commute. I still see lots of benefits for remote-working. Striking a balance is the key. I wouldn't want to exclusively work from home either.
I don't think the arguments against were hinged that much on difficulty. Mostly it stemmed from supportability, correctness, having to train all your new hires on your new language, etc.

Sometimes, sure, the right move is the least worst decision. But that doesn't excuse it for being a bad solution in general.
It is nice to see some competition to Leap Motion[1], which made into HN's first page a few weeks ago[2].

Getting them integrated with Chrome/Firefox would be amazing.

[1] https://www.leapmotion.com/

[2] http://news.ycombinator.com/item?id=5179335 and was not the first time:

http://news.ycombinator.com/item?id=4250536

http://news.ycombinator.com/item?id=4170446
FogBugz' core is still in Wasabi, but nearly all new code, including one hell of a release coming out soon, is in C#. The Wasabi core is gradually dwindling into an API shell, which will itself probably disappear at some point in the future. If you prefer to think of it this way: on any given FogBugz page load, you'll hit Wasabi, but the time spent in Wasabi will be increasingly tiny.

Kiln is pure C#/Python, Trello is pure CoffeeScript, and so on. Wasabi solved a porting issue. It wasn't designed for and isn't used for new stuff.
If customers prefer to run bug tracking software internally, then you are giving up a lot of customers by only offering external hosted solutions. If customers prefer one stack to another for internal solutions, then you are giving up a lot of customers by saying you only work on PHP or some other stack. If you just look at Joel's decision to write in something compiled to different stacks that can be run internally from a technical perspective, yeah, it sucks. But if it doubles the number of people who will buy your solution, then it may not suck from a business perspective.

Software is all about spending a fixed amount to produce it and then selling it over and over and over. If you double that fixed amount and double the over and over and over, you doubled your profits. Writing once and compiling to two things is less work than writing the same product in two different code bases as well. That sounds good and ignores things like buying a magazine ad becomes more efficient because more people who see the ad are potential customers.

As an engineer, I sure as hell wouldn't want to work on a system written in Wasabi. But as a business person, or an employee getting equity or options, it might make sense.
Semantics3 (YC W13) Is A Massive Consumer Products Database To Rule Them All
sorry to hear about that. Your comment is very helpful as most, in fact, all Canadians I know are from big cities, and so I now have a richer set of anecdotes... ;)
Does it suffer `Gorilla Arm' as others? Is it necessary to keep one's arm aloft for hours to get in a day's work? It certainly looks exciting for momentary input.
slava @ rethinkdb here. We don't support Python 3 out of the box because rethink uses protocol buffers for communication between client drivers and the server, and the protobuf library hasn't been ported yet to Python 3. As soon as it does, we'll support it officially.

If you'd like to fund the porting effort of the protobuf library to Python 3, shoot me an email to slava@rethinkdb.com and we'll see if we can arrange something. Otherwise, I'm sorry, but you'll have to wait :)
The science is pretty basic. It's the law of thermodynamics. Your body can't magically create fat or other weight from calories you don't have.
I've done it several times. It always was for geographical considerations - I'm not able to relocate for personal reasons. If you can relocate or are living in a relatively poor area, the financial consequences can be very attractive, I've had colleagues from eastern block countries in that situation. For me that part is a wash - but instead it allows to work for companies I personally consider more interesting and better fit to my skills, compared to the locally available jobs.

You can indeed shift some activities that normally happen after work (and the two you mentioned are very typical) to moments during the workday, when such venues are much more quiet. This saves you time. In my case (and current job) it is also more interesting to work late in the evenings because I have to coordinate with a team in the Valley, which is far away from me timezone-wise.

The time you save commuting is 100% won, either for your personal use or to work more for your employer/customers. This can be very substantial.

Offering remote work isn't as easy a saying everyone can go home. You need management that understands what the employees are doing and can judge their output. You need infrastructure such as a secure chat and reliable videoconferencing. The latter is for some reason very hard to get right. You also need a good mindset that doesn't treat remotes as the exception, so you need either teams that are substantially remote, or managers that are remote.

If you're working remotely, you need to deal with things such as potentially being lonely (I have friends on IRC, which are essential to keep me sane, other people go to co-working spaces or go grab coffee, etc), the risk of slipping sleep/work cycles, and good separation of work/home time (this is tricky, but my social life seems to be OK :P).

I've found IRC just as conductive to getting into the company atmosphere as an office. It depends on the employer though. At least on IRC you don't risk sharing the office with the most boring people in the company. You can also regularly have real-life team meetings. My experience is that during those nothing gets done (exactly like working in an office j/k) but you can get to know your teammates a teeny bit better.

Productivity-wise, the advantage of working from home is that you can keep on going if you're on a roll. You'll have bad days too, just like you can have bad days at the office.

So: the downsides is that the company needs to invest a bit in this, and have a setup that's workable (enough people remote!) with a management and IT that can cope with this, and that it doesn't work as well for everyone.

The upsides: you have much more latitude in hiring people, and you win the commuting time.
Amen, thank you.
As I said to your sibling comment, it's helpful to hear of your experience.
Thanks! I'm going to write up a post with more details about the tech behind it. Stay tuned.
WebRTC - ringing a mobile phone near you.
Understood, but the original blog post begins “Boxen started nearly a year ago as a project called “The Setup” — a pipe dream to let anyone at GitHub run GitHub.com on their development machine with a single command.”

It was this line specifically which implied that Boxen is used to emulate the production environment in OS X and spurred my comment.
I'm wondering; both android and ios restrict apps from using the javascript vms (v8 and nitro respectively) because of security concerns (being able to generate code and mark their pages executable). The embedded webkit implementations use JSKit interpreter as far as I know. (Correct me if I'm wong)

How does FF OS handle this? I believe if there is absolutely no native code execution involved, it should not be a security concern. Is that so? Is it currently possible to have fast js execution in UIWebView iOS apps?
Not sure how others do this, but I use Amazon Cloudfront. You just prepend the cloudfront url to your asset path (like mybucket.cloudfront.net/path/to/my/local/file), and ... that's it. That's all you have to do. It's fantastic.
Accessing your email box is a different matter than taking over the whole account. The former you can generally recover from.
Maybe I shouldn't be, but I am kind of surprised that you can do an ecommerce site using mostly generated files. The two things that I wonder about are (1) displaying cart/user information on every page (is it all javascript?) and (2) csrf in the forms.

Also, I would assume that javascript becomes a requirement for the functioning of the site; I always considered ecommerce to be the one part of the web were you wanted to be able to operate without javascript, so as not to turn anyone away.

I found this blog post that says that in 2010, 2% in the US had JS disabled:

http://developer.yahoo.com/blogs/ydn/posts/2010/10/how-many-...
Meh, Github always seemed to me like an elite club of rich Bitbucket haters...

Like by having an account you're saying, hey, I'm rich enough to spend $7/mo just because I like a pretty UI.

Give it to charity for goodness sake.
> chances are, unless you’re an absolute genius, the collaborative efforts of an open source project will beat whatever you can do in 8 hrs.

It depends. There could be an information asymmetry that leads most people down the wrong path, and an open source team could be subject to groupthink that leads them down that path faster.

A lot of what distinguishes experienced programmers from inexperienced ones, is that experienced programmers generally know how to mitigate non-obvious risks. What distinguishes great experienced programmers, is that they know how to mitigate such risks more efficiently.
Ask HN: 'hacker' or 'hackr'?
I am registering a domain for my business. As you already know it is hard to find one that is not already registered. The above is just an example of what I may be doing. Omit the 'e' in the 'er' which isn't available. Do you think it matters? Assuming later on you've built your business around 'hackr', do you think it would become a serious problem if someone else owns the 'er' version? Yahoo owns both 'flickr' and 'flicker', but Tumblr owns only 'tumblr', not 'tumbler'.
If the configuration was data, then you would have to parsing steps:

Data => Python
Data => JavaScript

With this setup they only have one:

Python => JavaScript

Granted, storing it in YAML/JSON/whatever means that you could potentially have many different codebases / languages reading it without a Language A => Language B conversion. It just depends on what works best for your project / team.
You make a good point that Yahoo and 37signals are NOT in the same place. Yahoo needs to throw cold water in their faces, wake up and make some big changes, 37signals appears from the outside to be doing well.

Very different situations.
An automatic rifle is much more dangerous than an automatic handgun, because of the physics involved. When a bullet enters yours body, the rapid deceleration of the bullet creates a shock wave that creates a micro-cavity in your body that lasts for milliseconds. This micro-cavity does enormous damage to your internal organs. That is why rifles (which fire bullets with much more kinetic energy) are so much more dangerous than pistols.

In general, you are much more likely to survive multiple pistol wounds than you are multiple rifle wounds.

Sidenote: Rifles used in the Civil War and modern rifles fire bullets with roughly the same kinetic energy. Improvements to gunpowder have allowed smaller bullets to be fired with larger velocity.
Before I really started coding I worked in electronics (designing mixed-signal design kits at the semiconductor level) and I remember I used to judge programmers by how much "better" at google they were than me. Since I've switched over and become a full-time coder (and co-founder which is a whole different exercise) I have become far better at searching for solutions to my problems than I was in the past. That being said I don't think it's the fact that I default to searching that makes me a good programmer. I think it's like some of the other comments have mentioned, the ability to filter what information is useful or not quickly and then apply and test the useful information so that you do not have to re-derive every action. This has led me down a rabbit-hole a few times where I would be testing different solutions when just building it myself would have been much faster, but overall I definitely think it is part of what makes me work at the speed at which I do.

I'm reminded of Mathematics from college. When first learning something it's difficult and simply seeing the solution won't improve your ability to recognize it. But once you figure it out once, you may not immediately remember how to apply it when faced with a similar problem, but recall is very quick because your brain has already wired the pathways of understanding.
What's your evidence to support claim #1?
Google's authentication schemes can be incredibly confusing, and they're something I've had to deal with while building an unofficial client to Google Music [0].

Here are two things worth knowing (that are somewhat covered by the article):

* aside from OAuth, any method of client auth is basically equivalent to SSO (ie, your entire Google account). As noted in the article, this includes app-specific passwords

* SSO is not meant for programmatic access. If you want code to have access to SSO credentials, it's easiest to use some other auth service, and then "upgrade" to SSO (the linked blog post describes one way of doing this) [1]

[0] https://github.com/simon-weber/Unofficial-Google-Music-API

[1] http://nelenkov.blogspot.com/2012/11/sso-using-account-manag...
Could anyone explain to me what's the point of Google's two-factor authentication?

Without application specific passwords it's actually pretty secure. With ASP of course, according to this article, it's no more secure at all. So it looks like ASPs need to be revised/locked down. That doesn't mean that 2-factor security is useless in principle, just that this facet of it is insecure.
The obviously bad part is that you pollute the global namespace for no reason other than laziness. When someone comes across code that uses a "Table" object interchangeably with "Dictionary" and "Hash", then he's going to have to look through the source code to find this bizarre line only to find out that you renamed a built-in container for no good reason.
I think this is starting to change, slowly, but many schools do/used to get kickbacks from snack vendors in exchange for placing their products in vending machines in the school.

"Oh, you need new uniforms for the basketball team? We can help you with that. Just put our machine in the hallway, and our logo on the scoreboard." This is not hypothetical; this is how things were run when I was in school.
That's one of the advantages of the MYO: You arm can be at your side, on your lap, an arm rest, etc. It doesn't need to be seen by a camera.