skysight-inc/HackerNews huggingface dataset:
As I know social system (at least healthcare) is quite good in Catalonia (and maybe also in Spain in general?). What does it missing from Berlin's one?
The "supertaster" testing kit I found on amazon was actually intended to demonstrate simple genetics in a classroom setting, as apparently the ability to taste the chemicals was considered an ideal demonstration of genetics (though apparently the science is slightly muddier now)

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

I could taste the PTC chemical and the list of foods on the Wikipedia that supertasters wouldn't like certainly chimed with me:

https://en.wikipedia.org/wiki/Supertaster#Specific_food_sens...

I've never thought of it as particularly "super", I've always felt it was just me being picky and that it was my fault for not making more of an effort.
> "Diagnosis: All the transponder cards we use, ncs2k-400g-lk9, ncs2k-200g-cklc, are in "standby" state. One of the possible origins of such a state is the loss of configuration. So we recovered the backup and put back the configuration, which allowed the system to reconfigure all the transponder cards."

Their interfaces lost their configuration, and they re-applied configuration, and state came back. This does not equal critical software bug.

> "One of the solutions is to create 2 optical node systems instead of one. 2 systems, that means 2 databases and so in case of loss of configuration, only one system is down. If 50% of the links go through one of the systems, today we would have lost 50% of the capacity but not 100% of links."

This is a crap mitigation. They're still depending on the same hardware and process that led to the first outage, only now there's more of it, so there's more chances to fail.

If they had continuous configuration automation they would have detected when the router's state changed, identified the missing bits, and applied configuration.

"New" routers (as in, since 2011) have APIs and can even run code directly on the router in order to fulfill these requirements. Cisco has multiple white papers, and even provides complete products to manage and certify configuration is applied as desired, even in cloud-agnostic multi-tier networks. Even on old routers, practically all config management solutions out there have plugins to manage Cisco routers.

It's also ridiculous that they had no access to remote hands. This is IT 101.
If you are holding now then I would be worrying about how to get it all out in cash a.s.a.p
CUPS License Change Coming
That's cool but surely any implementation of a language in itself is going to deal with some pretty fringe situations, so it might not be the best thing to read in order to learn how you should write other things in that language?
Or people who are sensible, are incentivized to sell or buy things because they know the crazy bubble won't last. Thus creating adoption in a deflationary model.
Simple iOS Game
> Can be useful when you have multiple monitors and don't want to clutter the main window, especially for single page apps or visualization/monitoring things.

Yep, this is precisely the use-case I would have for this in loom-viewer[0], a SPA data viewer I'm developing for the Loom file format[1] (think large genomic data matrices + metadata). It has a lot of scatter plots and bar charts, and for people with multiple monitors using a separate window as a pop-out would be quite beneficial. It also would make it easier to print out the graphs (which I find silly, but it's a thing researchers do).

I've looked at golden-layout before, but it doesn't play nice with redux at the moment[1]. Since I'm already on React 16 this might be what I'm looking for.

[0] http://loom.linnarssonlab.org/

[1] http://loompy.org/

[2] http://golden-layout.com/
Do you care to elaborate? That statement (or joke?) does not make any sense to me.
But it is one thing to become a millionaire (the word was coined during the Mississippi bubble of the early 18th century) on paper, or in "bits"; it is another to be able to get into a bubble and out again with your wealth intact.

The Mississippi Bubble is an interesting one to invoke here. It was a share bubble fueled by France's overprinting of paper money and habitual currency devaluation.

The idea was to create a monopoly that would exploit the vast riches of France's territories in North America. The company never got off the ground, but the shares were sold and began trading anyway. Investors starved for returns flocked to the trading of the shares.

So yes, it's entirely possible that the overproduction of money by the world's governments is fueling a speculative bubble in stocks, bonds, Silicon Valley startups, and even digital currencies - not unlike the Mississippi Bubble.

Unlike the other inflating assets, however, the supply of bitcoin is rigidly fixed. As world governments produce ever more currency in an attempt to keep the other bubbles inflated, we can expect the bitcoin exchange rate to respond accordingly.

It's worth noting that the basic idea behind the Mississippi company was sound. The Mississippi was set to become a hub of world economic activity and valuable almost beyond measure - but not on the time scale of the day's short-sighted investors.
The Curiosity-Driven Career
Formal verification is critical. Projects like this are necessary: https://github.com/pirapira/eth-isabelle

Paper: https://yoichihirai.com/malta-paper.pdf
Your Acme example is similar to a Dutch Sandwich[1]. Dutch Sandwich, the Double Irish, a Bermuda Black hole... if my accountant started using such slang I'd start referring to him as my consigliere.

[1] https://en.wikipedia.org/wiki/Dutch_Sandwich
Amazon just use "Amazon Logistics" which I refuse to pay for any random guy with a van to deliver stuff randomly anytime up to 10pm
I meant dynamic (re)compilation yes - like adapting the stride in your kernel when you vary work group size for OpenCL kernels. I mean, I have something like that (a primitive self-tuning pre-run calibration step) and I only vary work group-, local- and vector size; and that's already a massive pain in the ass. It's ok on toy kernels but once you move beyond that, it just seeps into all your kernel code, making it almost into a meta-language. And then I'm not even talking about differences like using image types vs arrays for data that is 2d by nature. I don't see how I can generalize that; I just write various versions of my kernels. Which doesn't scale very much, to put it mildly.

My point is - was drawn to OpenCL for its 'portability' claim, and yes kernels will 'run' on various hardware, but with massive differences in speed. what good does that portability do me? My workloads (scientific computing, branch heavy) are different from the typical ML half- or single precision MulDiv()/linear algebra applications, so all the hand-tuned CUDA libraries aren't even my concern. The elephant in the room is that performance doesn't depend on this API or that; it's in how you tune your algorithm to the actual hardware you're running on. Which is the direct opposite of portability.

To come back to the post I was replying to - yes it's 'trivial' (I mean, a lot of work, but technically not hard, not to belittle your work) to compile almost any statically typed code into either SPIR-V or PTX or any other future format for that matter. But that doesn't mean that it will work 'well' (not even 'optimal') on other hardware. In the real world, you're almost always better off just spending a few hundred to get the same GPU as whoever wrote the kernels tested them on (or if you're running your kernels on existing clusters, to focus on optimizing them for what you know you'll be running them on).

Oh and all of that is just considering GPU's. I mean, when you read an OpenCL book they make it seem (in the first few chapters) that you don't even have to think about whether you'll be running on a CPU or a GPU. And then you accidentally use USE_HOST_PTR instead of COPY_HOST_PTR (or the other way around) in the wrong place, and all of a sudden your code is 10x slower than the sequential version of your algo even.

What I'm saying is - I no longer believe in easy to use abstractions for these purposes. If you want speed, you code to the metal, and/or you tweak your abstractions to your specific use case. Yes this is a lot of work. And if you don't need speed, you just throw in a few std::thread's here and there and call it a day.

But that's just my conclusion for my use cases.
There is also little work in how these autodrives interact with other autodrives running different soft/hardware where electronic communication isnt possible. There is a huge amount of non-verbal communication between human drivers that must be somehow replicated once there really is no human on either side of the interaction.
previously https://news.ycombinator.com/item?id=15652702

EDIT: and also previously: https://news.ycombinator.com/item?id=15642856
Consulting on the side can satisfy scientists' appetite for something more
Elastic acquires search startup Swiftype
> > Are they mad because they feel like they missed out?

> Eh, I doubt it.

I think there is something to this. If you've been on HN for 5+ years and have followed the progress of Bitcoin, but never dived in - but then gone on to watch non-tech people make 10x+ returns while not understanding the currency - there must be something about that which grates some people.

I also think it's easy to dislike the "down with central banks", "fiat money is fake money" faction of bitcoin
It wasn't confused, it was just stopped - preventing worse damage to the occupants and itself. The truck driver was in error and will have to pay for damages.
Nvidia is probably "wasting" just as much money on R&D to figure out "which ML chips will win out" 5 years from now, so that they can built it first and sell it as a "GPU".
Exactly what I was thinking while browsing the code. In particular, I'm looking for the "right way" to code the application. Using Observable, Promise, patterns, etc. To get to the point that I don't ask myself all the time if it's the right way to do the things.
Show HN: Storm It 2 for Android – Tweetstorms made easy
VIPER reminds me of the "Enterprise Code" meme. Take a look at the FizzBuzz Enterprise Edition if you're not familiar: https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
This sounds like an amazing project! I'd love to help in any way I can. Do you have a website where I can learn more about your startup?
Is this both sexist and racist?

> Supertasters are mostly women, and people of European ancestry are usually not supertasters.

Edit: The quoted statement does not offend me personally. I’m wondering:

1. When is it not sexist or racist (e.g. pointing out statistics about height, hair color, or skin tone)?

2. When is it definitely (I’m told) sexist or racist (e.g. James Damore asking about capability to write software)?

3. When is it in the middle (e.g. being a “super taster”)?
Reminds me of the Sequoia "RIP: Good Times" and all the "tech bubble warning" articles in 2008.
Any decent sr. network engineer or architect should be able to design you a network and explain the pros and cons, risks, and future scalability.

If someone doesn't know why a failure occured and they can't find out then they aren't looking hard enough
I'd spend dollars on the phone, because the same BTC might buy 10 phones in a few weeks.
"io.Reader and Writer are interface{}'s[1]."

No, they are interfaces, but they are not interface{}s, the interface that is met by having no methods and is therefore met by everything. Nobody is complaining about the use of interfaces that declare a useful set of methods, and are meant to be used when the set of methods is all the target code cares about. They may complain about some of the edges around them (no support for contra- or covariance), but that's not the complaint that is being discussed here.

The complaint is specifically around interface{}, which is a type that means nothing, and so everything fits into it. It means that if you are a function that is receiving an interface{}, you know nothing about the argument to start with, and will have to either pass it along to something else, or examine it via type assertions or in the worst case, the reflect library.

As a multi-year Go programmer, I agree that A: the "true" interface{} that is the meaningless type appears less often than people think, and that if you program is shot through with it, you are either working in a domain where Go is not suitable (complicated math processing, IMHO, for instance), or you are programming some other language in Go, and need to learn how to use Go properly, but also, B: it does happen that things that would be well-typed in other languages will have interface{} show up, which means you're going to sacrifice runtime safety and some performance, though the exact impact depends on what you are doing.

(I say the "true" interface{} because there's also some places where interface{} shows up, but it doesn't hurt you. For instance, the standard JSON library accepts an interface{} to say what data structure to parse the JSON into, and the code that implements that is somewhat complicated, but for the most part, that interface{} doesn't bother you, the Go user. In theory you can encounter run time errors if you pass in something that doesn't work, but in practice, if you pass in the same type every time, which is the natural case that is going to result if you just program normally, it's not a problem. In general, `interface{}` showing up in the incoming parameters of a library is much less concerning than an interface{} showing up in the return parameters for a library. In the former case, even though the language does not enforce type safety, you can enforce type safety by how you use the method; in the latter, you are stuck with an interface{} in your code with all that implies.)
-We solved this in a simple manner at a former employer - we just had everybody who wanted something sent to work have it addressed to such-and-such, room 40.

Room 40 was a bench behind the warehouse reception.

Of course, there are potential pitfalls here - say, assuming your colleagues to be honest, for instance - but to the best of my knowledge, we never lost a parcel in years. (Which is more than could be said for anything entering the murky depths of our ERP system...)
Hard to judge this without seeing it. A human driver might of been able to anticipate what the truck was eventually going to do sooner so as to find a better place to stop. A human driver understands the difference between a truck backing blind and other vehicles.
It probably doesn’t and the uptick in the deaths of comparatively advantaged groups doesn’t fit the model well. Addiction and distress have well documented links with things like unemployment rates correlating well with ODs and deaths. However despite wealthy people featuring in the article the vast majority of the deaths, ODs and incarcerations aren’t in the group you describe.

https://www.google.co.nz/amp/s/www.theatlantic.com/amp/artic...
No, the government wouldn't store anything other than the basic identity (which they already do) and issue verification tokens. The accessor would store their proprietary info as well as the access token to person's private info on the govt api.

Full blown crypto solutions to this don't really scale well and present many problems where the accessor would need to keep asking you for info to see if it changed.

My solution solves the main problem of having a universal number that can get your identity stolen. If we can fix that we have solved 90% of the problem and can work on other things like privacy of said data at a later date.
Are you asking if statistics are racist or sexist?
This is not fully true. Amazon used DHL with me once - they didn't deliver because of a code/gate thing I used to live at. I called Amazon and they got the DHL DRIVER on the phone - me, Amazon customer support, DHL Driver on a single phone call. Amazon CS fucking rocks sometimes. So yes, there are companies that can go the extra mile and seriously dial up the heat on the delivery company.

I think the best CS will call and deal with shipping issues. Crappy companies will have none of that.
Taleb describes how antifragile systems need to provide enough leeway for people on the ground to actually make decisions. Otherwise you can't react to unforeseen events and things go sideways. Delivery companies and support departments of large companies seem to have built a incredibly fragile system that can't even deal with frequently occurring anomalies. Reading some of the comments here those anomalies even seem to include things like red lights and bad weather. It seems to be a consistent pattern that reaching out via social media or directly to leadership is what yields the best results for the same reason the system is so fragile.
Former archlinux developer here (maintained the haskell stack, coq, built an aur git repo, math packages, created 100s of packages, etc.), I think that this is a good thing:

I never used i686 even though I built for it.

The way I built packages was on my local laptop (clean chroot). Building for 2 separate architectures involves building 2 separate packages. This doubles the time it takes for a developer to build. This might not be that bad for smaller packages, but ghc (haskell compiler) took a long time on my computer. This means that if it takes an hour to build ghc, it would take 2 hours of my time to actually build ghc for both platforms. When you're talking about 100s of packages built many times over several years, this quickly adds up.

The other benefit from removing i686 support is that the packages built for that architecture were never really tested by developers. I ran x86_64 10 years ago, tested the x86_64 version of my packages, and most of the time pushed them directly to the main repositories if everything checked out. For more critical packages, I would push them to testing, let people report any issues, and then move them after a couple of days. This means that I never knew if i686 broke or not. This was the case with most of the developers at the time.
> Bitcoin has the potential to actually change the world

I really doubt this. I have never seen a convincing argument about how BTC would solve any of its many technical issues, and the political ones are even larger.

I would gain a lot from Bitcoin's success. Really. Just by making it possible to do business without the gov being a bottleneck it would already change the lives of mostly everybody around here.

I just don't see it happening, for obvious and important reasons, that a bunch of people insist on ignoring. It's hard enough not to pass judgment on the people making an effort to ignore the obvious, now those same people trying to paint the others in a bad way is a bit too much.
Dieting Without Feeling hungry--infographic
It should honk.
By this standard, gold and USD also don't really scale, because you can't send them fast enough. Interbank clearing is pretty slow.

We already have exchanges and clearinghouses like Coinbase for example. It's easy to imagine a Bitcoin-backed payment infrastructure offered by Coinbase or a Visa-like consortium of exchanges.

Of course this taps into a huge and messy ideological debate about what kind of thing Bitcoin ought to be.
'Eavesdropper' vulnerability strikes hundreds of mobile apps using Twilio
Regeneration of the entire human epidermis using transgenic stem cells
In some countries, downloading things from CDN has a significant effect on page load times so this is good advice. Sadly most users won't disable custom fonts because they don't know it's a problem.
As someone who gets paid in Bitcoin and only has Bitcoin I can explain how it works.

I make purchases using Bitcoin or credit cards. I then sell enough Bitcoin to pay the credit card bills.
Privacy Pass: A browser extension for anonymous authentication
Then spend the billions you made off fb taking it down, Sean.
A lot of great new features with this update.

Highlights
Passes Jepsen, The Industry’s Toughest Database Test - https://www.mongodb.com/mongodb-3.4-passes-jepsen-test

Tunable Consistency -
https://docs.mongodb.com/master/reference/method/Mongo.setCa...

Retryable Writes - moves the complexity of handling temporary system failures from the application to the database.

Change Streams - The application can register for notifications whenever a document or collection is modified, enabling downstream applications and consumers to act on new data in real time, without constantly querying the entire collection to identify changes

Fully Expressive Array Updates - can now perform complex array manipulations against matching elements of an array – including elements embedded in nested arrays – all in a single atomic update operation https://docs.mongodb.com/master/release-notes/3.6/#array-upd...

Schema Validation - DevOps and DBA teams can now define a prescribed document structure for each collection, which can reject any documents that do not conform to it. https://docs.mongodb.com/master/reference/operator/query/jso...

Security Controls - IP whitelisting, all networked connections to the database will be denied unless explicitly configured by an administrator

End-to-End Compression - wire protocol compression to network traffic between the client and the database. 80% savings in network bandwidth.

Sessions - https://docs.mongodb.com/master/release-notes/3.6/#sessions

Improved scalability with the WiredTiger storage engine - a single MongoDB instance running with the WiredTiger storage engine can support over 1 million collections.

Subqueries - A more powerful $lookup operator https://docs.mongodb.com/master/reference/operator/aggregati...

R Driver - https://jeroen.github.io/mongolite/
Scientists Are Growing Human Mini-Brains Inside Rat Bodies
I'm not sure, I've never wanted a credit card. Why would you want automated credit card issuance?
> Stopping in an unexpected way is fault.

Generally, not, though there are some exceptions. But that's not relevant here, because the bus stopped in an attempt to avoid/mitigate a collision with the truck, which was illegally backing into it's path, and the driver of the semi was cited for the violation.
Hi, author of the post here!

With GraphQL, you can think of each field as a tiny endpoint, and you do access control on that in the same way as before.

It turns out that while GraphQL allows the frontend developers to select the data they need, that doesn't result in an unlimited set of queries. You often get a number of queries which is similar to what you would get if you hand-coded specific endpoints for different UI views, which turns out to be a common pattern outside of GraphQL.

> What happens if the user doesn't have access to part of the requested data

In this case, the gateway just falls back to the underlying server implementation, and it's a cache miss.
Take my job (please) – Ryan Avent
> which I must be able to show to certain agencies at any time.

Which agencies and for what reason? There is no general obligation of US citizens to carry identification or even to provide your name to authorities unless you are reasonably suspected of a crime.
Privacy Pass
Yes. If you consider this a poor outcome, then you should consider regulating the banks.
ebay gives ~ 24 days
I wonder whether scrutiny of those tax avoidance schemes revealed in the paradise papers or Panama papers will lead to those investors moving their funds to bitcoin.
Segwit can enable that kind of scaling.
The "blockchain" hype right now feels so much like "internet" hype in the late 1990's. Was that a bubble? Yes, but successful companies and technologies did emerge from it. People did make money too: those who started companies (even the companies that aren't around anymore), those who got lucky and invested in the few winners (like Yahoo), and those who invested broadly across the whole "internet" market.
Definitely shouldn't be restricting how you code based on your IDE. If VS can't handle auto, either update for a fix or switch to CLion, it works just fine there.