skysight-inc/HackerNews huggingface dataset:
I thought you would have reported the issue before/at the same time as the blog post. My opinion's that it sometimes works out better if I get in touch with software developers first, in case there is a known issue and/or workaround.

I say this because most posts about issues we experience don't end up being on HN, and add a result the powers that be either don't hear us, or by the time we've logged issues and gotten the problems resolved; there's no longer enough time to spend another week migrating again to WT.

If the issue isn't resolved by 3.2.10 as mentioned elsewhere, I hope it gets resolved soon so you can get that 7x throughout improvement.
He's wrong about one thing: this girl prefers the bigger "jacked" guy.

As a woman who's into fitness, the real key is: don't be fat. If you are slender, a small amount of muscle goes a big way. And fat guys rarely get the pretty girls.
Well, we've established we have differing hardware and differing requirements from our computers.

The wifi modules were a generic device with a Ralink/Mediatek chipset, and another TP-Link branded device. I don't recall the specific webcam verson, it's an older Quick series one that really should have worked.

> I had a great experience the other day when I plugged in my ancient CanoScan LiDE 200 scanner I bought back in the Windows 2000 days

In general this is a situation where Linux shines, because hardware tends to remain supported much longer as long as there's someone willing to keep the driver compiling. With TWAIN scanners it's a lot easier of course.
Your first photo is of paramilitary police in a country fighting a civil war.

The second photo does not show any militarism.

The third photo is, sadly, from the USA.

The fourth photo is from a police state (Russia).

I don't know the context of the fifth photo but it looks like it may also be from the USA.
OpenSSH?
Roger Waters Rips Donald Trump at Mexico City Concert
Not quite; the author states the MongoS nodes were SIGGERM'd. This is unrelated to WiredTiger (which runs in MongoD), and more likely caused by the Linux OOM killer or another resource limit being exceeded (like the number of threads or sockets MongoS tries to open). This can happen if the application is configured with larger connection pools than the limits imposed upon MongoS; e.g by calling ulimit).

The above scenario can easily happen if an end user's application doesn't take all resources into account (e.g. a web applicstion that accepts as many requests as possible and as fast as possible, and opens as many database connections to MongoDB as possible). In that situation, if MongoDB can't keep up, the application logic may keep accepting HTTP requests and generate even more DB requests. If this was indeed the case, MongoS would have been the bottleneck, thus SIGTERMs.

The crux of the actual problem they're having with wired tiger may have been due to a misunderstanding of performance expectations or configuration.

EDIT: it appears to have been a bug in this case; not the expectations or configuration I initially implied. My point about application design still stands; an HTTP 500 message is much better than submitting more requests to an already overloaded DB.
Those are absurdly high figures for a range safety package - it's a self-destruct system, meant to terminate out-of-control flight by making the platform no longer airworthy. You don't need a Mark 82 to do that.

Indeed, a firsthand source [1] describes the QF-16's range safety package thus:

> A small ball of flames burst from the middle of the aircraft, followed by thick black smoke, but no sound. The sound followed soon after with a deep reverberating boom.

> The extent of the damage went undetected at first, due to the amount of smoke billowing from the wreck. Once it cleared, it revealed the F-16 had been split in half between the cockpit and the wings.

Something on the scale of a 500- or 2000-pound bomb, as this random forum commenter suggests, would've scattered pieces of aircraft all over the hardstand, in which it would also have left a hole.

[1] http://www.defense-aerospace.com/cgi-bin/client/modele.pl?pr...
The issue has never been about price.
You're wrong. Absolutely, undeniably, wrong.

A party simply can't change the license for code that they did not write. They can only change the license for their own work.
A proposal of new concurrency model for Ruby 3 / Koichi Sasada
Linux Bcc Tracing Security Capabilities
The 2.5lb increments/week seems unrealistic. If you can increase weight by 2.5lb/week over any sustained period, it most likely means that you started with too low a weight. A 2-3 week increment cycle seems intuitively more likely to match actual strength gains. I'd be curious to hear others' experience, or any references on the subject.
0.50 caliber sounds more like the canopy.

Minor correction, from Wikipedia, with references: The armor has been tested to withstand strikes from 23 mm cannon fire and some strikes from 57 mm rounds.

References:

Donald and March 2004, p. 18

Jenkins 1998, pp. 47, 49

Note "strikes", not shrapnel. The armor thickness varies. From some angles, the cockpit can take a 57mm shell. From other angles, it's only good for 23mm.
About the Explorer bug, I've had it for years in Windows 7. It's inconvenient, especially when coding. The (very) short workaround is to rebuild the indexation.

I'm sad to hear it is (seemingly) still present in Windows 10.
Yes, I'm familiar with SDE, but thanks for mentioning it. The SafeTSA I mentioned was one of Michael Franz's later contributions to the field. SafeTSA was an SSA representation capable of expressing all of the security and other semantic constraints of the Java language. Michael Franz's group took the Jikes RVM (then known as Japapeno) and added a second front-end to the JIT that could read SafeTSA, so they could test performance of programs running Java bytecode and SafeTSA in the same process. SafeTSA both took less time to go from bytecode to native code, but also the resulting native code ran faster.
Musk: “Particularly trying to understand the quieter bang sound a few seconds before the fireball goes off… May come from rocket or something else.”
Very interesting article but the title is clickbait at best and Big Brother propaganda at worst. The NSA is still as strong as ever in Oakland. Corporations are still selling spy cameras and microphones disguised as cell phones or entertainment centres. The population is still distracted by the lottery and by sports and by politics. Big Brother plays tricks where it makes you think you're not being surveilled by 'losing' public battles. But it does not lose. Articles written to make the citizens feel good about the current state of increasing surveillance are likely written by friends of Big Brother.

Neither Oakland nor any other US city has, or ever will, "beat" Big Brother. Not unless there is global systemic change and current surveillance powers are ended.
MIT is not copyleft. If you can sublicense MIT to be proprietary (which is what most people consider to be a "benefit" of the MIT license) then you can also sublicense it to be under the GPL[1]. The GPL does not strictly provide more rights than the MIT license.

[1]: http://danashultz.com/blog/2010/10/19/what-is-a-sublicense-a...
Look, the Air Force has plenty of real combat drones with actual remote weapon controls. This is simply a target drone program to follow up of QF-4 program since we are running out of old F-4s. No sane actor would do anything you suggest since there are purpose built drones that have actually been used to do weapons release. We have enough existing ability to drop weapons that the new Navy drone will actually be used for refueling missions to keep the hours off the F-18 airframes.
- You'll look like a developed man, rather than like a permateenager. This is nature, not artificial standards

- Greater bone strength AND flexibility, preventing posture issues

- You'll be perceived better in your development team when it comes to leadership, arguments, etc. It's hardwired in us

Seems like a deal to me!
The same documentary with a different name ;) Never have twins, your brain is useless for quite some time afterwards...
You don't necessarily have to be charged yet if you have concrete plans to do something that is prohibited and you want to challenge the prohibition (I don't enough about this case to know if it qualifies). Otherwise the only way to challenge these laws would be to risk a serious criminal prosecution: http://federalpracticemanual.org/chapter3/section2 (see 3.2.B).
This is beautiful, but there's a more direct link here: http://3d.si.edu/apollo11cm/index.php
You are implying that Apple added absolutely nothing to macOS since 2010 that wasn't useful to desktop-/laptop-only users, or that there've been glaring omissions of functionality since 2010 which they haven't addressed or aren't about to address, without giving any examples of either. Heck, they just announced a new and modern filesystem! Coming next year! [1] What about systemwide support for Wide Color? [2]

It's a free OS, it gets major updates every year and minor ones every few months.

Even if the spotlighted features of every release (like Siri this year) aren't exactly appealing to you personally, what most people seem to overlook — odd for a place like Hacker News — is that every release of macOS also includes many new native APIs for developers. Not to mention subtle new accessibility features, which most of us may hopefully never need but it's nice to know they are there for the people who do need them.

[1] http://arstechnica.com/apple/2016/06/a-zfs-developers-analys...

[2] https://webkit.org/blog/6682/improving-color-on-the-web/
The Apache 2.0 provides an uneven patent grant. Specifically, it's directed from users to the developers. The GPLv3 makes the patent grants much more copyleft in style to ensure that users cannot be attacked by patents from developers as well.
I've been following Justin on Snapchat for a few months now, and this blog post was inspired by that. The three startups that I wrote about are Simple Contacts, ScriptDash, and Wave.

With his experience & role at YC, I think Justin is in a unique position to share a glimpse at companies changing the future more than almost anyone else. Also I think it's cool how he responds to questions from followers.
http://www.openbsd.org/innovations.html
Agreed. Before PDF.js I was mostly avoiding opening any pdf links because that meant a slow Adobe Reader opening.
"Instead of trying to repair these relationships we are just throwing more surveillance equipment at the problem. We are smart people here in Oakland. We have Silicon Valley right up the road and we just think all these new tools are going to solve our problems but it just doesn't work."

This is a really excellent quote. Technology does not solve human problems. Humans solve human problems - sometimes with the help of technology. Improving safety involves convincing citizens to trust police. Accepting distrust and working around it is not a viable solution.
Well, I used to use it, at least!

I actually came to quite like it, but the workflow was sometimes a bit tiresome :( When I found myself the situation you describe, potentially wanting to make an additional change while already working on another, I did exactly what you suggest: add a todo item, and carry on until I'm done with the task at hand. Then start my second change with nothing checked out, so I can undo checkout on everything should I make a mess.

This works, and you get used to it, and of course many would say that it's a better approach - but it would be nice if the Perforce client tools could be a bit more imaginative.

As for how I think of version control, if it's git, #1. If it's Perforce, #2, plus #3 - backup and distribution.

I don't know how much value I get from being careful about my commits with git, but it does make me feel better (which I suppose could be reason enough). On the large-scale, goal-oriented projects that I've used Perforce for, worrying about logical changes has never felt very important. Does it make a big difference if you have one commit that implements 3 features, or 3 commits? When you're trying to fix a bug, you don't really mind either way, because (a) bugs don't respect feature boundaries, (b) all the features are non-negotiable, so it's not like you can back one out and carry on anyway, and (c) the project is large and fast-moving enough that even if you could, there'd be a good chance that actually, you couldn't.

What history tends to come in useful for when it comes to this sort of project: finding the code that corresponds to a particular build that you have a bug report for, and finding who made a particular change so that you can ask them about it (using the imeline view say). These both work fine whether you make granular changes or not.

You might want to be a bit more careful about things if you're working on changes that might want to be merged into another branch on an individual basis. (Suppose you're moving spot fixes from release branch to main branch - some you'll want, some you won't.) But you usually know when you're making this sort of change, and so you work that way anyway.
I just watch Sicario last night - pretty good movie actually - a central element to the story is how they operate in US borders.
But isn't the deal that you get it for free if you include the software? i.e. there's an exchange of value there?

I suspect the problem is that there's no "I'll pay you, but not include the software" option for Android, but couldn't it be applied to any FLOSS as in "there's no option to pay you, but not contribute back" in the case of the GPL or even "there's not an option to not buy a Mac with MacOS", or something like that?

EDIT: If the problem is using Android's dominant position to bundle Google Search, then I get the similarities to the MS lawsuit, the difference being that people actually want to use it, which is why I think Google should be confident about including a "Bing Search" or "Google Search" option, as 99.99% of people would go with Google, since in Google's case, Search is actually a product people want to use when compared to the alternatives, whereas Explorer wasn't in the MS case.

But couldn't this then also be extended to Chrome and Search on the desktop? i.e. Google used its dominant position in search to push Chrome, (try visiting google.com with Safari or Firefox, notice the top-right Chrome banner?) and once they got to a dominant position with Chrome, they used it to further the dominance of Search, by it being default in Chrome etc.
Which is like saying that Ford has 100% of the market share for Ford cars. Antitrust regulation cares about product categories, not brands.
MindGrid for Prior Art in Artificial General Intelligence
I want to point out that, not only is this comment absolutely correct based on what we know, but also, the more studies we see, the more this fact is confirmed. A great meta-analysis can be found here: http://strengtheory.com/hypertrophy-range-fact-fiction/
Molecules with Silly or Unusual Names
+1 to strengtheory.com. For example this is probably the absolute best resource on squatting on the internet: http://strengtheory.com/how-to-squat/.

For noobs, do StrongLifts 5x5 or Starting Strength instead.

Minimal viable workout over premature optimizations! Hand grippers and citrulline malate you'll probably not need for a long long time.
Maaaaaybe for beginners it works

But I'd much rather go to the gym around 9pm than 9am. Much, much easier
When AI starts writing programs? Then we would care about "intentions" rather than mistakes (as with humans).
How to get these into the vive?
18k operations "per minute?"
You can do that on MS Access.
Why use MongoDB at all then?
We do thousands of transactions per second on mysql with innodb and SSDs.
Do they really save internal size by not having a DAC internally for the analog lines on USB-C? They already need a DAC for the internal speakers. How much silicon could one take?
100 Greatest TV Shows of All Time-From Time-Capsule Sitcoms to Cutting-Edge
> Predictions about what is "lasting" are very difficult to make :-)

It's kind of sad when you realize that a lot of the code you write will eventually be rewritten or lapse out of use, or be replaced by something better.

It's very hard to find truly "lasting" work in this world. Maybe research?
> For example, how would your SQL view access something like redis? or any kind of external cache? or an HTTP service?

Smug comeback: https://wiki.postgresql.org/wiki/Foreign_data_wrappers

But your point still stands; no other RDBMS has those, so it can't really be an assumption.

Still, there is a mismatch of paradigms here. The people who built the RDBMSes assumed that everyone would import data into them from wherever else. You, the user (or you, the application developer) shouldn't need to query a third-party web service when doing your database query; something else was supposed to do that query in expectation of your need, and shove the results into the database, so you could just treat that data as another table of useful information to JOIN on.

People who front databases with web APIs tend to treat the database itself as a dumb store—one among many—that's supposed to quickly return "raw" data from single tables so that the web service can chew it together with other data to compute answers to questions. But, by doing so, they're in effect creating their own bespoke Database Management System: the web service becomes the thing that does efficient OnLine Analytical Processing of manifold backing datasets. (Or, at least, attempts to.)

A DBMS's job is to ingest data and process queries to spit out answers. It's not your job; it's not your app's job; it's the DBMS's job. The DBMS has decades of optimization for that use-case; and in fact, that's the meaning of the word "database management system", when defined in opposition to a "flat-file database" like BDB or LevelDB. The fact that there's a daemon sitting there between you and your databases allows the daemon to index and join and expose views and run checks and enforce rules and on and on and on. It allows the daemon to do asynchronous, streaming imports of data-sets from remote sources, so that its data is always up-to-date. It allows the daemon to be there for things like crawler agents to dump their results into, rather than dumping them to something like an S3 bucket where you later have to be the one to import them in. In other words, being a daemon allows the DBMS to be the service that you just come to and ask questions—arbitrarily-complex analytical queries—and get answers.

But that only works if the database management system itself is given access methods to all the databases that contain the data to answer your question. And, in modern practice, we've essentially forgotten that that is a thing that we ever wanted to do. Who would teach a database management system anything? Database connector libraries don't belong in DBMSes; they belong scattered throughout our toppling edifice of RESTful API microservices!

(And if you argue that we still need those RESTful APIs for things like browser-clients wanting to do queries using AJAX: there's no reason DBMSes—not just document stores but full-fledged OLAP DBMSes—can't speak HTTP as well. CouchDB is a great but strangely-unique example. Adapter gateways also exist, like PostgREST.)
I forgot to mention that I was really disappointed (even sad) to see the Jolla (with Sailfish OS) fail. I kind of gave up on "smart devices" after that. Sure would have been dandy had YC backed them.

https://en.wikipedia.org/wiki/Jolla
Yes, we did report the issue to MongoDB. They've acknowledged that the issue does exist, and are working with us to repro/resolve.
> You may recall the FSF's position that the app store EULA placed "additional restrictions" on the GPL, a position that was and remains controversial.

I don't think that the position was contraversial, I just think that people took it the wrong way. The Apple EULA objectively has clauses in it that state that users must follow the "acceptable usage policy" and it is enforced regardless of any external agreements -- this would mean that Apple would be violating the GPL if they distribute any GPL software in their store.

You can add additional terms that permit distribution in the Apple store (as Signal has done), but the stock GPL does not permit distribution in the Apple store because the "acceptable use policy" is one of the things the GPL was made to fight against (the idea that users must act in an "acceptable" way to Apple when running software on their own computing devices).
Why is this a dick move?

It only applies to further work done on the project. By licensing your work under a BSD/MIT/etc. style license you explicitly gave anyone permission to use the work in nearly any way they wanted, including as part of a Apache, GPL3, or even completely proprietary closed-source project.

If everyone else on a project decides to use a different license than you picked for their future hard work, that's their choice, not yours.
But the EU charges are about Google's tactics within the Google run Android market. Google isn't leveraging it's monopoly outside of it's own brand either.

The argument hinges on Google not owning or operating Android. AOSP has been a dead dream for a while now due to carriers locking down phones and Google needing to circle the wagons.
If you liked Carnival there is another canceled show called Utopia.

It is the most incredible 2 season conspiracy thriller you shall ever see. I mention it because it has the same Lovecraftian feel that Carnival managed to obtain.

It also has a score like no other.

Listen to this:

https://www.youtube.com/watch?v=m2f6MfEzhvo
It wasn't even in the top 10 in 2014 according to the BLS Census of Fatal Occupation Injuries[1], as summarized here:

http://time.com/4326676/dangerous-jobs-america/

Police and sheriff's patrol officers was number 15, at 13.5 fatal occupation injuries per 100,000 and it appears that around half of these were traffic related fatalities.

The top 5 are:

Logging workers
Fishers / fishing workers
Pilots and flight engineers
Roofers
Refuse / recyclables collectors

[1] http://www.bls.gov/iif/cfoi_revised14.htm
Another option when upgrading something fundamental is to run a dark service on a fork of real time load for a bit, to make sure it can take it.
Given they were in ECC and only had two storage servers, that seems like something I'd like to read about when they try again!
"The problem with selling for consumers is simple: it's hard to achieve credibility. "

I probably need to think on that angle more for the consumer side.
The worst cancellation I have ever seen was of Caprica. The last show aired made a veiled criticism of Israel policies toward Palestine. It was pulled the next day! The rest of the season be damned. They stuck reruns of ST:NG into the slot. A year later they allowed the final few episodes to be shown and that was the end of that. Since then I am reluctant to watch anything on SyFy.
Random advice from the internet:

If you're worried about what your cofounder might do to you if they have control then it's worth talking through your concerns with your cofounder and through their concerns about you.

My advice is to follow Spolsky's advice: https://gist.github.com/isaacsanders/1653078

If the company is successful, then the difference between the effect of 51% of a big pile of money and 50% of a big pile of money on your future life might not be worth the potential of strained cofounder relations to that an uneven split has the potential to create. If the company is not successful the difference between 51% and 50% of nothing is not worth much either.

To put it another way, if having a cofounder more than doubles the value [for some way of determining value] of the business, then it's worth 50% equity. That's the objective way to look at distributing equity.
I think Apple fans just want to believe!