skysight-inc/HackerNews huggingface dataset:
The real problem with these programs is that they are designed with a hard cut-off point rather than reducing the compensation at a slightly slower speed than private employment ramps up. For instance our tax system works in a rational fashion: you pay say 0% on the first 8k, 10% on the next several thousand and so on. In this manner, you are never disincentivised from trying to get more money because it's always positive (though more inefficient money accumulation wise).

What I don't understand is why we don't have programs (say unemployment benefits) where when you finally get work, the money you earn above the cut off replaces need based compensation dollar for dollar until you're free of the system. It makes no sense to cut people off the soon as they get a job when the job pays less than the program.
Fair points, though I quite like the concept of a "variable containing a library" (or module).

Personally, with JavaScript being the first language I seriously learned, it's intuitive for me to reason about. JavaScript is built around closures, and you're simply importing a closure that returns (exports) its public interface.

In fact, the main issue I have with ES6 modules is that they differentiate a "module object" from its default exports, which can be tricky to reason about (basically, what I wanted from ES6 modules was just syntactic sugar over CommonJS, whereas what we have is more powerful but more complex).
https://wiki.mozilla.org/WebAPI has a list
Thank you. I've always wondered what the correct spelling was. I've seen both ways here and now I have a firm answer.
this gingko app makes no sense to me.
Which is a step in the right direction. After that they can make it multithreaded. Right now it's all too tied together.
Samsung’s newest TV lets viewers watch different HD programs on the same screen
I's movie
Node is not really tied to Joyent. Actually, a good amount of the core team is at StrongLoop.

Joyent has basically got it as far as they needed it to get for their own uses. Now they are just sitting on it and keeping it stable while letting userland modules cover future expansion.
> Synchronous child process execution is being added, at long last.

Thank the jesus. This will be nice to have, especially for some command line and filesystem operations.
What's your citation for the claim that the CIA denied ever creating a file? All I see is denials that the file existed at the time of the FOIA requests, and nothing to suggest those denials were untruthful.
Because that's not why I wrote frak. Originally, I wrote it to help eliminate backtracking and, indirectly, minimize the state table of two enormous regular expressions within Vim's Clojure syntax file (the README has a link in the "Why?" section by the way).

Vim uses an NFA style engine and it was obvious to me that backtracking with these patterns would be an issue. Since we went to such great lengths to provide the most accurate regular expression highlighting possible for Clojure, which is pretty damn accurate, I figured we might as well try to make it performant. It turns out our efforts were not in vain.

Have a look at this pull request: https://github.com/guns/vim-clojure-static/pull/28.
> On current hardware (a.k.a. the last 10 years or something), showing a flat picture or a rotating 3D object consisting of a small amount of vertices has no significant power usage difference.

In properly optimized software, yes. In current browsers? We're not there yet. In firefox I get maybe 10fps on these animations, and in all browsers it causes a minor temperature spike that h264 video does not.
We're using Mandrill - inbound email to boards.trello.com is routed to them, they parse the email into JSON, and then they POST data to us. They do spf/dkim validation for us in addition to the parsing. That said, that might be a bit heavy for your use-case.
It mirrors my own opinion when I jumped in to try programming for the windows 8 app store last year. WinRT is so restrictive that microsoft can't even publish their own office software on it. Even Apple knew better then to completely cripple their desktop app store.
Actually, pretty much, yes. That's the thing about irrational models: if it's not constantly reinforced, people start to question it, and then it all falls apart. The modern notion of self-esteem is no different.
Probably because you don't have enough reason to finish it. If you had users clamoring for you to finish the project or a boss then you would probably finish. I would suggest doing something similar to agile. If you know you can't work on something more than a couple of days set a 3 day sprint only add features you think you can finish and add the rest to the backlog. complete your sprint. if you feel your upto another sprint start another one. Also, find others you can work with that depend on you(customers, teammates rtc.). Most people work harder for others that depend on them than for themselves.
Most servers are doing pedestrian things like VMware, Exchange, web etc. and people buy server hardware for the RAS features. I'm saying apps and hardware you reference are uncommon.

games was an example perf critical code that seldom benefits from numa optimization.
Get back to me when you can explain why the "Android is Better" link was on the page for practically a split second the other day, despite people commenting on it after it disappeared off the front page. There's far too much fanboyism going on here, on both sides.
> Am I missing something? Why is the one-process-per-tab model considered "severely" superior?

I'm not sure process-per-tab is "severely" better. However, how are you measuring that 1.6 GB? If you're not careful, you're N-counting the copy-on-write pages that the processes are sharing. Even chrome://memory-redirect has a note that Chrome itself has a bug with N-counting its RAM usage across tabs. (Issue 25454) The RAM overhead of process-per-tab is more than the fanbois will tell you, but it's much less than you see by adding up the sizes you seen in top/taskmgr, and is less than seen in chrome://memory-redirect.

Sandboxing for security and fault tolerance is a big deal; it's certainly worth the difficulty in figuring out how much RAM is actually being used by N tabs, if that's your main complaint.

Edit: I'm notorious for browsing with 30+ tabs open. I currently have 48 tabs open, and I'm not noticing any ill effects from high RAM usage. I really wish there were a keyboard shortcut for pushing the address of a link onto a temporary bookmarks stack, and another shortcut for popping a bookmark and opening a tab.
Just divide the yearly cost by the rate of interest or inflation. $10 billion divided by 3.71% yields that $270 billion figure. Use whatever mental shortcuts work for arithmetic in other contexts. There's no need for an actual infinite series.

Explaining it the other way around, if you had $270 billion now, you could fund the NSA by $10 billion per year in perpetuity based on the interest. That's a simple calculation of $270B x 3.71%.
Thanks for your comment, as I clearly had erroneous preconceived notions regarding this subject.
Getting government support for the project is part of the risk and cost analysis, and I don't believe it would amount to a very large percentage of the total cost.
My understanding of the logic behind it is that HSR will begin by building a short link between two unimportant destinations at great expense; Musk is trying to upend that idea by building a longer, more useful link between two great destinations.

You are right to say that comparison of LA-SF Hyperloop vs. LA-SF HSR is unfair; we should be comparing LA-SF Hyperloop to Fresno-Bakersfield HSR. For both projects, these would be their respective first stages.
I don't use anything from Google or Apple. I have a Windows Phone, host my own mail in Luxemburg, and don't use any cloud storage. I can't imagine why anyone would use Google.
"How I Got Wed for Less"
MacBooks were manufactured from 2006 to 2011 with a wide range of GPUs.
You can use fibers. We are doing that via common-node (https://github.com/olegp/common-node/) and are very happy with the choice at https://starthq.com
“I was going to buy an outfit, but it was so hot.”

TL;DR Talk about First World Problems.
When my co-founder and I were the only full-time folks at our startup, we subscribed to individual insurance plans with Blue Shield of California. We had some high deductible plans so we were covered in case of a major accident but had to pay our own way for everything else. I think it costed about $100 per person per month, which seemed like a steal. Fortunately, we did not end up incurring any major medical expenses while on that plan.
You're right, the poor and needy were so much better off before government welfare programs. Ha ha ha ha ha.
> If you think you are running a server/service that violates their TOS for a personal account

That's the problem. I have no clue whatsoever if it would violate their TOS. The TOS is so vague as to be meaningless when it comes to figuring out if a noncommercial use is banned or not.

Whether a rule is vague is not binary. They can leave themselves some wiggle room while still providing rules that can be understood.
> At least when the Tea Party criticizes the government, the government doesn't pull the welfare checks of its members.

Nope, they just nail them with a tax audit. Power corrupts regardless of who wields it.

Also, I wasn't proposing theocracy. Read what I wrote again. You weren't paying attention.
An answer in one link: http://www.dataliberation.org/
Zwiebelfreunde take over popular onion.to Tor gateway
The longest TGV and Shinkansen consists are around 400 m, so they pass a given point in 30 seconds at about 50 km/h (30 mph). Of course there's spacing for safety and so on, but 50 km/h is so low that it's really a factor in practice unless you also have non-HSR traffic on the line.

A bigger factor in practical capacity is loading and offloading people and switching near termini.
For those in the same boat: the BBC article talks of a design where maglev trains, starting in city centers, accelerate to a few hundreds km/h and then get picked up by a huge flying wing that swoops on it like a bird of prey. Later, much farther away, that flying wing will put the trains back on a maglev track, without ever landing.

See also: http://www.core77.com/blog/transportation/flotspotting_u_of_...

That truly is a toy for boys (as in "looks cool and dangerous") unlike the Hyperloop ("it may or may not be dangerous, but you can't see that, so who cares?")
http://www.egr.unlv.edu/~larmore/Courses/CSC477/monge.pdf

How? That is an algorithm for a completely different problem, which is not obviously reducible to this one.
Smartphone pictures pose privacy risks
Hah ... I'm glad he posted this and it subsequently made it onto HN. I got the same email last night and have been dreading trying to log on to figure out how in the heck to cancel the account. I had a similar confusing problem canceling an azure subcription, xbox live indie games subscription, windows phone store subscription, and zune music subscription in the past.

edit: it gets worse, unfortunately. I followed Frans' steps and tried to chat with a support tech. I didn't notice when they came on after a while and so they closed the chat session. Fine, my fault. So I went with the "call me" option. After a while, I get the call, and the first lady was really nice, but informed me that she couldn't help me. So she forwarded me to another number which ended up being MSDN subscription support. After I got on with someone there, they informed me that they couldn't help me and that I had to do it online at orders.microsoft.com/history (the http version is a 404, so I had to figure out to put in https). He was clueless otherwise, so I hung up and just tried to go back and initiate another chat conversation. That is unfortunately erroring out with a 500 server error. What a CF :(
I'm glad I decided to click this link.

I have a vested interest in this whole debate, being that I went ahead and bought a month's supply. After reading Rob's blog throughout the development of the product, I'm not as much worried about the "almost dying" and rampant self testing, as it seemed an honest and open process. He was solving a personal problem in a complex area and tested his solution on himself constantly. From an amateur science standpoint, a well documented approach such as this is better than most. I also am not as concerned by the full diet replacement route, as I only ever planned to replace breakfast and/or lunch most days.

The critiques that concern me from this dietician are those about the source of weight-loss coming from too little protein (the daily recommended amounts are clearly under anything I've ever heard from modern nutritionists; including a NASA nutritionist), the medical meal replacement this is based off of being woefully incomplete, and the possibility that the founder actively shuns criticism from dieticians/nutritionists.

The first concern can be supplemented with another protein source, but the other two definitely mean I have more research ahead of me. I'm glad the author in those comments included a different meal replacement formula to compare against. At the very least, the commentary provided has many small things that could be incorporated into my own Soylent to improve it (carnitine, spirulina, etc.)
Wow, work and support themselves! What an idea! I can't believe nobody thought of that! You must go to New York immediately and tell all these people!

Seriously, though, I'm pretty sure they've already had that idea, and I'm pretty sure there are reasons beyond laziness why most of these people haven't carried it out.
Have a look at node.native. It's just libuv and c++11, which behaves pretty much the same as node. But much lighter, and with no Javascript engine tacked on. Obviously not nearly as stable and supported, but it's an example of how c++11 can work very similarly.
It was so, so easy to move on from Reader, which is why I think the shutdown was not such a big deal.

Google gave months of advance warning, and made it easy to export your feeds and data in a cross platform, open format. The fact that their API was open for other clients to use meant there was already an (admittedly limited) ecosystem of feed-reader UI apps that could pick up where they left off, such as Feedly and TheOldReader.

You lost a good product when Reader shut down, but you didn't lose the kingdom by any means
That's great, but it's not without cost. Here, the cost is you end up with deeply-nested directory nodes (which breaks Jenkins ability to properly purge the directory after a job). Node modules are also extremely liberal in the number of files they create -- even a "simple" app using just a few common modules could end up with 1k+ extra files. This can produce problems in your IDE, as well as with your source control or continuous delivery systems, among other things.

So, it solves some headaches, and creates others.
There is probably somewhere in the world right now an aspiring plutocrat screaming into a mirror "Release the drones!", you know so they can really nail it when the time comes...
What are the sites where one can find SaaS coupon codes and offers? AppSumo, F6S, TNW Market - any others? We would like to aggregate them at https://starthq.com
If you changed the file to state=delete it should store the fact that file should not exist though - that would avoid this problem wouldn't it?

Granted you're trading in a bit of convenience for having state controlled in this way -everything would have to go through your config tool (ansible in this case) - I found commenting out tasks after I was happy they were complete in order to experiment with the next part of the config was a good way to make config changes like this painless and quick though.
I use a master password with Firefox; part of the reason I don't use Chrome is because it doesn't have a similar feature.

But this shows it's even worse than I thought. Security in depth. Encrypt the hard drive, encrypt the home directory, encrypt the browser password storage. You're basically advocating shallow security.
The day after thing with Dr. Who is because it's airing at the same local time in the US as it does in the UK I believe, which is perfectly reasonable to me, i'd rather not have to watch it at something like 5am :)
For someone who is not too familiar with the Clojure world, how does this compare to test.generative[1] (which I heard about in a talk[2] about Simulant[3])?

[1] https://github.com/clojure/test.generative

[2] http://www.infoq.com/presentations/Simulation-Testing

[3] https://github.com/Datomic/simulant
I applaud the Node developers for their effort. While recent "competitors" like Go are fascinating and in some ways even arguably better, the fact that every device on earth runs JavaScript makes me bet that Node will prevail.

Computing will need to move fluently between the cloud and the terminal, and JavaScript is the only language which allows you to use a single codebase for both (in the foreseeable future). As developer time will stay the biggest expense when developing software, I am bullish on Node and JavaScript.
In the Java world, OSGi takes care of that and much more.
hmm, wouldnt it be better to link to some examples instead of the implementation?
That is an absolutely disgusting attitude.

True innovators carry all of humanity on their backs, and give massively to all of humanity, present and future.

The fact that they get some monetary compensation doesn't entitle you to not be grateful and to not recognize their heroism.

It does not entitle you to imply, as you have, that they deserve the same level of praise as any person who is paid for any work whatsoever.

You are, by implication, equating Elon Musk to the teenager flipping burgers, or any other menial laboror.

That is moral treason.

Without innovators, we would all be dying in pestilence-ridden Stone Age villages. In my opinion, those who claim that innovators do not deserve the highest of possible praise _deserve_ that fate.
It probably would be fairly straightforward to write a generator that wrapped every function in a module with Q.nfcall.
...some with hate you for it...

I find that proofreading my writing helps to avoid such errors...
Not the original point perhaps, but its come around to that. A couple years ago they settled on callbacks after a fairly active debate, as the least ambiguous option for continuation passing. As more people explore Node, callbacks are one level of abstraction too deep or just too tedious for some people. Fortunately there's a great selection of asynch modules to help them.
This is a cultural problem, not a module management problem per se. Blame the author of module C, not the package management system.

Semantic versioning's raison d^etre is to prevent these sorts of issues. Reusing a major version number is supposed to constitute a promise not to remove or change the call signatures of any functions published by your library. This is necessary so that a dependent library can declare a dependency on version 1.x.x of your library when version 1.1.0 is released, without having to worry that version 1.2.0 of your library will break things.

The problem is that too many library and module authors (who are otherwise talented, or are simply the first provider of a useful library that ends up gaining traction) refuse to follow the rules, and there's no effective sanction in the OSS marketplace for this sort of antisocial behavior.

As soon as backward-incompatible change is introduced without bumping the major version number, the dependent module author becomes paranoid (and being closer to the user, he's going to wrongly get a disproportionate amount of blame), and (rightly) feels he has no other option but to declare a strict version dependency. And when there is more than one dependent module involved, the misbehavior of the independent module author can cause a dependency graph that is impossible to satisfy.

As far as I can tell, this whole situation started with Ruby, and is the main reason (along with second-class documentation) why I am generally averse to its ecosystem. rvm and its ilk shouldn't even have to exist.
That's what semantic versioning is for. Node modules should continue to move forward, and reinvent themselves to improve how we write our apps. Otherwise it'll just turn into another PHP.
Sorry, that ogg was borked. At least I cannot play it anywhere. Will replace it with a standard Ogg Vorbis one.
Social Flow Down
It is a shame, but I just don't know how node would migrate to ES6 modules. I'm sure someone smarter than me could think up of a plan, but it seems like a huge amount of work. One of the strongest points about node is the amount of small reusable libraries available. They aren't about to ditch that.
Is this a file locker or cloud storage service?

The entirely web-based interface suggests the former, in which case the storage limit is curious. Other file locker services have allowed users to upload and share effectively unlimited amounts of files for years.
I thought that once, and the company wound up getting acquired by a huge company at the 8mo mark.
A good start, but I want to add more.

This may seem unrelated, but there's a difference between poker and slots. Both are "gambling", but one has a performance effect and one doesn't: if you're good at poker, you can make money at it (of course, many people lose). With slots, there's no skill. If it's viewed entertainment, fine; but don't think it should take a major place in your lifestyle because it's just going to lose you money. Playing slots is not a sound financial move. For some (top ~2% of poker players) poker is.

I'll get back to that.

Now... let's say that you're a typical 28-year-old programmer making $120,000 per year in a cushy corporate job. Your financial advisor comes to you, one day, and tells you that you should invest $30,000 of your annual income in penny stocks. Not only that, but it's a single and illiquid penny stock, with tax implications you don't fully understand. Oh, and the company issuing it is your employer and has about a 20% first-year chance of firing you without severance ("for performance" because tech startups never do an honest layoff; they'd rather hurt your reputation than theirs by admitting contraction) and invalidate your investment (called "cliffing") outright. That's your financial advisor's proposal: buy illiquid penny stocks from your boss.

What would you do? You'd fire the fuck out of that financial advisor, that's what you'd do.

Yet there are plenty of people who'd work for $90,000 (instead of the $120,000) plus "equity" whose expected value is much, much less than $30,000-- maybe $10-15k at-valuation, from the perspective of VCs who have a much higher risk tolerance, who also get control of the company and preferred shares in the deal.

It's a shit deal. Don't take it.

Now, back to poker vs. slots. If you're a founder, your equity holding (which is likely substantial, unlike typical employee bullshit) is more like poker, because your performance at your job can have a macroscopic effect on the company. Your ability and performance directly affect your payoff (of course, there's a lot of luck, too). You're still gambling in the abstract sense that everything (even driving) is a gamble, but you're taking bets on yourself, which any self-respecting person would do.

If you're an engineer or, really, anyone outside of the top O(N^0.25) executives, you're playing slots because nothing you do will have a real effect on the macroscopic performance of the firm. You're betting on people and factors over which you have no influence. Even whether you get that full that 4 years or are fired first is (let's be honest here) outside of your control.

Employee equity is a nice-to-have for an otherwise good job paying a market salary (if not above-market, to account for startup risks) but it doesn't justify taking the kinds of pay cuts involved at most of these startups.