skysight-inc/HackerNews huggingface dataset:
It's potentially more complicated than that.

Someone on Reddit asked a brilliant question a while back - what happens to quantum fields at the event horizon?

In QFT, fields are everywhere. But to support a field, you need a mechanism that allows causal propagation - which is exactly what isn't allowed across an event horizon.

So at the very least you have a discontinuity where three and possibly all four fundamental forces stop working, and which is separate to any hypothetical relativistic singularity.

Whatever is left is going to be some kind of unimaginably weird sub-quantum soup.

I don't know if that's the same firewall that was invented in 2012. But the takeaway is that relativity isn't complete enough to model black holes. You absolutely need to include quantum effects - and when you do, things get very strange indeed.
Lift a new language to support cross platform parallelism
.google??? Really?
> I'm not arguing with you over what they did, I have not read about it enough. I didn't even read the the exchange in full. This is purely political and a sign of a lack of leadership.

"I literally don't even know what I'm talking about at all, I'll admit it -- but definitely, trust me and my immediate assessment of the situation, it's accurate"

LOL.

>> The bottom line is: AMD want to merge this into the kernel's main tree

> No, AMD wants to have working AMD drivers on Linux.

Are you even reading the words you type? AMD _already has working drivers_. They're right there. You can go look at the code right now, 'git pull' it and install it on your machine. What's stopping you? Your inability to read, apparently?

No, it is literally -- by the definition of the above email -- the case that they want to merge already existing code upstream, into the kernel, and have upstream share the maintenance burden. That's part of the deal -- if AMD code goes upstream, everyone helps maintain it, and in turn, they help maintain everyone elses.

But it turns out, upstream doesn't want their code in its current state. Of course, they don't have to merge it upstream -- they just want to. They don't even have to merge it upstream now or "soon", but they would have liked that. They could easily ship the AMDGPU driver as an external module using DKMS or something, just as things like ZFS-on-Linux do, and start ironing out problems for upstreamability while actually shipping drivers to people.

They have drivers. The drivers work already, in fact. Having them upstream is totally different. Try reading the article and doing some digging through this thread to understand the context.

> But hell, maybe Linux devs think that Linux is so important now that they can pressure AMD devs into doing whatever they want from them. Maybe it works, maybe it wont.

You realize that given AMD's history -- it's entirely possible AMD needs Linux more than Linux needs AMD, right? Linux doesn't need to win the desktop or win over AMD, it thrives in its own market and has been surviving perfectly well without them.
But how can advice for winning a game be either bad or good if you will win whatever you do? That's the part I don't understand.
>> and so do I

So you believe in the concept of sovereignty. France's laws end at France's borders? Border should be strong, right?

>> No, Google wants borders to mean something, and so do I.

No, Google wants borders to mean something when it benefits them, such as in this case. They want borders to be meaningless when it benefits them, such as the ability to operate in almost every country in the world.

These sorts of skirmishes will only increase in the connected world being promoted by corporations. Some people, including myself, would rather that it wasn't done quite so hastily.
>"if random noise is behind the patterns, says Afshordi, then the chance of seeing such echoes is about 1 in 270, or 2.9 sigma. To be sure that they are not noise, such echoes will have to be spotted in future black-hole mergers."

We are getting closer and closer... So finally we see a correct interpretation of a p-value in the media, but the connection to the following sentence is not clear so I am not sure the meaning was really understood.

How does spotting more such echos allow us to "be sure they are not noise", and how does this relate to that 1/270 number?

If the probability of such an observation was 1/1.7 million assuming a random noise model (rather than 1/270), would that mean we could "be sure it was not noise"? Shouldn't that depend on how well the observations could be fit by alternative models?
The people living there will all be working in the office space in Cupertino and nearby towns. It’s ridiculous that all of these towns can add unlimited amounts of new office space, without likewise building any new places for the workers to live.
Interesting link. I saw something weird going on with a favicon up in the browser tabs the other day, flashing and reloading sporadically. I wondered if something like this might have been going on in the background.
That's Latin. The emperor Vespasian's reported last words: "damn! I fear I am turning into a god!"
> I don't know what recourse the PSF has but maybe they should even go all in and defend the "Python" name so as to prevent confusion and stop a potential community fracture. Just call it anything else but "Python 2.8" is not Python.

This! A thousand times! I love open source and free software. I absolutely love the fact that you can fork the code and adapt it to your needs. If you find others who like it great! But please, don't use the Python name! It will create more confusion than help. This fork with a different name is 100% fair in my opinion.
Call of Duty Infinite Warfare Game Serial Key Generator (No Survey)
Possible fix:

I suffer a bit from tinnitus and as a result have taken to carrying earplugs for noisy environments. I find in addition to protecting my ears I can hear conversation better. I think basically the ears work better in the normal db range and don't function so well if overloaded. My kit, approximately:

Holder: http://www.ebay.co.uk/itm/Large-Emergency-Cash-or-Pill-Keyri...

Wax ear plugs: http://www.boots.com/en/Boots-Muffle-Wax-Earplugs-5-Pairs-_1...

Wax is quite good because you can adjust the effect - put in loosely they don't block much, squish them down and they do. I also chop them down to fit which the packet advises against. I recommend for tinnitus avoidance if nothing else.
CIA Says Russia Intervened to Help Trump Win White House – Mpelembe Media
This is like notch and minecraft. I was on the javagaming.org forums with notch for many, many years playing his little games and experiments. You can't look at the finished product and have any idea about the real work that went into it.
I also do iOS apps, and I think the reason for bugs and low maintainability in our domain (i.e. programs that have to power a GUI and all its states) is convoluted state. You stack feature upon feature, and once the system gets big enough, it's getting hard to get a proper grip of what is actually happening. So you start monkey patching, and you start to regret not having written any integration tests that would tell you when you introduce regressions.

State has to be managed rigidly. If you cannot deduce what semantic state your app is in while you debug, then chances are things will go wrong.

I have found two approaches that work for me: Reactive programming, and good old state machines. The former is needed when there is so much state that the latter would be too complex (too many possible permutations > too many states to grasp).

Every property that your screen has (element A is hidden, element B has this text, animation C is in flight...) should be derived from the current screen's state machine or stream of values. Meaning, state 1 will set A to hidden, B has no text, and C is stopped; state 2 will set A to not-hidden, B has text "xyz" and C is still stopped, etc. It's kind of like React, but on a lower level - properties are overridden or methods are called when transitioning between states. One could call this state machine "ViewModel" :)
Swift brought us Enums with attached values, so they are perfect for modeling a state machine. IMO Optionals also prevent some state sloppiness we had with Obj-C's nil behavior.

I'm not saying state machines or Reactive programming are a panacea, but they have solved the problem for me. I'm confident in my code now, and have the feeling that I do solid work (which is good as I'm huge on feeling like an imposter). As long as I use Swift and RAC or state machines, the very most bugs I cause are of semantic nature - e.g. a button text is wrong in such and such state. But crashes or unreproducible behavior are really rare now.
Microwaves in the cold war: The Moscow embassy study
Well, in some respects T-shirts made in the 80s are obsolete, even though functionally they still work. Fashion changes, materials change, cuts change, etc.

You could still wear them today but you'd be working against today's "protocols".
Take it to some store I've never heard of? This is why I will only buy a phone from a brick and motar, or online from a place with a brick and mortar presence (Apple, Verizon, Best Buy)
> Why would you want to downvote somebody trying to help you?

Misreading comments is not helping.
Wouldn't you get orbiting photons simply by having them emitted from falling bodies, i.e. hot gas?

Any photons emitted in the right direction by incoming material in the right place would enter an orbit; and given that hot material emits photons in all directions continuously, and there's a steady supply of infalling material, there's going to be a continuous source of orbiting photons.
https://en.wikipedia.org/wiki/Sensorineural_hearing_loss
From the wording, which I only point out as it seems like people reading your comment are being confused and maybe that means you are also confused, this is a standard code freeze for this one release: the idea being that on your way to a release, such as 2.0 (or 1.8), at some point you have to say "look, we are doing a release here, stop making major changes so we can fix some bugs and cut a version", and this "release candidate" "marks the beginning of the code freeze period" (implicitly for the release of 2.0).
Isn't there a relatively easy way to solve this problem?

As an employer, when you decide to hire someone to produce software for you, you assign them a private key tied to a certificate issued by the employer's certificate authority. The employer then has tooling which requires all commits to the employer's repositories to be signed with a certificate issued by the employer's certificate authority.

Then it's very simple: any code which has been signed by those certificates unambiguously belongs to the employer. Any code which has not been signed by those certificates does not belong to the employer.

Employers can demand that employees sign their work with these certificates in order to consider the work done, so employees who refuse to sign the work with those certificates risk giving up their salary for breach of contract. Employees are then free to sign whichever code they want on their free time, and assert ownership by virtue of it not being signed with their employer's certificate.
Wow, you got really unlucky. I'm on Debian Unstable yet I spend less than that per year. Are you sure you just didn't happen to hit upon a particularly badly supported hardware configuration?

In any case, why are you updating the kernel version every month?
it would definitely give you more analytics to work with...but that was not the scope :$
your missing the point of representative democracy
Powerful Search Tools for Most Popular Keywords on Search Engines
Well, things change, especially in tech. For better or worse, but most of the time for the better.

You should read some changelogs of past python 3 releases. 3.6, for example, has ordered dicts by default. Which is quite convenient when you need to write test testing a small dict with two items for example.

I like driving an old muscle car, most of m look beautiful and bring me everywhere i want. But damn, those new cars changed a lot and are much more comfortable. (But they do break as much ;))
Samsun Rus Escort Lena Sınırsız Anal Keyfi İle Sizlerle
If Google wants to charge Apple iPhone prices, they can't continue with Google level service.
Many people believe that censorship applies only to speech limited by a state actor. Ex: the first amendment of the US Constitution means that the US government cannot repress your speech. It does not prevent others from doing so.

Many other agents engage in repression of speech: we repress ourselves, so do parents, friends, communities, lawyers, contracts. We don't automatically regard repression of speech/expression as a bad thing, and in many cases we are glad for it.
Personally, I would not be surprised if we discover that our understanding of general relativity is wrong for extreme values (i.e. very high mass densities). The whole problem of dark energy and dark matter -which has failed to show up in any conceivable form so far- also gives reason to doubt the validity of our current theory of gravitation.

I think we're in a similar situation like at the end of the 19th century, were many physicists thought that everything that could be discovered already was, apart from some "edge phenomena" that would need to be resolved somehow using the current theories. In the end, these edge cases turned out to be the first hints of some completely new theories that dramatically improved our understanding of nature. I think that gravity and quantum mechanics are due for a similar change, and in the coming decades we might just get the data that we need to make this change happpen.

I also have difficulties "buying" the current theory of black hole physics, especially the concepts of an event horizon and the infinite mass density, as well as the problems which arise from them (e.g. black hole energy evaporation through virtual particle generation at the horizon). And as previous theories of gravitation have broken down at points of extreme value (high energy, high speed), I think black holes are a hot candidate for breaking general relativity.
Show HN: Tool for searching IT jobs in Berlin written in Go
Every even-numbered Wine release is a stable release preceded by a code freeze. If they followed the normal pattern, this release would be Wine 1.10.
> What about contributing towards a project which enables python2 code to run in python2?

Surely that already exists?
On A serious note about the UI though, that red/green colour is awful for colourblind people. Didn't even realise there were two colours at first.
Sure. The purpose of a SaaS product would be to improve efficiency and save time. Given lawyers typically charge by the hour, they would lose money unless they could bill their clients directly for the use of the more efficient software to make up for the lost revenue due to saved time. However billing clients for legal software is not the norm.
Agreed. For me though, my biggest concern with having "everything" in a handful of providers. At least once a month, we get a story about someone having their account shutdown with no way to get ahold of customer service without creating a blog post and turning it into a news story.

Sure, a number of these show fault on both sides, but many do not. The recent article about an amazon seller adding a profile on his kid's kindle and getting his seller account suspended is an example. With google, having a google account suspended can remove access to your email, calendar, plus all of the linked "log in with google" accounts you have out there.
Measuring New-Yorkers Satisfaction and Getting Trends
Depends, there are billable hours e.g. time spent with customers and non-billable hours e.g. administrative tasks not specific to any customer such as payroll, transfer of knowledge between work colleagues. So by targeting reduction of non-billable hours, you would have a compelling reason to sell to firms who bill by time.
> Changing to `unicode_literals` will likely introduce regressions on Python 2 that require an initial investment of time to find and fix. The APIs may be changed in subtle ways that are not immediately obvious.

Unless you're willing to put in the time and energy to extensively test, this is basically a recipe for disaster. You're basically paying at least 80% of the cost of a full Py2 -> Py3 port (since looking for regressions is a huge part of that cost), for only a fraction of the benefit.
My scheme tries to achieve all of that;

https://roamingaroundatrandom.wordpress.com/2014/06/16/an-mp...
What is to stop an employee cloning his work and signing it with his key
As the page notes, many Py2 APIs are completely broken with unicode literals, some noisily and others silently (due to implicit ascii encoding/decoding) leading to hard to diagnose regressions in the codebase under Python 2.

I think leveraging PEP414 and carefully using bytes, unicode or "native" literals is a much more resilient mode of operation.
And now, after the PR shitstorm for reaching HN's frontpage, all will be solved in a couple hours...
Face It: Fake News Is a Disruptive Innovation
If you read ProPublica's R script rather than their anecdote-filled news article, you discover the algorithm is accurate (p < 0.001) and unbiased (bias tests had p > 0.05).

https://www.chrisstucchio.com/blog/2016/propublica_is_lying....

Unfortunately an honest title/article "sentencing algorithm is accurate and eliminates racism" wouldn't be viable clickbait, so they decided to ignore their own conclusions.
I am in the same camp as him actually. I dislike using a case and prefer to use the phone as it was (afaik) intended to be used. Cases change the weight and feel of the device.

I also would like to add that in all my years of smartphone usage (probably about 4 years, quite late adopter) I never broke my phone or screen.
Waiting to see when this crops up here, and how it'll fly considering Consumer Rights [0]. It falls into minor, so Google will have to:

* free repair, (with a repair notice describing the fault)

* replacement (must be the same condition as the purchase, so no second hand!)

* refund (the same amount you have already paid, provided in the same form as your original payment.)

And of course, the kicker:

> You are entitled to return a product if you believe that there is a problem.

And the business you purchased from has to foot the costs of said return.

All of these things are things Google has tried very hard to avoid, but they're selling the Pixel here, so they have to play by the consumer-oriented laws.

It'd be interesting.

[0] https://www.accc.gov.au/consumers/consumer-rights-guarantees...
How leaving a corporate job to join a startup fucked me up and sorted my life
Depends if you can afford to enforce those rights
I've got an MPC based proposal;

https://roamingaroundatrandom.wordpress.com/2014/06/16/an-mp...
Here's mine;

https://roamingaroundatrandom.wordpress.com/2014/06/16/an-mp...
Docute – writing docs without building, no more hexo/jekyll/webpack
Some people keep their remotes in plastic wrap, doesn't mean that's expected.

Sure there is a thriving aftermarket for phone cases that emerged in late 00s, but it is certainly not an expectation on the manufacturer side.
That was literally my thought. Apple doesn't have the best customer service ever, but it's pretty decent and people that have warranties seem to leave happy.

a) if the author speaks the truth (and I have no reason to believe otherwise) that the was never dropped - Google should fix it. That much is obvious.

Now, the b).
b) C'mon Google - you know the author is a techie / twitterer / reviewer - of all the people to annoy with customer service, is a person like that really the good choice?

This incident clearly exposes non-positive elements in their customer support culture.
I'm not saying that he's necessarily dropped it or that it's okay for the CS rep to have accused him of that, but my 4+ year old Galaxy S3 has the same sort of bubbles in two corners on which it has been dropped so I get why that was the first question asked.
Implying Apple service is any good. (See: bendgate)
Well, whatever Intel has been doing, they're just successful as merging their codebase. It doesn't mean the driver is stable though.

The KMS/dri driver itself certainly has _major_ unsolved issues since basically forever. The KMS driver for broadwell graphics was trashing the screen with massive horizontal flicker until kernel 4.8. That's not a long time ago. It's still not solved BTW, just got less frequent. Random pipeline stalls happen on an hourly basis. Tons of graphical glitches and random performance issues with the "glamour" accell path. I've stopped reporting issues at their tracker, as they just get ignored.

The performance of the KMS driver is also inferior to their existing xorg driver in a number of very important scenarios (Xrender is particularly affected).

Sure, I do have vulkan drivers as first class, but my screen flickers, I get graphical corruption and the driver hangs the entire system with certain shaders. I can see inkscape repainting beneath my eyes like it's '84. Wow. And I'm trying that with 4.9 rc8.

I've been using laptops with integrated graphics for almost 10 years. The moment you can get the intel driver to work half-decently, they're already rewriting it. I wish I was kidding.

Intel does have the money. They're actually doing worse in my mind.
Depends on how the verification is done. If it is verifiably derived from your raw vote, then yes.

But if it's is tied to the process of voting such that it doesn't reveal the contents but confirm it was recorded right, then it can work.

See 3-ballot, and also my suggested scheme;

https://roamingaroundatrandom.wordpress.com/2014/06/16/an-mp...
As a Python 2.7 project why would I trust more to this unofficial version with a lot of backported code compared to the tried and tested 2.7 to 3 route?

What would happen with my python 2.8 when it needs to be converted to the official python 3?
I found blocking loud noise with earplugs allowed my ears to recover naturally over time to a fair extent. It may not work for everyone but it's easy and cheap to try.
Your meant to be a "good servant" as this aspect of employment law descends from the masters and servant acts
Apple service is next to perhaps only Amex, if any. Perhaps.
Equivalent in Australia is a Strata Corp and the resulting meetings they involve.
This is how you keep using those efficient, numerically-stable subroutines written by a smart guy who retired 20 years ago in your new code. Unlike Python, Fortran has managed to add significant new features without breaking old code.
for images/home movies I use google photos...for the free aspect that is :)
It most certainly fixes support for Unicode on Windows in terms of filesystems paths, OS function boundaries and the console. Some of these fixes have even taken until 3.6 to get implemented.

As someone who writes cross-platform code, Python 3 was a breath of fresh air after fumbling around in the dark with Python 2.
Indeed. One of the selling points of the Pixel has been a more personal, available and exclusive customer service experience: https://madeby.google.com/phone/support/

This is in contrast with most Android manufacturers who are happy to forget about you after the device has left the shop, and (free) Google online services which have basically non-existent customer support.

It will look pretty damning if Google itself can not build reliable customer service experience even while charging ridiculous prices for supposedly "premium" Android device.
I have the exact same problem. This could really be a life changer for me. Only recently I was at a reception at work after one of our town hall style meetings and in the large room with many people talking, I could barely hold a conversation. It literally took all my mental effort just to hear what the person if front of me was saying. I left shortly after because I couldn't talk to anyone.