skysight-inc/HackerNews huggingface dataset:
It's interesting to me that there has been very little mention of the fact that the Apple Watches (at least the watches we've seen so far) are purely for right handed people who wear watches on their left hand. If you tried wearing these on your right hand, you'd be reaching across the face to use the digital crown.

There are two logical solutions for this:

1) Sell a left handed model as well. You can expect there to be a 90/10 skew for righties just because of genetics, but that can be accounted for in manufacturing runs.

2) Allow the watch to be flipped upside down for the right wrist. While technically this would work, I highly doubt Apple would design something to be worn upside down.

Or they can just say fuck it and only make watches that make sense for right handed people. I guess we'll find out in a few months.
Just had a realization, I wonder if you get health insurance during your trial?
I don't recall stating anything about definitions; however, if you're a man approaching someone at a hackathon, you probably don't know the person otherwise (or you'd do so at a more appropriate place and time) and you're probably doing so on the basis of appearance (i.e., objectifying women). You're probably doing so because you think she'll be receptive (I have no idea what logic constructs these thoughts but men have them nonetheless).

I would say that your comment is a perfect example of male entitlement. Is it really so impossible to restrain yourself for the few hours a hackathon lasts?

Regardless of whether you actually are the one "nice guy" who would be respectful of a declined proposition, women have no such luxury. Because of our cultural focus on blaming women victims of sexual assault, women are taught (and rightly so) to be cautious of men, and a man becoming violent or threatening because of rejection is incredibly common. Forcing a woman to go through an incredibly stressful and frankly frightening experience, because you feel entitled to do so, is simply chauvinist. It demonstrates that you think your right to hit on women is primary compared to women's safety and mental well-being.

If you don't think that's intrinsically evil, I guess you just don't think women are human to the same degree you are, which is pretty common sentiment in tech circles.
What benefit does this approach bring?

It reminds me of Chrome OS and Firefox OS. These all are based upon the Linux kernel, so they could potentially offer a very rich user experience like so many more traditional Linux distributions do. Yet they intentionally cripple themselves into being limited, JavaScript-only platforms.

This would be understandable if, say, storage space was expensive, like it was in the 1980s, and the software had to be kept lean and limited. But that's clearly not the case today, even when it comes to low-end smartphones.

The same goes for runtime performance. It'd be one thing if software written in JavaScript was consistently and significantly faster than software written in C, C++, and other commonly used languages. But that just isn't the case. Unless we're looking at highly tuned and highly unrealistic benchmarks that even the JavaScript VM authors have focused on making run fast, JavaScript's performance is quite bad.

It would be understandable if perhaps the user experience could be improved in some way by them providing superior alternatives to the traditional userland software offered by Linux distributions. Yet this isn't the case, either, because some of the biggest complaints with Chrome OS and Firefox OS are that the bundled software is awful, and users have no real recourse due to the very limited environment that both offer.

As far as I can tell, users just can't win with a system like this. The kernel is powerful, but this power is isolated and kept inaccessible. The userland experience is much worse than what one would get if just using a traditional Linux distro, and running the JavaScript software on top of that. The benefit to the user just isn't apparent.
Where did you find bezier_clock.pde to modify? I would like to try a few things as well.
Because reasoning about hardware is hard it's important to be able to rely on simulation. I'm not saying that all issues can be caught/detected in simulation but many can. In most designs 90% of the code (typically the synchronous logic) can be fully debugged in simulation. Ok there is still a portion that can't be debugged, and you'll likely spend a large amount of time on that final 10% but the alternative is certainly worse.

A good designer can avoid constructs that can't be or are very hard to simulate correctly. A good example is signals that have to cross clock domains, metastability is easily missed in simulation and the problems it causes in actual hardware are huge. Good hardware design tries to avoid or encapsulate these kind of constructs.

Beyond this you still have to deal with the analogue world and that is often hard to simulate. Clock generators that misbehave, working with memory controllers (and buggy IP cores): it's not all under your control and that why hardware design often feels so hard. A lot of time is spend on these issues, but that's only because the rest is made easy by using VHDL.
How exactly to you choose a compiler? I have both cygwin gcc and clang (3.4 cygwin, and 3.5 native) installed. I can't seem to get it to use anything other than cygwin gcc.
We already know – they went with #2. http://www.iclarified.com/43778/apples-iwatch-is-reversible-...
Hacker tells Bitcoin creator, 'You are not safe. Get out.'