skysight-inc/HackerNews huggingface dataset:
What's the SQL and wire compatibility level? MySQL?

EDIT: Found quite a bit of my answers in your linked article:

> Cloud Spanner uses a SQL dialect which matches the ANSI SQL:2011 standard with some extensions for Spanner-specific features. This is a SQL standard simpler than that used in non-distributed databases such as vanilla MySQL, but still supports the relational model (e.g. JOINs). It includes data-definition language statements like CREATE TABLE. Spanner supports 7 data types: bool, int64, float64, string, bytes, date, timestamp[20].

> Cloud Spanner doesn't, however, support data manipulation language (DML) statements. DML includes SQL queries like INSERT and UPDATE. Instead, Spanner's interface definition includes RPCs for mutating rows given their primary key[21]. This is a bit annoying. You would expect a fully-featured SQL database to include DML statements. Even if you don't use DML in your application you'll almost certainly want them for one-off queries you run in a query console.

> Though Cloud Spanner supports a smaller set of SQL than many other relational databases, its dialect is well-documented and fits our use case well. Our requirements for a MySQL replacement are that it supports secondary indices and common SQL aggregations, such as the GROUP BY clause. We've eliminated most of the joins we do, so we haven't tested Cloud Spanner's join performance.

This seems like it'd prevent any kind of easy switch over to Spanner.
The study goes from 1994 to 2001, so during the aftermath of the dot-com bust.

That's like studying housing data from 2004 to 2011 and drawing the conclusion that a reduction in the number of construction workers in 2004 would have reduced housing price losses in 2011. It might be correct, but it's ignoring some pretty important externalities.
Because it's highly innovative. Cost != value.
At some point, there's a limit to practical venue size. Football stadiums are probably the most common large venue readily available to rent, and that will only hold at maximum 60-100K. Large outdoor venues can hold a lot more people than that, but the logistics probably are a lot harder (most large outdoor events go for the "festival" approach, for all I know it is not worth it to do that scale for single artist events).

TBH I imagine (as implied in the article) scalping is "tolerated" a bit by venues because some of the risk of a dud event is offloaded to the scalpers. The main problem with high priced concerts is probably more in artist image. It's harder to have a "mass market" friendly image if your concert tickets are not really accessible to the "mass market". Branding is critical for artists; if chasing the short term dollar is bad for the brand, it may not be the best thing to do long term.

Allocating a section of low cost tickets via ID based lottery (ala Hamilton) is a great solution for this in my opinion.
Hugely useful but also hugely different from an engineering/coverage perspective, perhaps.

Companies with more data than can fit in a single-instance RDBMS system (like >3TB of hot data, more throughput than a single node can handle) but still seeking transactional consistency are a clear use case. Single-person startups could definitely benefit, but it's a less-likely scenario that they would require the level of coverage Spanner provides.
I accidentally posted this more than a week ago. Silly me, I forgot that there was only a landing page with the words "Coming Soon". https://news.ycombinator.com/item?id=13566857

This site reminds me of https://choosealicense.com, which gives info on what licenses to use for software projects. I suppose the new Open Source Guide will eventually replace choosealicense by this year.

Somewhat related -- I'd like to see GitHub refresh their GitHub Help articles. They look like man pages, rather than support documents. Just adding a mobile viewport would make it 2x better.

Or, you know, they could open source the entire GitHub Help repo. Perhaps they are actually working on this, and cleaning up the codebase in he meantime.
The java.net package already exists. And there's Netty, which is more battle-tested than likely any networking library save BSD's.
How Exactly Can a Chatbot Increase Company Revenue
We're still working on rolling a few docs throughout the day. For example - here's the node.js lib:

https://github.com/GoogleCloudPlatform/google-cloud-node#clo...
It shouldn't get deleted—on a quick read, it looks like it meets Wikipedia's notability policy.[1] :-)

[1] https://en.wikipedia.org/wiki/Wikipedia:Notability
One of the benefits of writing tests is that helps a programmer avoid writing code that is hard to test (and by implication hard to measure correctness). And one of the goals...or maybe the only goal is to use tests to improve the code. Based on your description, a first order approach might be to write (and/or refactor) your code into a testable form. And by 'testable' I mean what your current skill set allows you to test.

If you've listened to 'uncle' Bob Martin, you've probably seen him advocate writing tests first (if you haven't listened to him and you're interested in testing, he has an experienced view whether or not you wind up agreeing with him). Writing tests before the code means that the code will either be testable or it will be wrong (it might be testable and still wrong but there's a chance that the tests will show that).

Anyway, I suppose my point is that if I don't know how to test my code, the problem is probably the quality of my code not my knowledge of testing. Perhaps complex testing techniques are a code smell for complicated programs. Or not.
Speed is about the only user-facing difference. But the big user-facing difference is that commits are glued to their parents. They really are glued; the merges and potential conflicts involved with rebasing and cherry-picking are a consequence of trying to undo this glue.

Darcs' and pijuls' patches aren't glued, they only either commute or do not, and the conflict resolution mechanisms for non-commutative patches are different.
I've just fixed the article history to make the sequence of events clear.[1]

[1] https://en.wikipedia.org/w/index.php?title=Hemovanadin&actio...
Concurrency in Elixir
> I mean, should you need a staff economist to price your concert tickets?

If you want to avoid your tickets going to the people who are willing to pay the most for them then yes you're going to need an economist, and even then you will likely fail. (As you should, IMO)
I like the original better. The contrast on this one is too low and makes it harder for me to read.
Watch Drive.ai's self driving car navigate California roads on a rainy night
Why should useful things be cheap?
There's no observable difference between trying and failing, and refusing by pretending. We can obviously observe an open refusal.
I was refering to https://en.m.wikipedia.org/wiki/Worse_is_better , which does essentially say 'less is more'.
I don't see why that's "fair" - your definition of fair is entirely based on an assertion that someone with more money should be able to get more things at the expense of others, even when the person/entity providing those things doesn't wish that to be the case. Or, in other words, your assertion is that capitalism is inherently fair, because you're defining fair as anything that is the result of capitalism.
How much concurrent visitors does it support?
How to Create a Telegram Bot Using Python
I switched to the Manjaro + XFCE from Arch + XFCE with a hope to get a more stable system since Manjaro team does addition polishing and testing. XFCE is a kind of simple DM in comparison wit Gnome/KDE, but powerful enough - so less chance of problems due to a lower level of complexity.
Seek cash.

You can't eat equity or options.
But do you know who designed the server tech? Was it old mainframe people?
Comment lower down remembers that the staff suggested it. And William did not perform so well.
I'm only really after a ballpark figure, multiply everything by 744 and say it's estimated. Put a price per gigabyte overage underneath
Biology of Love: Are We Made to Live Happily Ever After? (2013)
Yes. The DAG in a context in darcs or pijul (so, I have a checkout; how did those files come into existence) is a consequence of the set of patches; the order is computed, not intrinsically part of every commit. This has many UX consequences; for example, when you darcs pull, you automatically cherry-pick patches in any order (as long as you have the dependencies) -- when you git pull, you pull in a commit in a position in a DAG, and automatically merge its entire history.

If you've heard someone say "never git pull, always git fetch and then either merge or rebase as appropriate", then they've noticed the difference between the two.
Not everyone can afford a crack ops team. Not enough crack ops people exist to go around even if they could.

"The Cloud" lets us do WAY better on reliability and a little cheaper on cost than we could with our own bare metal servers.

I do wish I could drop a Samsung PRO 960 in our database VM though :(
How We Became the Most Up-To-Date Monitor of Open-Source GitHub Projects
The people that I know at MS and Yahoo told me that Page Rank was never as good as meta-documents. And meta-documents was more than sufficient to explain the improvement in relevance.

Of course this is anecdotal and I would be happy to see evidence to the contrary.
they never seem to issue corrections, so screenshotting is pointless (this one's over half a year old)

I don't think that's true! A copy error is quite different from something one would expect to issue a correction for.
It's innovative. Cost != value.
Yik Yak is secretly pivoting to group messaging
I'm thinking of something automated.

For example, it's possible to gather some metrics of the usage of libraries from a running process (with strace, google perftools, source maps in javascript...).

It can be a process used by a real user or autotests from the project.

A software could monitor those probes and allow the user to reward the dependencies that:

- use less CPU or energy

- use less memory

- contains less bugs

- ...
that's every market you purchase anything in
I bet there will be a lot about CAP theorem in the comments:-)
That's currently in development for 2017, it's towards the end of this year. As we make more progress that timeline will get tightened up. But it is something we are actively working on and it was kicked off in the tail end of 2016.
Those are elephants? Look like boars.

"F"
Yeah, RHEL is one area I wouldn't spend the money on desktop deployments - CentOS is a much better choice here (it's $300/year for a RHEL Workstation license with support, you can get self-support desktop builds for $50/year but why not just use CentOS at that point).
Cloud Spanner
Redux-query – A React/Redux library for querying and managing network state
> it is very easy to forget a password that you no longer use regularly.

Heck, some weeks ago I forgot part of a passphrase I did use regularly. Fortunately, I remembered enough of it that I could feasibly brute force the rest.
Methodology of Human-Level Artificial Intelligence Research
Because you're paying not for cost plus, but value added. To make a meaningful cost comparison, the best alternative must be considered, which is you spending your own labor to engineer and build a similar system yourself.
The difference is more than just the storage format. You could compute snapshots on demand and just store the diffs (that'd be impossibly slow, but you could), but you still would have git's DAG instead of darcs' theory of patches, with all of the consequences of that. (I'd explain them here, but I've already explained it in sibling comments on this thread).
FWIW, the Guardian regularly publishes drafts of articles on it's website, and then makes changes and corrections to the articles.

I regularly see Top Photos, Headlines, Captions and even whole paragraphs appear and disappear after a few hours.
Which reminds me of the overstuffed walrus in the horniman museum, London, where similar events transpired: https://www.allinlondon.co.uk/images/musttry/419.jpg

As far as I understand it, the taxidermist didn't know when to stop, as he'd never seen a live specimen, so just...kept going.
It can be used in git, with a lot of duct tape like git rebase and git cherry-pick and occasional dynamiting through rough git merges.

The darcs/pijul world of repositories as loose ordered sets of patches makes cherry-picking the rule rather than the exception. A branch is mostly just the subset of patches you are interested in at a given moment. A "trunk" is just the superset of all possible patches. You can make interesting and easy usages of things like set intersections [1]: the intersection of the patches in two branches in darcs/pijul can be much more interesting than nearest common parent commit in the git DAG, and especially can be a lot more informative in the cases where things like bug fixes are cherry-picked across branches, which in git is a special bit of tree/commit surgery but in the darcs/pijul world that patch can be often the exact "same" in both branches.

[1] Aside, I love the concept of using intersection branches for consensus-oriented development (what releases to Production are the patches that every developer has pulled into their own working branch), which is a neat form of decentralized development that I think can only really be handled in the darcs/pijul model. (I have an ancient blog post on the idea of such a starfish development workflow.)
Live Nation owns Ticketmaster, and often the venues too, so in the end it all flows back to the promoter from drink pricing to ticket reselling. We used to joke in highschool that the guys punting tickets for 10x the price in the parking lot of shows were Ticketmaster employees and now they actually are.
Researchers Reunite with World Community Grid to Smash Childhood Cancer
I wonder how this will affect adoption of CockroachDB [1], which was inspired by Spanner and supposedly an open source equivalent. I'd imagine that Spanner is a rather compelling choice, since they don't have to host it themselves. As far as I know, CockroachDB currently does not support providing CockroachDB as a service (but it is on their roadmap) [2].

[1] https://www.cockroachlabs.com/docs/frequently-asked-question...

[2] https://www.cockroachlabs.com/docs/frequently-asked-question...
Artists pull inspiration from things they're familiar with, both then and today. Travel in Medieval times was challenging, causing people to generally stay where they were, limiting their view of the world.

You can see this throughout art history. Renaissance depictions of Jerusalem are very "European". For instance, The Sermon of St. Stephen At Jerusalem: http://www.louvre.fr/sites/default/files/imagecache/940x768/...

I'm sure these artists had only heard descriptions of elephants from the few that had travelled and actually seen an elephant. They then referenced things they knew are were familiar with in northern Europe: wild boar, trumpets, etc.
It is very interesting to see how DO is expanding its portfolio slowly and steadily. Does anybody have a relatively large-scale (>50k users) mildly mission-critical applications running on DO? Can you share you experience with existing services?
It has the same basis as standard SQL in BigQuery: https://cloud.google.com/bigquery/docs/reference/standard-sq...
What is TrueTime really? Are their Distributed Systems 'sharing a global clock'?
The Story of Paint Shop Pro
git and bash3.2 are GPLv2. They didn't stop at the version of bash that was GPL; bash has always been GPL. They stopped at v3 specifically.
http://www.catb.org/jargon/html/Z/Zero-One-Infinity-Rule.htm...
Release a gratis band-themed mobile game, with user ID tied to the phone owner.

In this app, allow the user to collect a free sweepstakes entry, with a 60 minute cooldown timer, to a maximum of 8 entries per calendar day. Whenever concert tickets go on sale, reserve a block on the floor from the Nth row to the back of the floor. (We all know that the spots all the way up front are for the groupies, superfans, and rich people.)

Allow users to allocate their entries to specific shows/venues on your tour. Hold a lottery for each show, and allow the users that are drawn to buy 2 tickets for $2, and an exclusive concert tee for $21. Allow a few winners to get gratis superfan passes, to meet the band, collect autographs, get the gratis ultra-exclusive VIP concert tee, scream and collapse on the fainting couch, or whatever it is your hardcore fans would most like to do. Close to concert time, if the venue is not actually sold out, do another lottery and make a second-chance offering to get any previously unsold tickets for $1 each. Any user that does not or cannot buy tickets can then spend their entries to get gratis/discounted merch or media files, or just get their remaining sweepstakes entries back, perhaps to try again on the next show.

The user arrives at the venue, and presents a certain screen of the app on their phone to be permitted entry.

This rewards dedication to the band (and its licensed merch). In order to maximize your chances, you have to check in every hour that you are awake and not at work or in school. You can't get those tickets any other way, and if you don't make the effort, someone who is more into the band will.

Also, the app itself can recruit and assimilate new people into your fanbase. And you can make sure that the band's own holding company controls the IP and app-based revenue, not the record label, promoter, or distributor.
Maybe lvh or one of the others who has more experience with darcs of Pijul will chime in. They've probably spent more time thinking about this.

One difference is that by storing the patches only you can understand more clearly what the intended change was. When you store the whole file it is easy to compute the difference between A and B, but may be impossible to compute the correct differences between A, B, and C. By storing the whole file you now have to consider all the possible differences between them, not just the ones introduced by the commits you are trying to merge.

I would have to play around with it, but I know there are scenarios involving rebase, revert, and cherry-picking commits that can cause trouble in git that I now understand comes because of the fact that git is storing contents, not diffs.

One that I've run into regularly is cherry-picking commits from a dev branch into a master branch to hot-fix bug fixes directly into a prod release instead of waiting until dev gets merged as part of our regular process. If I had commit A on dev and cherry-pick it to master it creates a totally new commit A-1 that becomes part of the history of master. We lost the fact that A and A-1 represent the exact same changeset. Depending on what the changes are, and what further changes happen on dev afterwards, this can cause failed merges requiring manual resolution when dev does finally get merged into master.

I imagine that would not be a problem for Pijul.
A marketplace for management Consultants
Scalpers don't create scarcity. They aren't buying tickets, and setting them on fire.

The artists are who create scarcity, by virtue of not having enough capacity to serve all fans willing the pay the retail price of the ticket. (Or by not doing tiered pricing, cheaper ticket distribution by lottery, etc.)
I've used Google Hangouts at my last two companies. Overall, it worked pretty well.
It seems you agree with me, yet you think I sound ridiculous. Did we move away from my original topic and are we now arguing solely about wikipedia being a good source for anything or on par with a PhD?

My point was that a PhD is in any case in a better position to make a proper & logical argument as opposed to many edits that general people make to wikipedia articles to suit their narrative. Heck, even I am guilty of that & my edits in wikipedia are still intact after ~6 years.

Additionally, the source (one of many) is a video with a face, not an anonymous edit made by a group somewhere somehow & it seems you're getting very personal / insecure about it. I would like to say "Grow up, dude", but that would be impolite.
A cheap VM is not likely to give the same type of performance.
Virtual nurse app Sense.ly raises $8M
The story is consistent with Joel Spolsy's first person account of Bill Gates: https://www.joelonsoftware.com/2006/06/16/my-first-billg-rev...
Artificially short by scalpers driving up demand.
I did a small (6-8 teams) 48 hour game jam that I wrote code almost continuously throughout. I had about 4 hours of sleep in the middle of it, and an hour or two for eating. The rest was writing code.
The code was game jam quality (that is to say not very high), but the game itself was pretty fun and we ended up placing second overall.
Given that CockrochDB is based on Spanner and F1, this DBaaS sounds like it will compete directly with them.
Avira Antivirus 15.0.25.148 Final 2017 Free Download for Windows
Here is a good article: http://www.bluetreble.com/2015/10/time-travel/
> Automation of scalping is bad for everybody involved (edit: except of course the scalpers themselves), as typically bots will buy out tickets to popular events extremely quickly, leaving legitimate fans out in the cold.

On the contrary, it's extremely good for legitimate fans who e.g. have a job and can't take time off to buy tickets at the exact minute they were released.
> I spent some of my formidable years scalping

I think you mean formative years.

Did you ever get hit buying lots of tickets for a show and then unable to sell them?
Whoa I guess that's more or less the same as downtime. Imagine if you were out of space but couldn't do anything for 100 minutes. I am watching EFS and hoping it falls in price or that EBS that backs EC2 instances becomes more automatically elastic.
As long as you keep them seperate enough, via APIs or.else, no issue at all.
I don't follow your logic.

You're suggesting that because a company without any experienced Ops staff makes bad decisions about their Infra, if the same company had experienced Ops staff, those staff would somehow make even worse decisions about their Infra?
> Today, we’re excited to announce the public beta for Cloud Spanner, a globally distributed relational database service that lets customers have their cake and eat it too: ACID transactions and SQL semantics, without giving up horizontal scaling and high availability.

This sounds too good to be true. But it's Google, so maybe not. Time to start reading whitepapers...
> For example - mayor secretary receives a document from some government agency, in docx format, and LO can't correctly open it. Now what is the fallback solution?

Yeah, what do you think could be the fallback solution if one government agency sends a document to another government agency in a secret language, telling them that they have to pay the only company that knows that secret language (and that they paid to translate it into that language) to obtain a translation in a language they can read? Any ideas what possibly could be the solution in this scenario?
Never thought of using EXPLAIN to get an estimated count... nice trick!
This is no different from a myriad of other companies that have private networks on private fiber that span large geographical paths. Google's is probably bigger than most (both in terms of geography and throughput), but it's nothing new to have private fiber to ensure latency/throughput/reliability.
Vendoring Python dependencies with pip
That's inevitable when you're going against standard practice in the industry, and refusing to fit in with everybody else.

Try the same thing in any other industry and you'll get the same result. "You created the problem: you deal with it."
I don't think that necessarily make it's illegal to do it anyway.