Outside of saying "it's our responsibility", he doesn't cover how he/Square will respond in order to help solve the problem. It's likely an intractable one, that really falls to the city and state government, not growing businesses that happen to pay well.
I am assuming the labels are used as a heuristic for traversing the graph. What kind of speed increases in graph traversal are available w/ labels vs w/o labels?
They are used to attache indexes and constraints on them in order to speed up traversals. They themselves have very little logic right now, more will follow in terms of query optimisation etc..
It would be really useful for someone with experience developing in Go to explain the pros/cons of using Go over alternatives. Why should I develop websites in Go over Node or Python?
the double buy-in approach is interesting, and being applied to a lot of different use cases - hr/employment, by Angel list, hooking up, via Bang With Friends (now called Down) and of course Tinder, and also dating via OkCupid locals... it's especially effective if the subject of connection is not something you wish to socially broadcast, due to stigma or fear of rejection (jobs/dates/hooking-up/etc.). There's a lot of untapped use cases where applying double buy-in would be effective, like finding a roommate. Or, perhaps situationally it could be effective and reduce the fear of rejection or awkwardness associated with striking up a conversation at a bar or at a convention, etc.
Maji, nice work. Enabling graph like functionality with linking records is an interesting addition. Any idea what performance looks like going 2 or 3 levels deep with a cross-linked graph of say 100k vertices and 500k edges?
