skysight-inc/HackerNews huggingface dataset:
Somewhat related, there's a very good post here: http://lesswrong.com/lw/l8/conjuring_an_evolution_to_serve_y...

It's about the unintended side effects of trying to be a 'Natural Selector'. One example is selecting individual hens on egg output to create a breed of high-egg producers. The result was mean chickens which had gains b/c they were very aggressive. The breed needed to have their beaks clipped otherwise they would kill each other. When productive groups rather than productive individuals were selected though, they got the desired effect. (Though in another example I can imagine selecting for mean group behavior)

Another example was trying to selectively evolve animals that would self-limit reproduction. (to avoid overpopulation and resource over-consumption) The end result was selecting for cannibalism.

In organizations, the equivalent of propagating a feature are the hiring stage and the promotion stage. Whatever you hire for, or promote for, will be the trait that's optimized. Whatever the side effects may be... (e.g. Enron)
He gets paid big bucks to lead a company like Uber and be held accountable by the board, not some random stranger. You seem to have some romanticized view of the world that's not congruent with reality.
With cities in the US (apart from a select few like NY, Chicago, New Orleans, etc) being what they are, I wouldn't put forward the US as any kind of model for urban planning or the desirability of cities in general.
$420 a year to watch broadcast TV?
Calling it hazing is pretty fair.

The only time it made sense is when I was coming in to interview for a lead/manager role. Even then we were (the two interviewers and me) were just walking through architecture level stuff.

My hiring philosophy was to bring in contract to perm w/ 60 day contracts. If the programmer could not provide value we just let the contract expire. Otherwise, there was no way to screen out bullshitters.
> For instance, somebody who travels with a freshly-reset phone to restore later certainly might get extra vetting as a result...but SO WHAT? Going through a secondary screening is MUCH BETTER than having to give up your actual data. Isn't it?

That really depends on how resistant a factory reset is to forensic techniques, yes? If they can recover 40% of the data, but give it extra scrutiny, are you really safer than if they have 100% of the data but look at it cursorily?
They get marked as inactive which they accept, and go back to their normal business of being a private limo service for the wealthy at $135/hour.

Uber Black in Washington D.C. is basically exclusively run by private limo operators driving Escalades. Owners of recent model $70,000+ cars are not your typical Uber driver, and do have other sources of income.

Almost every Uber black driver I've taken has handed me their card and proceeded to upsell me on their services outside of Uber.
> something else that offers native bindings to other languages will eventually...

No it won't.

This is our one chance to kill javascript; if we don't do it now, it'll be entrenched forever, and best we'll ever get is 'compiles-to-js' languages like clojurescript and typescript.

Let's be realistic; who has the man power, community good will and business savvy to push an entirely new language across all platforms, mobile and desktop?

Microsoft? Come on. Apple? Google? Google tried with dart and failed.

Who else, seriously, is going to step up?

We can day dream about the magical 'no js' world, but it's never going to happen if web assembly doesn't work.

Currently we're seeing the reverse, js stretched off the browser, onto the server, into mobiles, onto iot devices.

You've got to layout some pretty damn fine arguments about why that trend is going to suddenly reverse.

Web assembly is pretty much our last best chance to flip javascript off and have something better...but it might already be too late for that to work. :/
the latest iteration of this idea seems to be the "awesome" lists on github [https://github.com/sindresorhus/awesome], which are a bit more decentralised and crowd-sourced while still being human-curated.
Just because it's common doesn't mean it's going to remain. The status quo is already changing with the rise of companies offering flexible hours and remote work.
Would you have a reference for that?
Make profiles more robust. Features could include:
• Event creation
• A forum/group tab so followers of a specific account could more easily communicate with each other
• Expanded "About" section
• Custom calls-to-action (i.e. "Sign Up," "Message," "Shop," etc.)

Allow people to publish more content natively. Such as:
• Long-form writing
• Long-form video
In that specific case he might still be ruled a contractor, sure.

But if you expanded the list of duties to be sufficiently large and indefinite ("gardening and whatever else I need"), then a court might rule that you have created an employment relationship and are responsible for providing various other benefits.

So it would seem to favor the "employee" classification if Uber had a long history of "oh, and you also need to take these other requests ... oh, and support spotify integration now ... oh and you have to auto-accept requests before you're done with the current."
REST: JSON CRUD over HTTP https://youtube.com/watch?v=oVE6OF-d1oQ#t=02m02s
this is pretty impressive. can you add HTTPS support please.
Timenote – Calendar, Agenda, Sync with Google, Share with Fb Event, Twitter
Which, ironically, is virtual signaling. That's the modern world though - lets everyone retreat to your corners and come out throwing buzzwords at each other.

"Misogynist"

"Cuck"

If only we could talk about ideas, not labels.
Circuit Breaker Pattern (2014)
Maybe it is fair to call REST a failure in that it is flawed, and there aren't perfect implementations. But I just had to go through a SOAP XML integration, and it was ten times more painful than the worst REST experience I've had. So I still see REST as one of the biggest tech wins in a long time.
My thinking...

Public figures post on Twitter first. As a result, it's where news breaks. However, due to the constraints Twitter has placed on how people are able to represent themselves (i.e. limited profiles) and communicate with their audiences (i.e. inability to publish long-form written content natively), these people are driven to other platforms (i.e. Facebook) to do things they might've otherwise done on Twitter.

Instead of trying to compete as social utility in the way that Facebook, Instagram and Snapchat have positioned themselves, why not cater explicitly to the newsmakers who are already defaulting to their platform, giving them fewer reasons to go elsewhere and attracting non-Twitter users in the process?
First question in the FAQ https://github.com/WebAssembly/design/blob/master/FAQ.md

Memory allocation is particularly painful in asm.js, for example.
REST has "failed" in the same way that many original visions of the web/APIs/protocols have "failed" - you have a few "no-true-Scotsman" purists complaining about differences in implementation; meanwhile a great many real-world developers are quite happy and productive in a REST-like paradigm and don't particularly care that their API doesn't fit some Platonic ideal.

Could things be better? No doubt. But REST (or something like it) is largely "the way things are built" these days and most people don't mind. Calling it a failure is quite a stretch IMO.
The "true spirit" of REST, to me, is that there's a certain set of things
you can do when creating an API that will let you re-use the huge amount of
HTTP middleware that's been written and get correct (and useful!) semantics
from it. Caches (browser-, edge-, and server-side-), load balancers,
forward- and reverse-proxies, application-layer firewalls, etc. will all
"just work" for your software if you do REST correctly, and won't have any
weird edge-cases.

Doesn't that assume that the middleware also implements REST correctly? As the article points out, there are all too many HTTP libraries that only support GET and POST, not the more "esoteric" verbs like PUT and DELETE.
In the wake of today's S3 outage, this seems like a good thing to look into, for those of us that haven't implemented it already (myself included).
It's working for us now
Any other region of AWS would also have worked around this one.
Here's the rub, you're completely right, the problem is for the most part when you don't have rockstars making JSON Pure APIs you end up with half of HTTP redone in some god awful manner.

I once worked with an API where they implemented their own HTTPS and because their own https didn't support gzip they removed quotes from json keys to save bandwidth. JSON pure probably is better when working with knowledgeable people but REST is better than what most people come up with and when not following REST
I get why deep learning is nice but I just do not get the hype around reinforcement learning yet. RL seems great for things like training video game agents and have seen videos of this, but fail to understand where RL can be applied in the real world.

It reminds me a bit of genetic algorithms. GA is the 'last resort' when you truly know nothing about how to model your problem.

What is the sweet spot for RL?
Yes, when you're compiling a particular language to wasm, you could include a GC in wasm code as part of that language's runtime system. But it wouldn't interoperate with the Javascript GC, or GCs for other wasm modules compiled from other toolchains.
Why not just open a support ticket?
It took them 2 hours actually.
Ghost Robotics' Minitaur Demonstrates Impressive New Skills
JavaScript minifiers are already in wide use by anyone making serious use of JS, and JavaScript obfuscators exist.

I think the cause of computing freedom is likely better served by building high-quality wasm disassemblers (radare has an open ticket, for instance) and by making sure that wasm code is so tightly sandboxed that DRM can't work, i.e., that you have the equivalent of an "analog hole" because you can write a browser extension / patch that taps all the data and the inside code can't tell. Hoping that technologies won't get developed has historically not been a productive approach for software freedom; the folks who want to take our freedom have enough resources that they'll do it whether or not there's a standards process involved.
Ah, it's made with something called Blocky from Google. Very interesting interface paridigm. Thanks for doing something with it as an example.
The promise of APIs is simple. Send some data, something happens, get some data back.

But at about hour 4 of wrangling a bearer token to authenticate your barely-documentated PATCH request that is returning a strange error about your application/x-www-form-urlencoded body, you start to realize that APIs in theory are very different from APIs in practice.

(That being said, I don't love the "solution". It's very simplistic and it seems like the author doesn't really understand what he dislike about APIs. I don't think we need another protocol, but rather higher-level tools for dealing with them.)
>I'm going to have to call bullshit on that one.

And yet you don't provide a single concrete reason. And even go on to say the non-REST way you use REST at your team.

>REST is one of the more successful strategies we've come up with for connecting systems, this is just another case of letting perfect stand in the way of good enough. Using GET for non-destructive operations and POST for updates and deletes is a nice, portable compromise. I've been trying hard for years to find a reason to bother with PUT, but so far I've found it not worth the effort.

Note how none of this (or even few parts of what the author of TFA described) is actually REST as defined by Roy.
The google guy pointed out that they are API-compatible (thus easy to run side-by-side) and, most import IMHO, he was humble, self-deprecating, and honest.

This here is insane. The claim that something nobody has ever heard of is more reliable than AWS or Google is the worst possible way to promote the product – even if true.
Pus, I hope.
> Doesn't that assume that the middleware also implements REST correctly?

It assumes that the middleware supports HTTP properly.
This article is being published at this time in part because an anti-immigrant politician is leading in the polls in France, as they are in many Western democracies. All of their platforms always include some element of using police violence to assault or incarcerate undesirable minorities. And it is unclear to me what these proposed solutions have to do with the problems people say they are experiencing.
Ouch. You brought a gun to a fist fight. Ok ok, SOAP/XML apis are worse. Agreed.
Here's a comparison. With advertisement sales, often companies will say you must provide at least X impressions, even if we won't guarantee premium pricing for you.

Sometimes, maybe even most of the time, you'll get a high CPM (like Uber Black). Sometimes you'll get a low CPM (compare this to Uber X). Regardless, you have to do X amount of business with them or else they drop you.

Sometimes this means taking higher quality traffic (thus potentially higher CPM), and funnelling it to a certain advertiser at a lower rate simply to maintain your impression level.

That doesn't make web site owners, employees of ad companies even if they're solely dependant on a single ad company for their livelihood.
But that means you're not going to end up significantly above average either. Whether that makes sense really depends on your financial situation and tolerance for risk than any hard and fast rule.
>You can choose to follow the style (which is so much more than naming methods and URIs) or fight it.

And most people chose to ignore it -- and implement RESTful (mostly unrelated to REST as described by Roy) APIs, and no much harm has befallen them.
I see huge crowds, maybe the most cars in a parking lot ever, I don't know, you look out the door and its nothing but cars, huge. Many people say that JC Penny is the best store, huge store, way bigger than Amazon. Have you seen an Amazon store when walking by yourself in the Mall? I haven't. You know why? Amazon is a fake store. That's right, fake store. Nobody buys anything there because its fake, all fake. Malls are wonderful places, I love Malls, everyone goes there and loves them, all our shopping is done at Malls, and I have to say I know a thing or two about Malls. Huge crowds, JC Penny is the best. No more questions.
(ahem!) graphql
Uber is not immune to societal change, they fully embrace this, like any company must if they want long term success.

Every corporation seeks to maximize profits. They may make investments, but every company expects a positive return on those investments in the long term.

I think we are responsible for our own actions. No one forced this driver to use Uber. Uber and Lyft always had very open relationship in the sense that drivers routinely double dipped in the pool without legal issues. There is absolutely no expectation that the terms under which the drivers are operating are set in stone and they aren't going to change in the future.

You have to look at things within the legal framework. $97k is a lot of money and people sue for much much less. That driver probably had no case at all.
> the most adapted novel of all time...

I'm a little surprised by that fact. I had always assumed The Three Musketeers was the most adapted: https://en.wikipedia.org/wiki/The_Three_Musketeers_in_film (If you count the bullet points, it's pretty close...57 vs 65?)
I agree that it's potentially useful, but it also adds it's share of complexity to any implementation I've come across. And most proposed uses I've seen do not obviously benefit from the idempotent approach, from my experience it often complicates the server implementation. I've found using the REST approach for URLs, separating reads from writes and using status codes a good compromise.
I still remember a Google screening call I had a long time ago. "You have 1 petabyte of data you need to transfer halfway the world, what kind of network protocol would you implement for it". I, of course, "a truck/ship/container with tapes?". "No it needs to go through <i think a satellite link>". "Well, lemme see, larger frames, window sizes, capacity of the link becomes sort of the leading issue, but seriously, I'd Google for some papers and take it from there". I found it an extremely strange interview, as it went on like that.
I mean entrepreneurship assuming he lost $96,000 by buying a few cars and timesharing them out to other drivers... which is starting our own small business...

You can't "lose" $96,000 by being a driver...
We Used Terrible Science to Justify Smoking Bans
Reporting bias inflates the online reputation of medical treatments [pdf]
Comparing ancient and modern genomes for cognitive ability variants
Also sad from the AI perspective, this was a great, public human-labeled dataset.
You might do well to read what I wrote about perfect and good enough. These are ideas, not laws.
But flying close to the sun is still really bad. It's just we've never got close enough to the sun for it to be a problem.
Your comparisons are not that relevant. Also comparing it to a "protocol" is the overstatement of the decade.

How many browsers do you have? 3-5?

How many REST client libraries are there?

Answer: one per service(per programming language).

What kind of protocol is that?
It failed? When?
I don't quite agree with the all-or-nothing assessment, but your passion is exactly why this will happen.

Too many of the silent developer masses (probably mostly back-end engineers) have and continue to feel this way about being stuck with JS. The genie's out of the bottle, it's not going back in.
Uber CEO Travis Kalanick being condescending to a taxi driver
That would be because the Google employee didn't claim they were "immune" to problems, and actually admitted having their own problems from time to time.
AWS's profit helps fund the rest of their business.
not that i'm saying that this is the case for the adobe vulnerabilities, but in practical terms the ecosystem is pretty tightly coupled to "the OS" when it comes to security.

if your OS needs a ton of cruft bolted onto it to make it useful, and that cruft has security issues then compare that to an OS that doesn't need that cruft, or has a more security software ecosystem. for example, adobe reader vs macos preview.

ecosystem is hard to change, and not entirely the fault of the owners/developers/etc of the software, but it's still important
Sure would be nice if people would look at what the DLC actually is before complaining about it....
Except the relative viewer numbers will be taken into account in their contracts with the cable companies.

If a channel attracts fewer customers to the package, it will get less money in return for its inclusion, so nothing is really being "subsidised".
At one of my first jobs, my employer had $1.2MM and 10 people budgeted full time for 2 years to build a project that would allow managers to make queries on a very large dataset.

I pored through the specs, talked to everyone who would use this, and realized all the queries could be calculated from a much smaller, summarized version of the data.

I wrote a script that would create an Excel PivotTable every month and send it to everyone who asked, solving the problem in a few weeks with a <500 lines of code. The execs decided it would not be worth spending an extra two years to get the exact same answers in a web UI.

Good times.
You seem to be implying that only rich people can afford taxis, and thus its some exclusive service no "normal" people ever avail themselves of.

This isn't true, and even if it were---cabs are private spaces; that's what you're paying for. Subways, elevators, busses are shared public space.
It's funny... the tactic that ReactNative runs for JS in different environments may well be contrasted with a "BrowserNative" library that bridges browser UI with another compiled (webasm) language.
Let me ask this - if/when the issues regarding the nature of causality and objective reality are finally resolved, will this be a result in physics or in natural philosophy?
us-east-2 is brand new and us-east-1 is the oldest region. Any time there is an issue, it is almost always us-east-1. If possible, I would migrate out of us-east-1.
FTFY

> 1. cut costs by a lot. they shouldn't be spending $2B per year

Really, is Twitter doing poorly? $2.52 billion in 2016 is more than enough revenue, I'd wager, to maintain a solid company. Twitter seem to me to have an explosive-growth mentality - spend like crazy and grow our way to success - in a post-explosive-growth reality.

Fix the cost structures, and make ~$1 billion in profit, and you have a solid company. With continued YoY growth of say 5%, and a valuation of $20 billion in the near future, about double their current $11.33B, is not out of the realm of possibility. Sure, it isn't Google or FaceBook sized, but is a $20B company in anyway failing?
I know this is off topic, but I really disagree about the quality of broadcast TV. Hannibal and The Good Place are both beautifully shot, very distinctive, and highly ambitious, and both came out of NBC. Speechless is on ABC, and while it's a pretty by the book family sitcom, I still think it's funnier than anything else on right now.
>At least for now, WebAssembly does not support garbage collection at all. Memory is managed manually (as it is in languages like C and C++). While this can make programming more difficult for the developer, it does also make performance more consistent.

I support anything that improves performance and efficiency. But the best of both worlds is always great. I'm wondering if it would be possible to implement reference counting (and maybe automatic reference counting) similar to Objective-C, and if so, would that simply be a matter of the particular language and WebAssembly transpiler you're using supporting it? And are there disadvantages to reference counting that make it a bad idea? I enjoyed using it doing earlier iPhone programming.
I've used Appengine since 2009. Early on they deprecated the original master-slave datastore, but apart from that I've had zero refactoring around their services.

Other services are a different story - from my perspective Google are better at supporting legacy interfaces than most.
Nobody ever needs to code binary trees, outside of interviews and a few library developers.
Hacking Issues
I can vouch for shadow duty guys he is a ­guru he increased my ­credit score from poo­r credit and helped m­y nephew upgrade her ­school grade and GPA ­ without any traces, ­he is geniune and reliable Shadowdataduty@gmail.­com or reach him at 205-686-1758 you will be grateful­.
> I just find it hard to follow the logic to how that makes them employees.

The IRS has guidelines: http://www.twc.state.tx.us/news/efte/appx_d_irs_ic_test.html

Arguments for drivers as employees:

Behavioral Control 1a (the relevant argument I am making), 1b (Black drivers have specific types of cars), 1f

Type of Relationship 11

> What I feel like uber has done is automated the process of hiring contractors for on the spot jobs.

That is not true because Uber dictates the pricing. In fact you as the passenger are not hiring the contractor. If you look at it from a per-ride-transaction perspective it is actually one more reason why Uber drivers are employees (Financial Control 7, Uber limits the extent to which a driver can realize a profit on an individual ride).

Looking at Uber drivers as being contracted by the passengers does not make sense.
Did you read the same article I did? There was zero reference to immigration, Marine Le Pen, police violence, minorities, or incarcerations.

I think you're projecting rather than commenting on the actual article.
Or a usb TV receiver for less than $100, watch it on ya 'pooter!