skysight-inc/HackerNews huggingface dataset:
Whoa dude, I totally disagree with the statement that 'the network', which you refer to as the 'product' of Facebook is not able to be copied. In one sense, Google has made the entire Internet searchable. In another sense, I think it would be possible to put together a decentralized Facebook, sort of a specification for blogs, that could replace Facebook under the right conditions. I could go on.
I don't think your design is that awful, actually; and I kind of love that it's pretty gender-neutral.
My god it is about time that someone started looking into this technology. I understand the tech hurdles and the even cleaner tech etc. but think about how much safer LFTRs are. Even just to replace all the running reactors if not build more.
http://www.ted.com/talks/kirk_sorensen_thorium_an_alternativ...
The starter edition worked for a long while for me to get a good feel of it, and I had no problem putting down the $ since it's a great platform.
I wonder how Rust is at this.
I have slept under this fan for 15 years now and I keep it running almost constantly. It has yet to kill me. It is on at this very moment and I will sleep under it tonight.

I wonder why we haven't see some silly correlation like "breath death." Do you have any idea how many people die shortly after breathing for the last time?
The Samsung TVs can supply something stupid like 300ma. Enough for a USB stick, but not a spinning disk that is host powered.
This was a really clear, concise overview. Just the right amount of explanation and clarity for me. Thanks!
> could have been the main way mobile applications are developed

is this so bad? I see at a competitive advantage to use their platform.

I'd rather ship 1.0 and 2.0 quickly to learn from customers than focus on the one true way to build mobile applications.
I'm using it, and I love it. I actually am getting some very good performance on Android since the language is actually good (related: http://jeffrey.io/damn-garbage-collection)
Good Writing
Sounds like you need a new router with a 5ghz channel.

According to this review[1] it won't be useful for the Google Chromecast:
"Internally, the hardware supports 2.4GHz Wi-Fi 802.11, which isn't quite as nice as the dual-band Wi-Fi offered on Roku's Streaming Stick."

[1] http://reviews.cnet.com/digital-media-receivers/google-chrom...
I can smell the blood in a niche market.

https://www.google.com/search?q=tv+stick
I've been using knockout heavily for a project recently and have come to really like it. This is a small to mid size website, about 6 engineer months of effort and somewhere in the mid 10klocs of custom javascript. Some strengths of knockout:

- it builds on the "Good Parts" of javascript, in that KO observables are just closures. You can pass them around or attach them to different objects however you feel like. For instance, we built a standard UI widget for entering currency values. Anywhere we need to accept currency, we instantiate one of these widgets and pass it the observable that holds the value. Clean, easy, encapsulated.

- Some people have a distaste for the "()" syntax: obj.prop() rather than obj.prop. There's some truth there, but the "()" syntax has one big benefit that overrides the slight ugliness in my experience: it catches naming errors immediately right at their source. If you've ever had to refactor a fairly big piece of JS, you know that one difficulty is correcting all the changed references. And if you miss one, the bug may be subtle, as the old reference doesn't except but quietly returns undefined. With knockout, the old reference blows up immediately, as undefined isn't a function. This is a big win.

We had some growing pains with knockout. Lessons learned:

- don't build anything but a small web app the way the knockout examples demonstrate. The reason is that while knockout claims to be MVVM, their examples are really just VVM -- there're no distinct model classes. They store data directly in the viewmodel classes. Bad things follow as your app grows: since the data is in the VM, any view that needs the data (i.e., all of them) needs to be bound to that same VM, meaning that your one VM ends up needing to feed several views. You find yourself annotating your viewmodel into sections -- "// these properties are used by view X ... // these properties are used by view Y" etc. Yech. Much better to have true model classes, then build a VM class on top of the model for each of your views.

- we now make heavy use of named templates to decompose large views into more manageable pieces. We wrote a simple custom binding to make this easy: since each VM is designed to work with a single view (see prior note), we put the #id of the view's named template into a .Template property of the VM class. The custom binding inspects this property and binds the VM class to its named template.
If you're using a sharded Redis, your problem is a collection of problems satisfying the above law. What I'm getting at is that if performance is seriously a problem, few things beat a dedicated service with concurrent, in-process memory--instead of pushing every operation to an external, fully serialized heap.
Because nuclear power plants have always been about producing weapons grade plutonium at least in the US; power generation is ancillary. Why else would we cap plant liability at $1billion? A big meltdown will cost way more than that, Fukushima cleanup is now looking to be about $80 billion. Since plants couldn't make the economics work if they had the liability, we had to entice them so we could participate in the arms race.
He didn't have to, because it didn't pass the House.

However, he's been vocally supporting spying, so it's assumed he would have voted No on this bill.
I am extremely interested in direct democracy, and the possibility of using it for larger populations thanks to technology improvements. To my knowledge the main argument against direct democracy has been "it only works for small groups". Could modern computing and telecommunications change that?
`git diff --staged` is the same thing. Git did a very halfhearted move to the `stage` verb and then stalled.
My experience was almost identical to the author's. As improbable as it sounds, reading the book and following it's advice completely eliminated my RSI pain after 3 years of dr visits (steroid cream), physiotherapy (tens, ims, massage, art, etc), and every ergonomic input device I could get my hands on failed to help. My RSI was starting to bother me even when I wasn't at a keyboard, to the point where it hurt to drive. I'm the last person I would have ever expected to use some "new age" treatment, yet as soon as I started to read the book, my pain lessened and was 100% gone within a month. I strongly agree with the author's premise about emotions playing a role in this, and in my case the onset of RSI corresponded with a very stressful time in my life.

Maybe this won't be the case for you, but it certainly was for me. I can once again type on a normal keyboard all day with no pain. 2 years ago I would have never believed this possible. If you're in a similar situation, you should give it a shot. It costs nearly nothing, and has helped many people (read the book's reviews on Amazon).
You know, DDT was actually used in an Albertan Junior High textbook as an example of a horrid chemical that caused cancer and posed serious threat to the health of the world. They reference Carson's book as an example.

I saw it before in Social and English but damn, the liberal slant of the system has never been so obvious in the sciences.

For a conservative province this is very surprising. It is one thing to be pragmatic and use facts that are just there to be used but cherrypicking data for students to learn and then testing them on it in a subject where it is supposed to be unbiased?

Sickening yet fascinating.
How admirable, good for you. I don't have anything more to add than my sincere appreciation for seeing what you're doing, it's a fantastic example.
Ignorance more frequently begets confidence than does knowledge. such a good summary of Java (and now Javascript) madness.)
No you don't. Thorium reactors are actually breeder reactors which run off of U-233, one of the byproducts of breeding U-233 is U-232, which emits gamma rays like nobody's business. The only way to stop gamma rays is with lots of shielding made out of high-Z materials, like lead, which is inevitably super heavy. So you'll either get a multi-ton car that crawls or a light-weight car that gives you cancer or a lethal dose of radiation if you drive it more than a few hours.
Quick comment: don't expect Daala to be a mature codec for a while yet. To quote Monty "Writing a complete new encoder from scratch is a small task compared to the time required to then tune that new encoder into efficient operation. Incremental changes allow demonstrable, steady progress."

The downside is that incremental changes leave you stuck in a sufficiently large local maximum, which is where Daala comes in.
I have no problem with kill -9. I use PUB/SUB sockets. I only have problems with reboots.
I like a lot of this, but one part I'm not so sure of is that, if I follow the docs, all get/set operations need to be from the root of the model. They take a "keypath" that starts at root, like "obj.get('subObj1.subArray[3].prop')". It seems to me like that would make it difficult to decompose a large application into component pieces. Your components, to do any get/set operations, would need to know their path from root. And what if that path changes, like an array that's modified? Seems like it could become a considerable barrier in mid-to-large applications.
Every git talk everywhere, everytime, should include "git rerere". http://git-scm.com/blog/2010/03/08/rerere.html

Best time saver ever.
That's an interesting thought. I need to look into whether I have TCP keepalive turned on for my private interfaces.
Congrats, it's amazing what you have achieved.
Hi evjan, just saw your reply. Here's a few ways I want to improve on Anki:
- "just works" deck importing from various formats (including Anki)
- Card formatting with Markdown
- Better deck sharing, forking and subscribing. Commenting on decks and collaborative shared deck creation. (I'm considering piggybacking on Github for this feature set)
- Slicker, more user-friendly UI
- Progress-updates and study-reminder emails
- Better sense of progression and achievement through charts and study-session summaries.

Most important however is creating something you don't need to install on your computer, looks good, and that "just works".
Very impressive. It reminds one that complaining about "too much work" is often just a poor excuse for petrifying in a niche of self-satisfaction and comfort. I can't read all of this, browse what you've accomplished in so little time, and doubt the feeling great things are destined for you. Congrats!
I think the issue is that the support for .NET libraries on Mono is trailing what is delivered with the MSFT tools. That said, Mono has been doing a generally good job trying to keep up and has very visible api pages about what is/isn't supported and how people can contribute.
PG's reply here is still consistent, if we assume that hackerschool is meant to train effective programmers, not so much star ones. But you raise an interesting parallel, though. It seems that a premise of YC is not so much to train great startup founders as to distil them out of the world population. I don't know whether that the former is hard, inefficient, or impossible, but I'm sure a lot of people would like to know.
See https://news.ycombinator.com/item?id=6091086
for a special case of "waking people up".
unfortunately I can't do that while the vm is booting up, and after bootup there is no traffic, so nothing to look at.
People who talk about the awesomeness of Thorium reactors rarely mention the very real downsides and technical hurdles. Such as the gamma radiation issue, or the fuel processing difficulties, and so forth.

Moreover, aside from overcoming those issues building a suitable commercial power reactor will take a lot of time and investment. We're on the cusp of the 4th generation of Uranium/Plutonium fueled fission power reactors which represents many decades of improvement in safety, reliability, and efficiency. Whereas LFTR designs are in their infancy.

The design deserves research, probably even in the $1 bil/yr range or higher, but we're not going to be switching the base load power plants to LFTR technology in the next decade or even in the next three decades. At this point, from a practical standpoint it's only slightly farther along than fusion technology, if that helps put it in perspective.
Nathan Myhrvold

He did this cool TED talk about shooting mosquitos out of the air with lasers salvaged from commodity electronics. Since that was years ago, it appears that it is doesn't work in the real world. Par for the course with TED.

A prominent malaria expert tore into him for exploiting a real crisis that kills millions to make his company actually does something good for the world. Going all hi-tech hero when what is really needed in low-tech nets.

So I'll go with evil for $500. Nice cuddly evil but evil nonetheless.
If you are doing freelance and consulting work, and not product development, then you should set up some type of hourly billing system, or consider setting up some type of'finders fee' for the work he brings in. It should be noted, that most freelancers/consultancies do not need a full time bizdev guy until they have at least a handful of employees and are working on a few projects concurrently. With that said, if he can bring in enough work, it may be worth it (and it should be noted that you will need a lot more than $3000 to keep you both afloat).

Also worth noting, equity in freelance/consulting companies is relatively worthless. Billable hours do not scale, so your revenue will be directly tied to the number of hours you and your employees can work. Because of this, you need to focus on making sure you get a decent salary/hourly wage as soon as possible.
So its a streaming Chrome 2 Phone.
A faster Internet — designed by computers?
Unless you want to work on your Macbook while watching a movie...
"All you need is Lambda".))
Is Chromecast Google's Miracle Device?
Finance shops typically contract through an outsourcing agency. Wipro, Tata and InfoSys are typically among the most prolific filers for H-1B, and those filings fell significantly in 2009 post financial crisis.
They make deals where they sell patents to East Texas shell companies but keep 90% of the proceeds from their shakedown lawsuits. That's what This American Life uncovered recently—they looked at just one (laughably illegitimate) patent, and found that hundreds of millions of dollars had been extracted using that one alone. I don't know how you could listen to that and not find the case devastating. If the broadcast was unfair, I'd very much like to hear the rebuttal. All TAL did was follow up on the example that IV themselves had given as exemplary of what they do, and it turned out to be shockingly unjust. So I do think most people here would disagree with their methods.
If I've understood the abstract and conclusion correctly, the message here is that people who are used to under_score identifiers read under_score identifiers more quickly than camelCase identifiers, and this is probably due to training.

I guess it's good we've got that established, at least.
Ever consider setting up a freelancing profile on oDesk or Guru or wherever, and getting paid to do interesting, challenging, different kinds of work of your own selection (more or less)?
> As others have said, one crude characterization of D/R split is that R is generally more supportive of spending for national security.

The split clearly doesn't work in this case.

I think the reason is that R is more concerned with privacy than D. Also R likes looking strong to other countries - this means spending on the military, they are not interesting in spending for the sake of spending. But the NSA fiasco does not make the US look strong in front of other countries.

D is more concerned with looking good in front of other countries (as opposed to strong), and the NSA situation doesn't do that either.

I suspect the ones that voted for it believe that the increase in security is worth the loss of face.
Many years ago I suffered nearly life-changing RSI pain. It happened in the middle of an extreme project where I found myself coding and running CAD for 16 to 18 hours a day, seven days a week for months.

The first good decision I made was to stop all work.

Next, I sought medical opinion. I was horrified to learn medical professionals were all over the place. I got recommendations spanning from surgery to vitamins.

I concluded that I'd do my own research and come to my own independent conclusions.

I focused on two areas: understanding the physiology or mechanics of the damage and taking a deep dive into ergonomics.

I came out convinced that the root cause was poor ergonomics. I had not caused enough damage to require surgery. I set out to test out various ergonomic products. Nearly all of them sucked. Gimmicky crap.

The ultimate solution was to design my own desk. The goal was to promote a fully relaxed posture with proper alignment and support.

The standard 29 to 30 inch high desk was designed in the dark ages for writing. Placing a keyboard or laptop on it throws your entire body out of alignment. Your fingers, hand, wrist, arms and shoulders end-up operating in tension as opposed to from a neutral stance.

My desk featured a dropped (about three inches) front section for the keyboard and thumb-operated trackball. I ditched the mouse as it caused too much tension. I found a thumb-operated trackball to flow naturally and comfortably.

A dropped keyboard shelf wasn't enough. The front edge got a solid piece of wood, 2x2 inches in cross-section with generously rounded edges. This created a forearm support across the entire width of the keyboard shelf. The net effect was that my hands very naturally drooped onto the keyboard and trackball. My shoulders were not unnaturally pushed up or pulled down.

I played with monitor height and settled for looking slightly down at the monitors (24 inch). I tend to alternate between sliding down in the chair and sitting up, which means that at times I am looking straight at the screens.

The end result was that all pain was gone and I could get back to work. I also took regular breaks every two to four hours based on flow.
Not OP, but in SC - email: einar@lcrnd.com
verisimilidude touched on a couple of these points already but apart from training your mind to not worry about pain you can also train it to type in Dvorak. I went even a little further and bought a $30 datahand keyboard (a really, really good price) but even with that dvorak'd wacky thing it only took me about 3 weeks of typing to get proficient and pain free. A good chair goes a long way as well.
I can't speak for the person you're replying to, but I would like to point out that RDBMSes are built on theory designed explicitly to handle general data problems. Situations for which the relational model is not a good fit are almost by definition special cases.

Similarly, while it is wise not to lump all of the non-SQL/non-relational databases together, to say that the bulk of them share a common obsession with scalability is not much of a reach. After all, we're not talking about Neo4J, FramerD, MetaKit, etc. We're talking about young systems that were born out of frustration with scalability issues. It's true that they all have different tradeoffs, strengths and weaknesses, but one significant advantage of Postgres is that it does so well in such a variety of situations. Maybe it isn't perfect for every scenario, but it's pretty good for most scenarios. This is partly an inherent advantage of age, and partly the benefit of a sound theoretical foundation. A big thing I dislike about the current crop of NoSQL databases is that you are expected to learn a great deal about their inner workings to make an informed decision about whether or not to use them. MongoDB really epitomizes this. But this is a pretty lazy complaint compared to random data loss and insane defaults (early days of Mongo), and I have to give you that.

Your position sounds quite reasonable compared to the one I've been primed by, but it's going to be a few more years before these databases mature to the point I'd consider one a reasonable first choice for a generic database. I don't draw the line quite as far as the GP—sometimes you have a special case and you need special tools—but I can certainly empathize with questioning the wisdom of making a distributed non-relational database the primary store for a low-load, classic RDBMS problem. But Twilio has come forward and agreed with that position and denying that they do that, so the spark for this flamewar is conjecture. While people have come forward to defend such a configuration, few seem to be endorsing it by using it themselves. This says something about the reasonableness of the idea.
> and let people ...let us know.

That virtually never happens. You have to do the work yourself.
Indeed, but rerere is tricky to explain because it goes hand-in-hand with a workflow that integrates topic branches via an integration branch that is not permanent ('next' in git.git). Despite its numerous unique benefits, it usually takes people a while to understand this workflow.
Calling Myhrvold 'evil' and putting himself in the same context as Hitler is absurd. One is a businessman whose tactics you disapprove of and consider to be unethical, the other instigated the murder of millions of people, over and above the casualties of the numerous wars that he started.
I don't believe the 100us saving by using kernel bypass such as OpenOnLoad is truly accurate, its more like 5us.

https://support.solarflare.com/index.php?option=com_cognidox... (requires login)
Congratulations, Geoffrey.

Been a fan since you originally launched the site way back when, and learned a lot from the videos I purchased.
Silverlight though did not have a new version released in 2 years but there updates even few weeks ago. I see video platforms only on silverlight.
Agreed; I like where I work, but it would be hard for me to turn down 2x what I'm currently making at just about any company. I suspect that is true for most people.
I'm curious of the motivation behind Issa's nay. I remember him being at the forefront of the SOPA rejection along with Chaffetz, Lofgren and Polis, all of whom voted for the limits.
Oh my goodness -- you too?!

I spent many a summer day matching blue paper against printed sheets and the occasional Mylar! I found the same
zone you're talking about.

Except ... did you ever get a paper cut and then reach over the ammonia fumes coming out the back? :-P
It felt like it was the other way around when this started.
Pelosi also happened to serve as the ranking member the House Intelligence Committee. The Intelligence Oversight Act of 1980 explicitly requires that the president keep congressional intelligence committees fully and currently informed of all intelligence activities, which means that Pelosi likely has seen more classified/NSA information than any other House member. She is also from perhaps the most liberal district in America.
All my sage.
Basic nginx Configuration
This is great. We need more public shitlists. Transparency in action!
For those who are interested:

http://www.thisamericanlife.org/radio-archives/episode/496/w...

http://www.thisamericanlife.org/radio-archives/episode/441/w...
Re-evaluation is easy enough when your computation is pure. But once you throw in some imperative effects, like adding a name binding to a symbol table, all of the declarative data binding frameworks fall down very quickly.

There is a lot of research in this area, concurrent revisions at MSR or self-adjusting computations at CMU to name a couple. Also, if you've seen Bret Victor's videos and wonder how any of those could be implemented for real, then this is where we need to go. It will be a fun trip though.