skysight-inc/HackerNews huggingface dataset:
Likely as a direct response to the hype of this article (a few thousand comments in the related reddit thread), Elon tweeted:

Battery "breakthroughs" need to state power *and*
energy density (not the same thing), plus how long
they last. They usually fail on energy.

https://twitter.com/elonmusk/status/585185843649716225
I'd say several reasons:

1) People are people and ingrained biases and social pressures are incredibly powerful forces.

2) The amounts of money are tiny ($1,000-$20,000) relative to a large company's operating budget. It's the same reason businesses overspend on airfare and SaaS products.

3) The hiring manager isn't spending their own money. It's no skin off their back if they pay a new hire an extra five grand.
I'm a bit surprised that you don't seem to have an equivalent of the Handysignatur [0] (eID based on mobile phone) we have in Austria. It's getting more and more popular here, I guess because all you need is a mobile phone (who has a card reader after all?).

I find it incredibly convenient as it gives you immediate access to a growing list of e-government services [1], as well as signing PDFs and even things like a service for cancelling subscriptions online [2].

[0]: https://www.handy-signatur.at/hs2/home.aspx?language=en

[1]: https://www.handy-signatur.at/hs2/?site=infos/applications

[2]: http://www.online-kuendigen.at/
This is also very true. The purpose of systems like Kubernetes/Mesos is to be set up once by a company, and for most developers to just interact with the CLI tool to run containers. Tools like Google Container Engine, make this into a software as a service product, where the cloud provider provides the API. In that world, as a developer, you never really think about the OS, just your app. But unlike in traditional PaaS, there is no framework that restricts what you can code (language, libraries, etc).
One of my favourite go-to phrases in health care is:
"Statistically significant, but a clinically insignificant difference."
I don't think you can prove that neither is true, but I rarely agree with myself to begin with.

I will not rely on the summary explanation, I can assure you of that.
Obviously it works better if it can find the exact image, but I don't think that's all that it's doing. For example, here's a picture of the Golden Gate bridge that I took myself from Angel Island, never before uploaded to the Internet:

http://bit.ly/1HJy0oL

It couldn't get the query, but it does get similar images, including at least one other that's also of the Golden Gate bridge. I unfortunately don't have any personal pictures of celebrities, but here's one of a slightly-askew photo of my computer screen that includes Obama's face (but deliberately not all of the original picture):

http://bit.ly/1CNk9wa

It managed to guess that one correctly, even though it didn't have the exact original image.
This is exactly the reason when working with my team on A/B testing, I'm always careful to use the phrase _meaningful_ difference (or not). With internet-based tests, the volumes of participants can be huge, so finding statistical significance is a hell of a lot easier than finding a meaningful difference. I like to say, "As N tends to infinity, we are guaranteed to find significance." The sad thing is that there are more testing platforms than I can count on one hand that introduce this p-value fallacy to users. They encourage things like repeatedly checking tests. I don't believe that users realize that the true p-value is oscillating around alpha. If your test isn't significant at them moment, just check a few hours later (it likely will be). Even with Bayesian methods, I've learned the hard way that you really have to be patient and let certainty accrue. More and more I'm lead towards Bandit methods for this reason. When sampling real-time data, you're in effect treating a historical sample as a part population with one part in the future --- that's a pretty dangerous assumption. My solution has been to guide my team towards large tests, work to _really_ move the needle (and have high statistical power). This is where statistical analysis has the best chance of providing certainty. In generally, with web experiments it's best to proceed with a healthy amount of humility.
Asymmetric Information is an economic inefficiency. On its face, it should be eliminated. Cato Institute describes a trend which appears inexorable.

Yet, Asymmetric Information does allow various agencies to attempt to add value by exploiting those inefficiencies. Remove asymmetry and we are left with perfectly efficient markets whose value accrues, not to the participants, but to the owners of the marketplaces: those who have access to sufficient capital to operate at scale large enough to drive down margins to where only they can compete.

My view is that agents, including individuals, must strive to preserve their economic advantage by jealously guarding their information streams and by poisoning competitors' streams with respect to data in which they have an economic interest.

Thereby, the inefficiencies of asymmetric information may be eliminated, as they should be. But the value of doing so will tend to be shared among all those who have an economic interest in adding value, by increasing efficiency. Thus a new information marketplace can be realised: one in which value from efficiency is distributed, rather than centralised.

To achieve this, massively decentralised information architectures are required.
Ha, I just did this. We built a VirtualBox VM with Vagrant and Chef then distributed the .box file. I think it worked pretty well, and we got good feedback about smooth installs, although there are a few small things I'd do differently to make updates easier.
Ottawa police get another year to crack Algonquin student's password
Nitpick: Comparing Rust's error messages and g++'s error messages, and saying that therefore Rust has a better toolchain, isn't really fair. pcwalton mentioned elsewhere in the thread that Rust's messages are based on clang's, which are orders of magnitude better than g++'s.
I work with Magento a lot lately. Very interested in hearing about this!
There's an old USGS paper on the increased seismicity around Lake Mead after Hoover Dam was built.

http://usgsprojects.org/lee/Rogers_Lee_BSSA1976.pdf

The Wikipedia page on induced seismicity has additional examples:

http://en.wikipedia.org/wiki/Induced_seismicity
I agree that using separate categories for git and GitHub doesn't make sense.
I was interested in the design decisions, but sure.

Lattice is a selection of Cloud Foundry components, principally the Diego runtime system, Loggregator log streaming system and Gorouter HTTP routing system.

If how software is written matters to you, then you might like the way we work. Cloud Foundry is Pivotal Labs DNA, scaled up. 100% pairing, every new line of code is test-driven.

We dogfood everything by running Pivotal Web Services as a public PaaS, which is always within a week or two of HEAD across the board.

Where we follow is that Kubernetes is extracted from real experience and Mesos has a head start on implementation.

In terms of design, I like ours best. Tasks and long-running processes are distributed using an auction mechanism, which means that there's much less global resource-status chatter required to make the scheme work. Diego is "demand-driven", meaning activity occurs when new demands are made. Mesos is "supply-driven", meaning state-affecting activity occurs when resources become available. They both solve a critical problem by pushing intelligence out to the edges, but to different edges.

I am much less familiar with Kubernetes, so I will avoid being any wronger than usual.
Hi. I've sent you an e-mail, can you confirm that you received it?
Regards,
I don't think it was a myth based on anime or otherwise. Japan did seem genuinely high-tech when I first arrived here 20 years ago. Talking elevators and high-tech toilets. Consumer electronics that were at least two years ahead of what was available in the US. Car navigation and mobile phones were way more advanced than in other countries at the time.
I'm am ex mechanic and I hardly ever replaced a relay. Even in the old Porsches I still work on as a weekend. The few I did replace were due to a fan motor going bad. Which made the relay overheat. But I did replace many solid state boards that would die from vibration or regular under hood heat.
Anything that touches our production databases, mostly sharded mysql, needs to go through our php orm.

We do have other contained infrastructure that is written in some other languages like go and scala.
A Mathematical Atlas
What is the performance overhead?
> But unlike in traditional PaaS, there is no framework that restricts what you can code (language, libraries, etc).

I'm not sure how traditional PaaSes are limited in that sense. Heroku accepts a wide variety of software through the buildpacks mechanism. Cloud Foundry supports both buildpacks and docker images, with clean extension points to add further mechanisms -- for example, .NET-on-Windows deployments, which is under development.

Disclaimer: I've worked on Cloud Foundry and I'm employed by Pivotal.
IMHO: HHVM/Hacklang are cool and i appreciate Facebooks contributions to building a better PHP enviroment... but at the end of the day, it feels like someone trying to put a V12 engine in a golf cart. It's cool if you are already driving a golf cart, otherwise it's weird.

So if you have the chance to start fresh: choose Java or Go. Or anything else... (define "performance"?)
Actually, I'd say the jitter is low enough that noise isn't really an issue here. Yea, you could drop every other point easily, but the meaning is pretty clear.
Be aware that while HHVM is more or less compatible with PHP now, there is no guarantee it will be in the future,and Hack is definitely not backward compatible with PHP. Not even talking about PHP C extensions.
Good grief, I was talking about referring to international postal codes as zip codes, which I thought was what this thread is about.
Because starting this month I need to work from multiple locations; and one of them isn't secure enough to leave a desktop.

I regret having a laptop at all (rather than the particular model I got)
Why aren't these tasks being updated at RosettaCode?
A Hacker's Guide to Hiring a Ruby on Rails Developer
It's possible that negotiation is the least bad option of what to measure, but that's a far cry from being a capitalist ideal.
Wait, what?

So tuition has gone up by 350%, but subsidies have decreased by less than 20% per TE student, at the same time that the number of academic staff has stayed roughly the same.

The only linked study says that tuition increases were larger in years with drops (in the tens of percent) in state funding, but the increases were not reversed when the funding returned, nor, in fact, did tuition even stop growing in those years.

Furthermore, the same linked study says that actual tuition revenue per student grew faster than ticket price tuition per student as colleges found other ways to maximise the revenue from students.

Yet the article still claims that declining state subsidies are a "key reason" for tuition increases?

I agree the NYT article was weak, but this one seems willfully ignorant of the implications of its own statistics.

NB: It's also interesting that the linked to study points out growth in operations as one of the largest cost centers over the time (the claim of the OP), but still not a vast increase. It doesn't include capital expenses, in an obvious way. So we're still none the wiser why costs have increased at 200% of the rate of the median family income over the period of the report (up until 2008).
What about The Book of Shaders?

It's not complete by any means, but will get there eventually, hopefully. :)

http://patriciogonzalezvivo.com/2015/thebookofshaders/
That's true. In my case I had plenty of tests for my application (that I ran inside the container environment) so I felt safe to proceed.
This does not help when you want to manage Arch or Ubuntu machines, since you're not installing ansible there, you're just letting ansible connect with ssh and execute Python2 scripts.

So, before being able to run your playbooks to do your provisioning/deployment, now you have to handle credentials outside of ansible, connect to the remote machine manually and install an old version of Python.

It's only a minor annoyance for me, but it could get worse.
Yeah, BK still pays the bills for our team. We're small though, I recently found out that perforce has around 250 people, we're less than 1/10th that. But we pull in millions a year, enough to pay our people above scale even in the bay area, so far, so good.

I'll admit we've fallen off the radar (well, we were never really on the commercial radar, the only "marketing" we ever did was getting Linus to use it and that wasn't intended as marketing, it was intended to keep the kernel from diverging like the BSDs did. But it turned out to be a form of marketing that has kept us alive).

We're gonna try some actual marketing. Stay tuned. We'll probably screw it up :) But we hired a marketing company, I've gone back to writing papers, we'll give it a try. If you have ideas on how we can put ourselves back out there, we'd love to hear them.

As for viable, heck yeah. We work well on big repos (better than git), we've got what we call nested collections of repositories (did I mention I suck at marketing, yeah, I came up with what to call it) that are sort of like submodules except they work exactly like a single repo, sideways pulls work, anything that works with one repo works with N repos, that includes all the guis, command line, everything. We've got an answer for binaries that works for gaming companies. We've got a sane user interface (that's what Mercurial copied, in a somewhat sketchy way).

Git is sort of like the wild west, it never met an idea it didn't want to implement (at least partially). We're more enterprise ready (yeah, over used term) in that we work hard to make sure that BK has all the guard rails, seat belts, etc, so that you can deploy to people who could care less how any SCM works and they don't drive themselves over a cliff. Definitely less cool than git in that we take away some (bad) options, but safer.

We have seriously considered open sourcing a version of BK. We've been doing a lot of performance work and we essentially have two BK's, the almost SCCS compat ascii format slow version (slow but any version of BK will talk to it), and the fast one with a new binary file format (stuff like show the top commit comments are 35x faster in the linux kernel, that number goes up as you add more csets). We considered open sourcing the slow one but that effort has stalled. It could be revived, it just has to be worth it to us.

The github ship, in my opinion, has sailed. Maybe we could have open sourced BK back before git and done a github thing but it's all flashy UI stuff and we sort of suck at that. We're really good at systems stuff (you'll see when we start doing marketing, we scale, git doesn't) but flashy? Not so much. We do our UI in tcl/tk (I know, I know, but we have one UI person who makes it all work on windows/linux/macos and tcl/tk is a big part of that. At least we wrote a C like language that compiles to tcl byte codes so we're out of tcl. Thank God.)
You are literally inventing problems that either don't exist or have an exceedingly small chance of occurring. Yes, a tornado could sweep through and blow the bust onto a passing baby stroller, but the saying, "don't borrow trouble," comes to mind.
I was thinking about doing something like this as a weekend project. I'm gonna use your and just have fun with it. Very nice work.
Of course, back then Japan had or adopted cooler tech than most of the rest of the world. The problem is that, at the same time, a high-tech, futuristic vision emerged and it was much grander than what was happening. That vision is the "myth" I am talking about. And then people were fixated on that vision while the means to achieve that vision was nowhere in sight. After a while, people give up and do these other things to pretend the future is here.
C++ isn't full of cruft, it's full of features. Many of those features apply only to a small niche, but those all those small niches add up to become an audience.

Much of the "cruft" of C++ stems from the template system. Rust has very sensibly decided not to go down that path. But aren't you happy that one language has sacrificed itself so that we can express ideas like this...

template<typename T, size_t A, size_t B, size_t C>
Mat<T, A, C> matmul(const Mat<T, A, B>& left, const Mat<T, B, C>& right) {
...

The actually useless features like exported templates and trigraphs, are removed.
Greg didn't reply but I think the answer is a resounding yes. I wrote this up a bit back when the devs were using BitKeeper. Lemme go find that. OK, ignore the "I want the 1995 era web pages" look and peek at this:

http://www.mcvoy.com/lm/bitmover/lm/talks/socal/

tl;dr: fan in/fan out scales great if you have BitKeeper or Git.
This is by far the most poetic article I've read on Wired
If this[1] is what you're referring to, it's because the acknowledgements would make things needlessly wordy.

[1]: https://www.gnu.org/philosophy/bsd.html
Android isn't a product for Google. It's a channel to route users to advertisements.
I showed up around 3:45pm and it was gone by then. NYPD were looking around though:

https://twitter.com/moyix/status/585181778438180864
A novel is not meant to be a police report. It's entertainment. It's a work of art. The point of art and entertainment is to provoke emotions and pleasurable sensations in the viewer's brain. In this way Pynchon creates a dreamy vivid world that's a plaything for the mind. Each sentence is an art object in a narrative museum.
TheGadgetForum – Compilation of the best technology articles on the web
Product Hunt for programming tutorials
No, it's not. Energy density is only relevant for today's uses of batteries - car's, laptop and the like. If energy density was all that mattered pumped storage would be utterly useless as it energy density is abysmal. The reality is pumped storage is 80% efficient, and is good for 10's of thousands of cycles (basically unto the dam silts up), and base storage medium (water) is dirt cheap. As a consequence we store and discharge gigawatt hours of energy using pumped storage every day, which I suspect more than all those batteries with higher energy density combined.

If you want another comparison, there are more vehicles using lead acid batteries than there are using lithium - yet lead acid has a horrible energy density. (You are thinking this is wrong - but you are thinking cars. There are far more golf buggies and indoor forklifts and the like out there than there are cars.)

They say the voltage of this battery is around 1/2 that of lithium - which I suspect means much than half the density. But Aluminium is cheap, more common and lighter than lead, and they are talking 10's of thousands of cycles. If this works it will change the world - regardless of it's energy density.
Awesome work, your avr computer is really impressive! So similar and yet so different! Emulating the Apple II was relatively easy, not a lot of extra hardware.

Haven't tried cross compiling anything yet, sounds really cool. Nice work on the Mandelbrot demo!
I found this paper to be quite interesting, but I have two issues with it.

1. At least at the beginning, it focuses excessively on the historical aspects of statistics. For example, it says that "most applied researchers are unmindful of the historical development of methods of statistical
inference, and of the conflation of Fisherian a
nd Neyman–Pearson ideas." To me, statisticians shouldn't /have/ to understand the history at all. For example, as a physicist, there is absolutely no need for me to understand the evolution of Ampère' theories, Faraday's theories, Maxwell theories, etc. to apply the laws of electricity and magnetism correctly.

2. The difference between p and alpha is central to the paper, but it doesn't seem to have a cogent explanation of what that difference is. (It's very clear who advocated for one and who advocated for the other, but that's not why the difference is important.)
Given that worldwide Internet adoption is still growing strong, it is conceivable that sooner or later a significant number of endpoints will only have IPv6 connectivity, or that their IPv4 connectivity will be limited to a private address behind a carrier-grade NAT.

Another point to consider is that there are things you can do with IPv6 connectivity that are very difficult/costly, or outright impossible, in NATted IPv4 land.

Personally, I'm waiting for the next generation of peer-to-peer protocols that make use of end-to-end IPv6 connectivity instead of hole-punching and proxying through third-parties. (Case study: ever thought how ridiculous it is that in 2015 it's still non-trivial to send a large file to someone over the Internet without using some sort of storage service?)

It's plausible that one of those new applications could end up being the "killer app" for IPv6.
Nah, man, I first came to Japan (from the Bay Area) in 1989 and it totally was like a science fiction movie. I then moved to Tokyo in 1994.

• weird giant TV screens all over the city, bleating ads at you while you ate in a grubby hand-built noodle shop next to a skyscraper (Blade Runner)

• super-advanced mobile phones COLOR SCREENS that you could PLUG INTO YOUR PDA AND DIAL INTO BBSes WITH! (Star Trek)

• toilets that sensed your motions and flushed for you (never saw this in a movie but I always imagined after seeing them that the toilets on the Death Star had to be like this)

• elevated trains and highways that passed through buildings and let you peep into tiny apartments so small they might as well have been Battlestar Galactica living quarters

• the badass cassette walkman i bought with an extra D battery attachment

• robotic vacuum cleaners doing the airports and stations while playing a creepy melody so they didn't scare you

... plus tons more like that. I had never seen any of that stuff in the USA in those days. It just doesn't really sound high-tech and futuristic anymore.
Xkcd: Operating Systems
That makes no sense. Android is no different to Windows or OSX. It is irrelevant which codec it uses. It doesn't benefit the platform either way to use VP9, MPEG2, H.265 or any other codec.

Sure there are royalty costs for using H.265. But one could argue that (a) Android already costs money due to Microsoft licensing and (b) there are likely patent issues with VP9 just like there was with VP8.
Have an upvote for making me laugh.

It's not as far fetched as you might think though, we've been building million cset trees and git is so darn slow that we made a "bk fast-export" that spits out the stuff that git wants. Because Git was over 20x slower just running the commits.
Or it makes it clear that the NSA is in fact, following the law.

Which as far as I'm aware, none of what has been revealed by Snowden has been shown to be illegal. Correct me if I'm wrong of course.
howsecureismypassword.com estimates a 26 character alpha numeric password (that I entered psudo-randomly) as taking 230 Sextillion years on a desktop computer to crack. So, that extra year they have isn't going to help much.

Following an IP to a Family house seems a little iffy to me. But I'm not a lawyer nor do I have any more information than the article gives.

If he's innocent I hope this wraps up soon and he can put it behind him. If he's guilty...
This is fantastic. Particularly helpful to me is the antipatterns. I've been playing around with Canvas for about four years now and I never knew to use clientWidth and clientHeight to fix the problems I was having using width and height.