skysight-inc/HackerNews huggingface dataset:
It's not about end-user freedom at all. The GPL is there to establish the freedom of the code itself.

For the end-user it's irrelevant what license a product uses. They buy a polished, boxed product; they don't download source code, set up the code's build requirements and then compile it.

The only practical benefit of open source products for the end-user is that there may be forks of it which could have an impact on the price (although a product is more than just its source code, so they may not even be interchangeable). Or that someone could pick it up if the original developer abandons it. But these are theoretical long-term benefits, not immediate ones like those for developers or the code itself.

I'm not saying the GPL is bad. Just that people often misunderstand its motives. The GPL is about code in the same way PeTA is about animals. If the humans benefit directly from it, that's great, but the primary motivation is an ethical absolute: code should be free, locking it behind proprietary licenses is against its nature.
My understanding is that Android uses essentially the same strategy as iOS: don't attempt to support full resolution independence, but instead enumerate a set of supported DPIs. See the DisplayMetrics class: there's an enumeration of supported densities, and the 'density' property itself is noted as being a "gross" measure that is rounded to nice values, like 1.5.

Of course extra space can absorbed into the screen size instead of its density. Android and iOS support this via their respective mechanisms, like autoresizing masks or autolayout on iOS, and I guess layout managers on Android.

If you were to make a new device with unusual screen metrics, you have a few options for app compatibility. You could report an unusual density, and risk ugly antialiasing or pixel cracks. Alternatively, you could report an unusual size, and get bad layouts, where lots of apps will have UI elements overly small, and excessive unused space. Or you could compromise: report sane (but inaccurate) sizes and densities, and resample. This maximizes compatibility, with some quality and performance cost.

(The idealized option is true resolution independence, where apps look great at any density and size. To my knowledge, nobody has achieved that.)

I figure Apple realized that the iPhone 6+ would be very heavily reviewed, and so wanted to ensure that existing apps would work really well on it. That's what their scaling approach enables.
Where though? The jumpbar does the same thing (sometimes - it is buggy). But where on the titlebar do I click to get the "file proxy icon" shortcut?
It's the difference between Common Law (case law / precedent) as practised in many English speaking countries, and Civil Law (codified law), as practised in Europe:

https://en.wikipedia.org/wiki/Civil_law_%28legal_system%29

https://en.wikipedia.org/wiki/Common_law

I looked into this, as sometimes on Internet fora I saw Americans argue about the interpretations of certain parts of their Constitution (or maybe it was the Bill of Rights). I used to never really pay attention to such discussions (because they do not apply to me) but when I thought about it for a little, it puzzled me very much. I always learned that Law, as it is written isn't supposed to be open for interpretation! That's why it's law, and it's written down very clearly in almost computer-like language in the ... which is when I realized I didn't know the proper English word for "book of law" (I think it's "statute").

Of course it's not nearly quite as clear-cut as that. Many European law systems have partial case law and vice versa in the US. In fact both types of systems are growing towards each other. But it used to be quite a fundamental difference in how law used to be practiced, Common Law being from England, and Codified/Civil Law from Napoleon, inspired by the Romans.
Before we get another rage post[1] I would like to emphasize that using Neovim requires that you keep up with the changes.

I use it full-time on supported platforms (everything except Windows), but breaking changes will require occasional reconfiguration, recompilation, or remorse.

[1] http://www.reddit.com/r/neovim/comments/2mo54n
This mirrors my experience as well. Mature well known open source is usually excellent quality. Many of the more "modern" packages are often a lot more hassle.
Hey Regus, feel free to borrow some stuff from my code - it's largely the same principles in Photoshop, as I understand - just slightly different way of addressing layers and things. Correctly positioning layers was the hardest job - Adobe has some weirdly contradicting co-ordinates system...
FYI: Australia has "Australian bat lyssavirus" which is indeed a thing very much like rabies: https://en.wikipedia.org/wiki/Australian_bat_lyssavirus. It surprised me when I learned about its existence :)
I once learned, in the good old mainframe times, that there are 3 sizes of databases: Small size that fit into RAM, medium size that fit on one computer, and big databases, that require a cluster of computers.

The relational model, and SQL databases play their strong roles in medium size databases, but are to much overhead for a fast small database, and do not scale well for big databases.

It was hoped at that time, that Moors law will beat Wirths law (who claimed this law much later), that big databases will soon be medium sized, nobody would care about performance of small databases that much, and we could happy use SQL for all problems. This was true for surprisingly long time, and still is, if your problem fits into a medium size database.

Unfortunate, computer history turns in cycles, and tends to forget lessons from the past. Coding access to a bunch of different databases was at least standard under COBOL. Coding for half a dozen NoSQL databases now, is a complete mess.
Good memories! I did take part in that "war", only that for me it happened after the Wall had already fallen (somewhere in the mid-'90s) but the damn beetles were still doing their thing. It was me, my brother and our grand-mother collecting those damn insects all-day long somewhere in a Carpathian village.
Show HN: Bunyan – a simple and fast JSON logging library for Node.js services
Rules for Creating Gorgeous UI, Part 2
Queues don't fix overload if demand is not related to completion of previous tasks. But sometimes it is!

Consider Internet congestion control. When a path is overloaded, a queue builds in the bottleneck router, eventually it fills, and packets are dropped. TCP congestion control reduces its congestion window, and the rate coming into the queue is reduced. So far so good - the queue didn't fix overload - dropping packets did. But TCP is reliable; it will just retransmit, so dropping packets didn't really shed load - it just moved the queue back to the sending host. No work was really shed from the overall system.

Now what really solves the overload is that the latency of job completion has increased significantly, and for much (though not all) Internet traffic, the job submission rate is clocked off the job completion rate. Think: you can't click on a link on a web page until you've downloaded that web page.

The only reason the Internet works when congestion happens is this: increased transfer latency decreases the connection setup rate. Thus, in a very real sense, the queue (partly in the router, partly in the sending host) did fix overload. But only because there's an external closed loop feedback system in operation.
> Even if the browser only had a single authority you do trust... how easy would it be for someone to force them to do something to compromise your trust? For instance with an NSL bound with a gag order?

By having several authorities you do trust? Preferably in different jurisdictions and parts of the world. But only those who you do trust.
A 1 dip line is sharp at 1x or 3x, but requires antialiasing at 2.5x or 2.2x.
What's so terrible about mmap()? LMDB seems to use it to great effect: http://symas.com/mdb/
Well, yeah, I was a bit hyperbolic. Linux also isn't entirely "free" - you have to spent effort configuring it and so on. But I just don't see renewables competing with oil and coal on the fair free market.
I've been doing it for years without problem, it's a lot easier than you'd first think. Markov chain makes the leader of the email address, domain is selected from a random pool.
Here are some more info including a video.
http://www.i-programmer.info/news/105-artificial-intelligenc...
This is cool, but what about https://news.ycombinator.com/item?id=8611839 ?
Dear Barack Obama, just give us more Facebook in Africa, it's fine really
Not answering your question, but I expect it would take a ridiculous amount of energy to change the angle of rotation on these things.
The effect is that the NSA, the FBI or others could obtain the private key of the EFF root CA through legal arm twisting and gagging.

Certificates are public, so there is no problem with certificate request.

If the project is US only, than it won't make much difference with the actual situation. It wasn't explicit in the announcement.
Exactly the kind of attitude that hinders the F# growth.

I mean F# is a pretty useful numeric DSL, but let's not blow things out of proportions. Modern languages have R#-like refactoring tools.
This is not what "causality" means.
F# is not meant for implementing the complete app anyway. Just use it for business logic where it makes sense.
But it's in the opposite direction: it's even wider, not higher than 16:9

16 / 9 = 1.77

2560 / 1140 = 2.25

It's closer to today's CinemaScope: http://en.wikipedia.org/wiki/CinemaScope "today it generally refers to any 2.35:1, 2.39:1, or 2.40:1"
That makes sense, but then it begs the question of why Light Table was originally distributed under the GPL, i.e. since it's built from EPL'd software... and the GPL is incompatible with the EPL, as you say.

Does Light Table's new MIT license insulate developers from EPL-GPL compatibility concerns that might arise from the EPL'd pieces (Clojure/Script, et al.) used to build it?
With Facebook, they abused the trust marketers put into them. From day one the conversation was about building your brand's presence on Facebook with the "understanding" you would more or less be able to communicate with your audience freely once you invested in building the list.

Bullshit. There was never this "understanding", just an assumption by people who were too blinded by greed to do a little simple math. There is only so much attention to go around and only so many items that can be put into a persons feed before it loses any value to that person. You were only able to communicate freely to this audience because there were so few using the channel. Once it was shown to actually be effective you were competing with everyone else for that small slice of attention. Welcome to the market pal, hope you brought your wallet! If a marketer complains because everything they post each day isn't pinned to the top of people's news feeds for free then it seems to me that FB is doing it's job. I would much rather have my feed curated for things that are relevant for me than for every piece of marketing some store I once liked four years ago wants to send me.
This is a really cool exploration project, but hopefully I will not see this in any production code. Way too un-idiomatic.
> a bit of black tape over the front-facing camera for a while since Google's Byzantine privacy practices had made me genuinely not trust the device.

I genuinely don't get this.

You don't trust the OS not to spy on you, so you covered the camera? Fine. But if you don't trust the OS, how do you stop it from, say, uploading everything you type to Google? OK, perhaps you have a highly restrictive firewall, or only use it offline (reading ebooks?)

But in that case, what's the point of the black tape over the camera? It now has no way of contacting the mothership; all you've done is restrict your ability to take pictures.

Surely the better idea would be to compile an AOSP build for the N7 (or maybe just get CyanogenMod if you're less paranoid?) and you basically have a tablet which you completely control without buying a Jolla (with an equivalent app ecosystem and less bugs)?

Note that there are definitely reasons to get a Jolla phone; for example the fact that AOSP on the N7 is unsupported by google -- just saying I don't fully understand the tape on the camera when you don't trust the OS.

(maybe it was just a figure of speech; in which case, ignore me -- it didn't come across that way in your comment)
I'm looking to relocate to NYC/DC and I have a passive income stream that supports me. I've been looking for jobs that would utilize my journalism/sales experience, but with a focus on technology.

Care to chat?
Dropping support for exotic OSes frees you from having to test on that OSes.
Mozilla Firefox Optimized for Yahoo
You're looking at a screenshot. The actual diagram isn't static. Hover over it and it will expand each box with all the info you need to see what was run, what called it, etc.
In the end of the day Node.js is just a Reactor Pattern implementation in a form of bunch of scripts.
in that case, being from Eastern-European country, you may find this entertaining (i suppose your former country has done the right thing - i.e. join the NATO :) given the way (pro-)Russian rebels appeared

http://en.wikipedia.org/wiki/Colorado_potato_beetle#2014_pro...

and

(http://en.wikipedia.org/wiki/Ribbon_of_Saint_George)
Well, for one thing, this would Break The Web (tm). I assume that users of, say, TorBrowser would not mind, but I strongly doubt the greater public would accept that.

For another thing, these two measures would only force the trackers to switch to other fingerprinting mechanisms that are harder to turn off (ETags, canvas 2d/3d fingerprinting, CSS fingerprinting, etc.), so I don't think this would achieve what you hope.
Are there any plans for English subtitles?
Yep - the state I'm from in the US, Oregon, has a law that says you can't pump your own gasoline.
Imagine an airplane at an airshow. It flies past with a smoke generator belching out smoke, leaving a rough trail behind it that churns and deforms. It's roughly a long tube of churning particles.

Now take this shape into space and make it enormously large. All of the particles in this long, stringy, tube-shaped arrangement attract each other gravitationally, so the tube starts to tighten. The particles around the outside of the tube are pulled back toward the other particles in the tube, which generally pulls them toward the centerline of the tube. Of course, each particle will have its own momentum, so if you looked down the centerline of the tube, you'd see some particles heading a little to one side of the centerline, some heading toward the other. Looking down that centerline, you'd see some particles tending to orbit around the center in a clockwise direction, some others going counter-clockwise.

It's very unlikely that there would be the same number of particles going clockwise around the centerline as counter-clockwise. Just randomly, there would very likely be somewhat more particles going one way than the other, so eventually the tightening tube would seem to be rolling around its centerline in the majority direction.

What trhway is saying is that any really big, dense clusters of particles in the tube would probably have roughly the same characteristics as the whole tube they were a part of. The particles rotating around the center of a large, dense cluster of particles in the tube would tend to resemble the rest of the tube statistically, so they would tend to roll in the same direction as the tube itself, meaning the axes of rotation of these big chunks would tend to be parallel with each other and parallel to the centerline of the tube.
Uber has more public exposure, and perhaps as Apple learned before them as did Google, you need members of Congress. Sometimes they remind you of that subtlety, other times not so much; legislation.
How is Android without using Google services? Is there a significant impact on the experience?
Obama's immigration overhaul could benefit many in California
Facebook Conversion Pixel
JavaScript Garden - documentation about the most quirky parts of JavaScript
Amnesty, EFF, Privacy International Put Out Free Anti-Surveillance Tool
Frankly, I doubt it, and I work at Mozilla.
I do
* Ctrl + L to use DDG (my default search engine);
* Ctrl + L "go" to use Google;
* Ctrl + L "tlf" to search in my dictionary;
* etc.

To set this up, lookup the documentation of "keywords" in Firefox.
Yes it does track links, and instapaper integration is planned very soon!
Before going through on object recognition in images, I'm curious about how they managed to arrange perfect sentence for the caption.

Are we already at the point where NN can arrange perfect sentence when we throw bunch of words into it?
There were no problems with 3G data, didn't had a chance to check out LTE. I've successfully received a copule of MMS-es with pictures, I haven't tried sending any.
No, the EU is not.
A Collection of Effects for Revealing Sharing Buttons
Show HN: WebGL Playground
Photographs Taken  at the Exact Same Moment  All Around the World
Conservation of angular momentum. I don't see this as all that shocking. If you consider that the universe is growing (or at least it appears to be and to the best of our knowledge), and that therefore at some point the matter that now comprises these quasars was quite probably part of a single coherent system, say, an earlier galaxy, which would have had angular momentum - all this is showing is the angular momentum of the structure which birthed the quasars. Which is neat.

Simple version: imagine you have a long pole which is spinning, fast. Then imagine a ninja comes in and slices the pole up, perpendicular to its axis, so you've got 20 short poles. The 20 short poles continue to spin on the same axis as the original long pole. If those poles are in the vacuum of space with nothing slowing them down, they will continue to spin in the same way for a very, very long time. They might wobble a bit (precession), which explains why the poles aren't all perfectly aligned in this data.
First of all, I am basing that on this article: http://www.rollingstone.com/politics/news/global-warmings-te...

Now, this article implies that we need to leave some coal and oil in the groud, even if it's economic to mine and use it up. My main concern is I don't think that markets can handle this task. Markets are great at exploiting all available resources; but how do you constrain them not to do that? You cannot set any price on a resource that you do not want to use at all. In a way though, yes, it's about externalities.
git-hooks is rewritten from icefox/git-hooks, with extra features. Especially support for common used hooks.
I'd like to see the worst-case behaviour too - e.g. hilariously wrong results. Seeing the failures (and their rate) makes it more believable and enables a more unbiased evaluation of the capabilities of the system.

It's like those "up to XX% better" claims - "up to", not "at least" being the key phrase here.
>My language forces you to add gender-dependent postfixes to every verb and noun.

If there's truly no gender neutral way of saying something, then I'd imagine that people always use one gender for generic cases, and as such it's not exclusionary. Which is different from having the option and not using it.

>The source is people being jerks.

Non-jerks being exclusionary is arguably far more of a problem than isolated jerks. If one person says "lol women suck at computers", they're obviously a moron, and can be dismissed. Whereas if everyone around you subtly assumes that all programmers are male, it's far more hurtful, because they're people that you respect.

>When you embarass them into treating women differently

Asking for gender neutral language isn't asking people to treat women differently.
> I never understood why Google created their own browser instead of tightening their already strong relationship to Mozilla.

Most likely because they couldn't own Mozilla. Just as Apple created Safari instead of promoting either Firefox or Camino, because they couldn't own Mozilla.

Both cases are companies that attempt to own the entire silo.

> Contrary to most opinions here, I think that Mozilla's decision is more likely the beginning of the end than a promising "strategic partnership".

We shall see. However, I believe that the previous situation was unhealthy: Mozilla was funded mostly by a competitor with a clear and present interest in making Firefox irrelevant.
The basic problem is there is so much good music out there and it has become so easy to find (and cheap to make) that it impossible for most musicians to make anything but the most basic living. I don't have a solution.
Yes, there is a recent trend to use Recurrent Neural Networks to model the structure and semantics of sentences. This used in particular to do research for Machine Translation by people at Google and the University of Montreal in particular: http://scholar.google.fr/scholar?q=rnn+lstm+machine+translat...
What is convincing evidence? Many prominent environmentalists consider the climate change to be the biggest problem. Even Mr. Lomborg eventually accepted that conclusion.
Make everything vectors.

IMHO this is what Apple should have done a long time ago, certainly on ios. Yes it has issues, but those issues are mostly faced by the OS vendor once, and have been successfully dealt with in the case of font rendering for example with antialiasing, hinting etc. You don't hear anyone decrying fonts being vector formats and asking to go back to pixel fonts nowadays, and resolutions are only going to increase.

The OS should be handling rendering, hinting, caching, raster representations based on vector data. As you point out this is a hard problem and Apple are uniquely qualified to handle it. Instead Apple have punted on this and developers are actively encouraged to produce raster representations of each asset which break for every new device which comes out (as you point out this doesn't just apply to fonts).

Controls like buttons or custom ones should be drawn in code, not included as raster assets, and the iconography for things like buttons, launch screens, branding or other app-unique assets could be stored as the original vector, as it should be. If you want to put a raster image on a button, well, sometimes that's not going to look good.

On top of the problems caused by resamping, what Apple have done instead of choosing the vector route is create an ever-growing headache for developers and themselves by focussing on raster assets and requiring pre-rendered bitmap reprentations of assets like icons, which usually start as vector anyway. How many different pre-rendered sizes of ios icon are we up to now, 20? Where does it end? This is not practical or forward looking, it's a hack which imposes real costs on developers, customers and Apple - there is a huge amount of work in creating and maintaining all the different launch screen, icon and other assets now required to be rendered at 3 or more different sizes for Apple devices, and this is bloating every single ios app with multiple megabytes of assets which could be generated on the fly from their vector representation, over the entire app store that alone is a huge waste of bandwidth for Apple and customers.

So there are lots of reasons to aim for real resolution independence, and from the point of view of developers, Apple chose a quick hack (which has devolved into a hacky mess over time), over a more difficult, forward-looking solution which anticipates that screen sizes and formats are going to multiply until it is impossible to cater to all of them with raster designs.
I remember doing something like this without the neural networks that is, but my results were very very bad. If i find that project in old laptop i'll post it to github.
Guessing you're triggering the "tablet" responsive breakpoint. That's a hard one to fix though, media queries are a bit of a hack but it's certainly better than http://mobile.example.com/