skysight-inc/HackerNews huggingface dataset:
First of all, the FOIA process take a long time to go from request to release of documents. And there's all sorts of fudging along the way to either not release everything requested or redact what gets released. I'm sure even you agree with that.

Second, "cannot function in a modern manner"? If you're creating a public record, it's subject to FOIA. End of discussion. The point of FOIA is that you, as a creator of public records, cannot hide your work product from the people you serve. If you have nothing to hide, you have nothing to fear, or so I've been told.
A human "brain in a jar" (as in Motoko Kusanagi) may well be the ultimate fighter control system for a short window of time. (They would have higher G tolerance, lacking a long body to produce pressure gradients.) It would only be a matter of time before G tolerance and processing power were surpassed by electronics based AI.

(Not saying militaries would adopt this as standard. But for a brief time, such pilots would be the smartest, most G tolerant flying sentients.)
Often it goes both ways. Of the people who oppose it, most do so blindly and dismiss valid arguments in favor, while a minority understand the arguments well enough to reply to them.

Ninety percent of opinions are crap.
Real world recursion: "Lather, rinse, repeat."

More elaborate example: Most human languages are recursively defined, with sentence or phrase units able to be part of bigger sentence/phrase units.
It's definitely a circular issue. The ones most likely to complain are the ones most likely to join.

Kinda like a HOA. Who -really- wants to be on a HOA Board other than someone who likes to be in other people's business/exude 'pseudo authority'/complain (and in a minority, someone who has been so badly on the receiving end of same that they're determined to thwart the system from within).
Yes, me too, by early 1986 I had a BBC Micro (expanded with a Torch Z80 co-processor and floppies) a 286 based PC clone and a ZX-81. I even had an Eclipse S/130 with a pair of 10+10MB top loaders in my parents dining room, until they saw the electricity bill and made me return it to the repair shop I borrowed it from. I was ~19 at the time.
If you tried pentadactyl / vimperator extensions for Firefox I'd be surprised if you found anything you couldn't program that you can acheve in uzbl.
This library is a couple years old. I know Urbit is older but is Urbit's nock also as old?

edit: yes, at least 5 years old, but bloody esoteric http://moronlab.blogspot.com/2010/01/nock-maxwells-equations...
I really like Passenger for my dev servers, because you can easily run both Ruby (Rails) and Python (WSGI) applications under it. I'm not aware of another mainstream app server that offers that flexibility.
If you know the time frame you expect the market moving news to come out you can go short with limited downside by buying put options. You also get more leverage that way.
With all due respect to Snapchat's users and their puppies - they're irrelevant. Successful businesses function in one of two ways: they either create a solution to a problem that bothers certain parties and sell that solution to them, or they create a problem and then "invent" a solution. Any real business on this planet is about supplying something that you know there's demand for. If you know for sure that you want to be a big-problem-solver, then go for it, you'll find your market as you go. Also, this might serve as an inspiration: http://www.technologyreview.com/magazine/2012/11/
It goes a bit further back than the late 19th century:

http://en.wikipedia.org/wiki/Hydraulic_telegraph

4th Century BC!
What Do Samsung, Nokia, Xiaomi and Pebble Have in Common? They Copy Apple
1) It's a double standard. You don't have the power to enforce fairness in the interview process. You can only react to prevailing tactics in a way that best preserves your position. Your best options are to not apply to positions that post a range too low, and to not discuss salary at all until an offer is on the table.

If you already have a job, and the prospective employer asks you for your expectations, defer and delay. If they will not proceed without your answer, WALK AWAY. Otherwise, name a price 20% higher than what you would be happy with, and qualify it by saying that what you learn later in the interview process may merit a revision.

2) $10k is peanuts to the company. If they really can't afford to monetize your efforts enough to pay you what you are worth, they should really be up front about that themselves, and put their range in the ad.

Otherwise, any company above a certain size can pretty easily justify budgeting $200k or more in salary and benefits for even a mediocre developer. A mediocre developer will never be able to actually get that much because of market pressures, but if a company can justify hiring their own developers at all, they can justify paying a little more for a good one. That's why the logical progression is to first find out how much you will be worth to the company, and then determine the compensation package that makes you a profitable employee.

You don't want to work for a company that determines compensation first, then scrambles to figure out how to pay for it.

In summary, always make the employer say their salary number first. If they won't, they are already trying to cut the costs you represent to them, before even hiring you.

The fair wage is the most you can possibly get [while still earning profit for the company].
WetInk- Because writing classes/communities deserve better than forums/MOOC/LMS
What law did she break?

I don't say that as support, I just haven't seen any clear explanation of that yet.
They're also only 3 years long typically.
We don't hire a lot of post-docs from the UK because they are relatively less well trained due to the significantly shorter time spend in lab...
Indeed. And he was very selective and disciplined about what he chose not to do.

Many gurus are bad businesspeople. (What makes them a good guru contradicts the nuts and bolts of running a company) I'm glad to see how well he's done.
Just to be clear (not sure if you're kidding) but people use Passenger (and production application servers in general) not just because they meet some minimum throughput threshold.

Passenger takes care of keeping your application alive, makes sure slow clients don't break it, automatically handles concurrency and has low latency. That's just the basics, there's a lot of configuration options for the more serious deployments.
I detested homework at school, mostly because it involved writing selective passages from textbooks as answers. I was among the smartest kids in school, and yet almost never did my homework in time.

Best experiences were those I had in college when I was tasked to be creative and present on topics. This involved a lot of research, something which I enjoy.

My worst experience was when my school teacher shamed me, and made me do my homework in school while sitting on the floor. I was crying the whole time.

As a side note, one very cool lifehack from one of my friends (while in school): He used to skip saturdays (which were half-days anyway). He'd instead stay at home and do stuff he loved to do (mostly circuits and reading). I really found that an excellent way to inculcate self-learning. He wasn't skipping essential stuff at school, and I found this really neat.
And for files/folders, maybe have the icon change to reflect that there's a note attached (in the same way Dropbox modifies icons).

I think it's a great tool but I worry I would just forget where I had attached my note: to the root folder for a project, to one of the many project files etc
I read the page, but it's just a short introduction to some of the commands in gitless; and they're not at all different from git in concept either, except for the hiding of the index. It does nothing to answer "why" gitless exists, and why its creators think it's better than git.

I identified several points where gitless' UI is in fact worse than git and as such am not likely to switch, but I am still interested in the rationale behind gitless' UI decisions.

I often see people disparaging git's UI, but honestly, I can't see the problem anymore. Certainly there are weird bits (eg. git diff --cached) in the UI that I've learned by heart now, but I've also learned git's internals -- which doesn't require much investment at all since git is extremely simple -- and in light of that knowledge, git's behaviour is consistent and easily predictable.
Every detail you just described exactly mirrors my experience. The VP of engineering, the math puzzle I hadn't seen before, trying to solve it in a Google doc rather than with code I could compile. All of it.

I did end up solving it, but I wasn't happy with the solution and neither was he, with good reason of course, but it was one of those problems I easily could have solved if given the proper time to work on it rather than digitally whiteboarding it for 20 minutes in a high pressure situation. A quick and dirty solution is all you should expect from working on a never before seen problem in 20 minutes on paper without a compiler.

I came away feeling as though their process was more broken than my performance. Doubtless, I could have done better. But it just felt so strange to be washed out after four other engineers thought I was qualified.
Find me someone in the State Department willing to be the recipient and I will happily conduct this experiment. Why do you think it would be any harder to spoof an email to the State Dept than anywhere else?
I won't disagree that CryptoCurrencies have by and large been used for illegal transactions. Though, my response would be: So?

Any technology can be applied to do something illegal. Do you think this fact played 0 part in the Internet itself thriving? I don't see us scrambling to throw away steak knives just because some people have been stabbed.
Q&A with Mark Zuckerberg in Barcelona
>a minimal engine with plain helper functions that let you use, understand and talk to OpenGL

You can try http://libcinder.org , http://www.openframeworks.cc or http://www.sfml-dev.org
Wow, great advice there "just keep your mouth shut".

For anyone who has actually invested a large amount of time in a dead idea, the above poster is right on the money.

I think you should take you own advice and talk only about things you know intimately. Lest your sentimentality gets the better of you, when actually trying to address a problem that could suck OP's life down the proverbial toilet.
From The Fine Article:

"When Zhou began looking into the Toano, Virginia-based company back in 2013, he says he found online complaints about its Chinese-made flooring. So he bought products from Lumber Liquidators and paid to have them analyzed. The results led him to publish a post on investing website Seeking Alpha on June 20, 2013, that advocated shorting the stock because the tests showed levels of formaldehyde above California requirements."

So while others might indeed lie, we seem to have enough confirmation from the subsequent investigations that Zhou did not. And there was no reason to believe he lied, this is a target rich environment after all.

And while 60 Minutes is entirely untrustworthy (I've watched them lying on the air for decades, since the '70s), likely would have started with "guilt in mind", in this case they chose a worthy target.
It is a copout. But, the next step is realizing that this is one way people prevent change from occurring, change is uncomfortable and scary. I don't think it's particularly empathetic to get upset at people's common thought processes, even when they are bad. Try to remember we're all humans and life is hard and everyone is already trying.

Also keep in mind that the person saying it may mean it more as flattery - i.e., it may be a polite lie and they don't really think that. And of course, "I'm not smart enough to do that" is more polite to say than "that sounds boring and I'm super not interested".
London traffic through the Lens of Behavioral economics
What do you mean by your last sentence? Looking at simplest benchmark - Dhrystones both 286 and 68000 reach ~2K. Arm M3 does ~1K _per MHz_, M4 1.2/mhz.

We are talking Pentium 100MHz performance out of Arm M4 150-200MHz (freescale 150/st 168/nxp 204 MHz). Even <$2 STM32F103 (72MHz) is faster than Intel DX4 100MHz.

16MHz Atmels lasted so long only due to Arduino :/
I think the point is that mining is subsidized by "printing" new bitcoins, which currently make up most of the block reward.

Speculation is in theory not a factor, since spending $ on buying a bitcoin == spending $ on mining a bitcoin, so the price would be the same, if a rational market existed.
I disagree, I believe one should just state what they expect. It wastes less time for everyone. If you take a guy through two or three interviews, decide to hire him, make an opening offer that's near the top of the posted salary range, and he comes back demanding 1.5x-2x that, you've just wasted a lot of time for everyone.

I usually ask in the first interview what the candidate expects to be paid. If I slip and forget to do this, I'd hope the candidate would ask what we expect to pay him. Much better to do this than try to skirt around it -- weird questions like "what neighborhood do most employees live in?" would turn me off for sure.
I read a lot about how employees get screwed over with stock options, so what we decided to do was to just give employees vesting stock straight up as a buy through.

Basically the way this works is that we give new employees an up front lump sum in the amount of how much it costs to purchase the shares of the company. The employee then purchases those shares from us in line with a vesting agreement. All warrants and conversions are exactly the same as the founders shares.

This means that they pay tax on this purchase as regular income rather than capital gains up front with the money we give them for it. This prevents a heavy tax bill at conversion and allows them to retain their vested shares regardless of if they work for us or not after the first 12 month vesting period.

We calculated that the up front taxes are magnitudes cheaper in the long run because the increased valuation will cover those differences handily and there is no waiting period like there is with capital gains tax.

In the end though our intention was to make a simple way for our employees to actually own the stock we give them as compensation and it not be something that they can lose or be restructured easily. If a VC or acquisition wanted to restructure that away for employees then they would be forced to restructure everyone's, so we are all in.
Don't Buy It Top 5 Stuff I Hate About Samsung Galaxy S6
I don't remember any of that, either. The worst I've ever had was a silly bug due to operator precedence. Barring some truly uninspired things (like signed integer overflow being undefined), I really think most of those are cases one shouldn't run into, not even in a much more complicated situation.
Immutability is hardly a cure-all, see the discussion here for why RethinkDB moved away from it: http://www.xaprb.com/blog/2013/12/28/immutability-mvcc-and-g...

The reality is shared, mutable state is the most efficient way of working with memory-sized data. People can rant and rave all they want about the benefits of immutability vs mutability, but at the end of the day, if performance is important to you, you'd be best to ignore them.

Actually, to be more honest, reality is more complicated still. MVCC that many databases use to get ACID semantics over a shared mutable dataset is really a combination of mutable and immutable.
Hot Stampers
> On my machine, the dbmon app in Ember+Glimmer gets 10 renders per second, React gets 14. Not bad, way better than 0.1 per second!

https://twitter.com/ryanflorence/status/572991666090467330
Show HN: Hooks – Get Custom Notifications for Everything Important to You
> could you or him point me to any page in the C99 standard document where it is explicitly stated along the lines that the compiler "should assume" the pointer to be not NULL after an undefined dereferencing in line

You won't find a line that states it explicitly, but the standard does allow it.

If the pointer is null, de-referencing it invokes undefined behavior, so the program is allowed to do literally anything. That includes doing whatever it would have done if the pointer wasn't null. So the compiler is allowed to assume that the pointer is not null.
I would love to see a software like this that would help me take notes from Google Books and reference back the book and page number. Then it would be able to give me my notes sorted by time, tags or book.
Tools for Mobile Development
OS X reused the screenshot shortcut keys from the Classic Mac OS (System [n]) days. And back then, I think Cmd-Shift-1 and Cmd-Shift-2 ejected floppy disks, when there were such things.
I think it's another HN bubble thing, though. It's been a few years since I was out interviewing, so maybe it's different now, but I would honestly be shocked if I interviewed with someone who even knew what "Github" was. Obviously it depends on the specific field you're looking in -- if you're interviewing with startups in San Francisco, then sure, the HN view might be helpful, but the vast majority of companies are nothing like that.
> For anyone who has actually invested a large amount of time in a dead idea, the above poster is right on the money.

I think the issue here is that the above poster has probably not done his due diligence to actually verify the premise of this statement (that the idea is a dead one).

I could be wrong on that, but I see almost nothing in the post that refers to anything about his experience actually using the app.

For what it's worth, I'm trying to use it right now but I think the site is getting slammed by HN, so I can't actually use it. Therefore, I'm not going to tell the OP that he just wasted all his time and money.
It does vary a lot by school. Total cost-per-student has risen substantially at many universities, but is closer to flat at others. The University of California system is one that has had kept per-student costs close to flat, and in their case, tuition rises do seem roughly equal-and-opposite of state funding cuts. Last time I ran the numbers (2012), per-student state funding had dropped from historical levels of $25-30k/student to $13k [1], which explains where the ~$15k/student increase in tuition over that period could've come from.

[1] http://www.kmjn.org/misc/uc_funding.txt
Don't be too ready to listen to people's words of encouragement, unless they're telling you:

Shut up and take my money!!!
"bar() is invoked" is not incorrect. It's perfectly legal for a compiler to produce this result. It's just not mandatory that all compilers do so. There's nothing wrong with the question postulating that a particular compiler behaves this way; the point of the question is to remind the programmer that they have to expect and be prepared for variance between compilers when it's permitted by the standard.
"her" wasn't a sufficient clue?
Toothpaste startup hopes to brush away competition
You might find the recent paper "Algorithm Aversion: People Erroneously Avoid Algorithms After Seeing Them Err"[1] interesting.

> [...] Dawes subsequently gathered a large body of evidence showing that human experts did not perform as well as simple linear models at clinical diagnosis, forecasting graduate students’ success, and other prediction tasks [...]

> [...] cited reasons for the cause of algorithm aversion include the desire for perfect forecasts, the inability of algorithms to learn, the presumed ability of human forecasters to improve through experience, the notion that algorithms are dehumanizing, the notion that algorithms cannot properly consider individual targets, concerns about the ethicality of relying on algorithms to make important decisions, and the presumed inability of algorithms to incorporate qualitative data [...]

Note: I removed inline citations in the second paragraph to make it briefer.

1: http://opim.wharton.upenn.edu/risk/library/WPAF201410-Algort...
Tolong Nenek Terlantar, Para Polisi Ini Ajak Makan Bersama Di Restoran
Before that, our Founders had the object lessons of the crimes and existential stupidity of democratic Athens in the Peloponnesean War to warn them against too much "democracy".

As well as sharp minds, they certainly realized that "democracy is two wolves and one sheep voting on what to have for dinner".
A more promising model, used in some systems, is to think of a database as an always-growing collection of immutable facts.

That would already be a huge progress over how databases are currently used; if records were in fact immutable many problems would be instantly solved.
AP: Hilary Clinton ran own email servers for private address
Why would anyone want to delete emails, period? Anything government-related, HRC's emails included, should be archived ten ways to Sunday and kept forever.
One of the reasons that there's not a "nice easy wrapper" that you refer to is that the workflow of using git is very, very different depending on what your role in a project is.

When most people talk about the git workflow, they are thinking of the workflow of a feature developer - which is one of the simpler use cases. Let's think about git, however, as a tool for automating existing workflows, though:

Person #1 is a developer. His workflow looks something like "git fetch public; git checkout -b new-branch public/master; $EDITOR; git commit; git push incoming new-branch". His 'incoming' remote goes to a repository of everyone's unreviewed feature branches, and each feature is parented from the last commit that was in the public repository.

Person #2 is a reviewer. He has two remotes, "incoming" and "reviewed". His workflow is "git fetch incoming; git checkout incoming/branch-to-review; git log --stat; $VIEWER; git push reviewed branch-to-review"

Person #3 is an integrator who's responsible for the state of the 'master' branch on the 'public' repository which is visible to everyone. He only wants to merge reviewed branches. His workflow is "git fetch reviewed; git checkout master; git merge reviewed/branch1 reviewed/branch2 reviewed/branch3; $BUILD_AND_TEST; git push public master".

This is the sort of real-world use of Git that goes on in large organizations. It's actually harder to think about using Git in a single-developer project, because one person is playing the role of developer/reviewer/integrator, and typically doesn't think consciously about what role he's in at any one point in time: so his workflow is sort of a mix of all of the above, which ends up being overly complex.

Tools like SourceTree really don't help the situation either, because they try to give you a graphical interface to git commands in general (since they don't have any insight into the development process for a particular project).
We've moved past the "Bitcoin will die" phase to the "Bitcoin may not be the largest technical innovation since the internet" phase. I'm okay with that.
I don't know how much this thing will cost, but you can get any ST Nucleo board (up to Cortex-M4, detachable ST-Link programmer/debugger and headers for all I/O, including Arduino headers) for $10. Hard to beat that.
Issues in regulating robocars, and the case for a light hand
Photograph of light as both a particle and wave
How and where did you market the app ? google adsense etc
Maybe transparency-adverse public officials are the target market for ownCloud?
So frustrating that here in the US, you can't even buy those individual components for that price, even if you buy them on reels.

I'm not sure if it's the distributor's profit margins, counterfeit parts, yuan-to-dollar advantages, or what.

Probably a combination of all that and more.

I doubt the STM32F103 is a knockoff though.

And they cost over $3 here in the US even on reels of 2400 pieces.