skysight-inc/HackerNews huggingface dataset:
> So a query that accesses 10 rows in disparate parts of the primary key space will take longer than one where the keys reside on the same splits. This is expected with a distributed system.

No, why? Query can be executed in parallel.

BTW, isn't 20k/sec is a very very small performance for 30 node installation. Cassandra can handle 50k+ (both writes and read) on a single node. When in most queries you are trying to collect data from many nodes it will scale almost linearly.
Those reasons make sense. Would it be fair to summarize all that as "better merging with fewer merge conflicts"?

Git certainly has some room to improve in the merge conflict department. I looked at the bad merge example you posted -- I suspect I've hit that before. It's rare, but yeah it's there.

I also frequently notice that git complains about merge conflicts, while the custom diff tool I use to resolve them says there's no conflict, and I don't actually have to do anything. Good reason to use a custom merge tool with git.

But, given all this, is this really all an outcome of patches vs snapshots, or is this just git's merge algorithm being suboptimal? Certainly git could selectively ignore the DAG when merging, couldn't it? Even after reading the other comments here, it still seems to me like git has more information when merging than the "patch-based" workflow of darcs & Pijul.

It seems to me like there's a language problem with trying to draw a distinction between patches and snapshots. Git is still storing and transferring patches at the tree level, even if it's not happening at the file level. Git does not store a commit as a zip snapshot of the entire tree, the commit is still only the changed files. It would be fair (but not standard or common) to call the overlay of changed files a "patch" or a "diff". People do still use git format-patch, and email git "patches" to each other. So it's inherently confusing & problematic to talk about git and say that it doesn't use patches.

What does make sense to me is the distinction of having a strict DAG vs not having one -- is that actually what people mean when they talk about snapshots vs patches? Am I tripping on it because I'm being too pedantic about what a "patch" is?
Craigslist Is Ugly, Janky, Old School, and Unbeatable
Just an ancient urban legend. I flagged this.
> I can't upgrade my Elasticsearch 1.7.5 to the newest version, because then I would need to upgrade this small(ish) 4MB Kibana 3.x to a monstrosity that weihgs more than whole Elasticsearch engine

...is that really a good reason to reinvent this whole solution, though? You're basically saying you're going to spend the time to replace your entire log storage/analysis system because you object to the disk size of Kibana. (Which, without knowing your platform specifically, looks like it safely sits under 100 megs).

The rest of your complaints seem to stem from not having upgraded elasticsearch, aside from possibly hitting query scenarios that continue to be slower-than-grep after the upgrade.

Maybe I'm misunderstanding your explanation, but if I'm not this sounds like a lot of effort to save yourself tens of megs of disk space.
But it will become much harder to hoard lots of tickets. And it will be expensive to not be able to sell them all. It guarantees that all seats (for which a ticket has been sold) are actually filled.
I've even heard of a technology for pushing compressed air in abandoned mines with surplus electricity, to be let out through turbines when there's need for power.

We do all of the above (except the compressed air thing and superconductors) here in Finland and between neighboring power grids. Of course there is room for improvement.
The article notes that some scholars would ascribe religiously inspired characteristics to real animals, but it also says that readers were generally canny enough to realize this was going on and points out that there were well-known works that didn't do this.
Why not use something like, "Death to all puppies" or "Death to all kittens"? That's a ridiculous thing to have someone hold up. The statement he chose was not ridiculous.

> If I'm not allowed to talk about tragedies

The sign didn't say, "The Holocaust was bad". The sign said, "Death to all Jews". That's not a tragedy, that's a hateful statement.
we actually had the new load balancers break an app when they added h2 support

there was some legacy code expecting headers to be all caps and amazon rewrites them to all lower case when they pass through the traffic

that was a fun one to figure out
When CSI Meets Public WiFi: Inferring Mobile Phone Passwords via WiFi Signals
That sort of response, "only uneducated people think...", really shuts down conversation, and is a hindrance to constructive discussion. Whether or not AGPL is 'problematic' is something that can be discussed without ad-hominem attacks.
So that means you will use pre TLS v1.0 to support those browsers that can not deal with SNI.

You must feel very smart to be able to support old Android browsers like Gingerbread which represent 1% of the Android market share [0], and iOS pre v4.0 browsers which represent less than 0,1% of the iOS market share [1].

Now according to TLS/SSL support history of web browsers [2] your server is vulnerable to BEAST, POODLE, CRIME, etc.

Congrats your SSL cert is useless.

[0]: https://developer.android.com/about/dashboards/index.html

[1]: https://david-smith.org/iosversionstats/

[2]: https://en.wikipedia.org/wiki/Template:TLS/SSL_support_histo...
I would, however, love that price point. It would be nice if I could run a few light-weight services on a VPS for $2.50 a month and then put my websites and other projects on a beefier VM.

I currently use Linode, but if DigitalOcean offered something at that pricepoint they would be getting $2.50 more from me a month than they currently do.
Except that A in CAP has nothing to do with overall system's availability over time and using it as such is just confusing.
Well, typing is more of a motorical skill than programming. Almost everyone can learn to drive a car (manual gearbox) but the same could not be said for programming where problem solving, logic and intelligence is a must.

But with that being said, people from other professions could still learn how to program and do it well.

Maybe you think of a programmer as person that is just typing in the program designed by someone else, a developer, in a specific language with a specific syntax?
I'm really curious to what people plan on doing with such insane amounts of ram.

Maybe it's possible to scale with just RAM! Fire up a uWSGI + Flask and up the RAM as traffic increases.
It does, but within what bounds? The CAP theorem doesn't specify. One could assume that it means before the partition is restored, but that is only one possible valid interpretation. The PACELC theorem, which is by no means the last word on the story, clarifies this well:

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

"PACELC builds on the CAP theorem. Both theorems describe how distributed databases have limitations and tradeoffs regarding consistency, availability, and partition tolerance. PACELC however goes further and states that a trade-off also exists, this time between latency and consistency, even in absence of partitions, thus providing a more complete portrayal of the potential consistency tradeoffs for distributed systems."

And I would take that argument one step further and say that latency and partitioning are effectively identical, and from the point of view of any given operation, it is impossible to say whether the system is in partitioned state until max lateny (timeout) has elapsed, because failure to make progress within timeout is the only meaningful definition of partion-induced unavailability.
I thought this was going to be a GitHub implementation of GitBook. Excitement fell when I clicked through. However, anything that makes getting into open source easier is good in my books.
Our app's build time ballooned by 2-3X or more when we went to multidex. We've had some luck reducing it, but we'd still like to axe multidex.

I definitely consider a 3X build time increase (not 30 seconds to 90 seconds, but 1 or 2 min to 5-8) to be a significant problem, bordering on nightmare... especially since we just included a few more libraries that put us past the 65k mark.

Is that what other people have seen?
I'm not sure if what you said applies, they have severe restrictions and spanner offers subset of MySQL functionality which is already bare compared to other databases. Changes can be done by primary key only, so it almost feels like a KV store that can do joins...

I don't think it's easy to port existing applications to use it and in the end you will still need to accommodate shortcomings in your application.
It's not even convenient. Strings are one of the biggest scourges of any programming language out there. Giant mess in basically every language until Java got it somewhat right, and even then don't forget your equals...

C# (.NET) could be the forerunner if only they had not gone with UTF16, but then it's only with hindsight that we can point out UTF8.
You could ridicule poor indians by getting them to hold up a sign saying 'lol indians'. Several points come to mind:

1. that wouldn't be much better

2. It's not at all unclear how the anti-semitic message was delivered

3. Why the fuck would you make excuses for such obvious bad behavior

I mentioned here a couple weeks ago that I thought it is sometimes OK to punch nazis and people lost their shit. But someone can throw out 'kill all the jews' as a joke and it's very important that we sit down and think about this analytically.

You really need to spend more time reading history books. You should probably brush up your ethics too, they seem sadly deficient.
what to learn from this? unpopular speech needs protection. google is a private company making money from popular speech. private companies don't care about free speech.
Easier maybe, but my experience of their comparative reliability has been the complete opposite.
database servers, redis and memcached I'm guessing. All of which are basically designed to take a memory-time tradeoff.
16 hours. It was a hackathon, I built a mobile app with mocked interactions and flashy UI.

9 hours. Just last weekend, had to build a system to migrate production database data to another db with different schema, right before a very-short-notice-yet-important QA.
About 20 hours solid, in a very high pressure deadline, with a lot of money on the table.

1 day beforehand was spent doing research, reading source code, devising strategy.

Next day (+ well into the following day) 20 hours solid development in Python and C++

After that it was deployed to 530 servers worldwide and went live immediatly.

Functioned perfectly. No bugs.

I was exhausted after that, it took me 3-4 days to recover.
Building a Custom Jenkins Docker Image – Part 1
The absolute level of computation available isn't changing at the consumer level. What's happening for the next decade is the destruction of businesses hosting their own IT infrastructure and moving it to a couple of core centers.

So, the computational "Gini index" is increasing, but no one is being thrown into computational poverty.
Oh this looks really compelling! Though I'm guessing this is targeted to companies? I'd love to use this for some personal projects but the pricing seems really high. Am I reading it right that a single node being used at least a tiny bit every hour is about $670 a month?

Maybe I'm misunderstanding how the pricing works here. Any clarification would be highly welcomed :)
Difficult-to-use software is most often the fault of bad design - and "software is everywhere" is precisely the reason we should care about making things easier and more accessible. The dozens or hundreds of engineering hours to revamp a feature or a set of controls could save tens of thousands of user hours over the lifetime of the software (especially if you have a significant number of useres).

And gives you a leg up on the competition.
I don't have the real numbers in front of me, but some back-of-the-phone math says we'd save something like $640 a month for equivalent RAM, which is our big limiter.

DO is slicker, but it's not 8k/year slicker. I can do better things with that money.
He didn't explain anything, that's his excuse. Are you really this gullible, or are you also making excuses for this?
The "old way" was sacrificing functionality such as transactions and joins to get scalability (BigTable, DynamoDB).

Google tried that a decade ago and found it lacking, this is why Spanner exists in the first place.
"Is this the phone you use on a day to day basis"- felony if you lie.
Jeff Bezos does the same, also if you are working on one of the retail teams you are encouraged to take support calls once a year.
How would this be in the best interest of the venue/artist who want to move tickets quickly and reduce risk? Seems like this would favor only those concerts destined to sell out or be popular.
Which will only make you more of a suspect, probably resulting in a deeper investigation or even being denied entry.
You can run a memory-based DBMS. That will easily eat all the RAM you can throw at it.
I was having a minor fit trying to recall this narrative from the book I read, until I realized 1421 != 1491.

Already reserved it at the library, cannot wait to dive in. Hopefully better researched than the other author, but I like plausible fiction, too!

1421:The Year China Discovered The World

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

Edit: It seemed familliar b/c I read about it in other book. Conquistador by Levy touches on the underreported civ's and tech in the Americas before the Euros arrived.

http://www.goodreads.com/book/show/2774104-conquistador
Java's crippled generics, lack of tuple support, and lack of default parameters encourage interface bloat in utility libraries.

Given how bloody good Java IDEs are (By which I mean to say - how good IntelliJ is), the cognitive cost of this interface bloat is very low... Until you start developing for Android.
I have a prepaid plan that only works in the US anyway.

I never bring my US phone on international travel, because it just won't work. Instead, I carry a cheap Chinese GSM phone that's wiped before every trip and preloaded with some music and entertainment videos (TV Shows, etc.)

I buy the sim-card at my destination and throw it away when I go back to the States.

I'm not sure this solves anything, but then again, I don't work for a company that makes me required to be able to access sensitive data from any point in the world. YMMV.
SqlAlchemy engine please :) ?
Keep in mind that it's a felony to lie to a customs & border patrol officer. "Is this your main phone?" How will you answer that?
Humans must become cyborgs to survive, says Elon Musk
Since the election I've seen pretty much every major news and reference information source disparaged as "fake news" by comments like this. It begs the question: if every major source is untrustworthy, if it's all a chain of lies all the way down, how does anyone know anything? Can those who have seen the light please point the rest of us to the untainted source of pure truth you've cross referenced against to confirm this?

It seems like there are plenty of people in the world who manage to act productively on the information they have, but maybe it's all just a big conspiracy - nobody has ever known a single fact.
While a agree to some extent and have even explored the idea of how my programming skills could be augmented with other non-programming jobs I still feel that for the foreseeable future we will have programmers.

I see lots of jobs being done by non-programmers that would be done much much better had that person been a programmer. The future will undoubtedly be full of people in traditionally non-programming jobs with programming skills. But we should not trivialize the systems that allow this to happen. While most programmers work very high in the stack there are many very deep layers that sit below that will require a army of programmers to keep going and keep innovating so more productivity can be had at the higher layers.

As an example I feel people often trivialize one or two liners programs, or short examples that seem to do so much for such a few terms. But even those simple examples are backed by sometimes 10 of thousands of lines of codes. A wave of a hand, and a bark of spoken command to a computer will -- at least with today's software and hardware -- never end up producing something new and innovated that will be widely used.

To get where you are suggesting many things have to change. And it's not all software. If you even take a cursory glance at what it takes today to bootstrap a operating system -- you would then see how complicated things get. For the future I feel you are envisioning the hardware will have to be worked along with software to make things much much much more modular than they are. More standardised terms to describe things and more finite building blocks will need to be made. In fact the closest thing I could get your future vision with today's technology is FPGAs and it is no trivial task to do anything useful with a hardware described language.

tl;dr We have not solved computers or software, therefor; a army of programmers will be required for the foreseeable future.
Oh yeah? Which was which in that comparison? I'm not familiar with that.
Who said it was totally fine to use impoverished indians as props in a comedic routine?
"Please hand over your personal phone, not any replacements you carry as decoys"
Aren't they slow Atom C2750 cores though?
Phones should load different profiles based on the password provided, with some activity logged across profiles so none of them appear stale.
Right. The market doesn't work very well except for the very simple scenario of maximizing revenue.
Exactly my point. I would say I personally prefer the Amazon way of forcing you to think about these things.
A critique making excellent points in a dull way would be unfortunate, but it'd still be making excellent points.
RELATED: "Keystroke Recognition Using WiFi Signals"

https://www.cse.msu.edu/~alexliu/publications/KamranWiKey/Ka...
I have to ask, which extensions do you use for your JavaScript development?
The paper focused on an attack against a payment system, not the lock screen, so you'd need to randomize every password input keyboard at the system level.

Probably not a bad idea...
If a border official hands you a tablet and asks you to login to Facebook, Amazon or even LastPass, are you required to do that?
As a developer, absolutely. You need that kick in the ass from the grumpy old bastard who refuses to setup your queue with a max depth of 1 million, or open up the firewall between the database and the DMZ.
Do tell us who you think is being criticized here. I eagerly await your articulation of this alleged critique.
PSA: If you're using the Linode API, the 2048 plan is now PlanID 2 and the new 1024 plan is now PlanID 1. The other PlanIDs were incremented by one as well. I wish they hadn't done that, but there it is.
> Have your phone manage the passwords and unlock via fingerprint?

Yes, that would defeat this particular attack.
From what I can see, absurdly inflated scalping prices is only an issue for a handful of bands out there: the bands whose fanbase has outstripped the capacity of where they are booked at. This is only a small percentage of bands out there. Your chocolate comparison in other words only works if the weird guy bought up only the most popular brand.

The generally crappy experience of Ticketmaster / Livenation and the high ticket prices of certain artists certainly have deterred me from supporting this "greed" very much. Instead, I've tended over the years to go for local scale up to medium-high sized concert events. I've rarely run into these sort of scalper issues as a result.

Judging by the continued high prices of certain tickets, I'm atypical. But this isn't life or death type items like food or healthcare, where capitalism runs into morality issues. This is music. If you aren't happy about certain portions of the music industry, the best way to express that is to not support this side with your dollars -- not as an absolute rule perhaps, but definitely as a factor in your decision.

Because I'm probably not the only one deterred by very high prices and the general crappy experience of Ticketmaster, I do believe that these things do indeed damage the brands of certain artists. If artists want to implement solutions to help those that can't afford market rates (like the many-times mentioned lotteries) to broaden appeal, that's fine. In fact, I'd suggest that would be a good idea: brands are often more important than chasing the short-term dollar. Creating fan clubs, and have ticket clubs allocated by lottery (perhaps adding a bonus of rewarding loyalty, such as increasing your lottery chances based on your membership length): that's probably good for your image, and thus your business.

But IMHO this type of initiative has to be artist driven.
Well, I'd say the "old way" is SQL with joins and schemas and transactions, and the "new way" is KV with eventual consistency.
I don't see how a role in management is at odds with job satisfaction. You mentioned you just graduated -- maybe your impression of management is based on the caricature that tends to be portrayed in pop culture? As a manager, I feel like I am able to see a (hopefully positive) impact of the work I do -- impact both on customers/users and on the members of my team.
Noticed that too, this is not for 'one guy mini-startup', but 'one guy' can already run small loads for almost free in vps.

Having your database problem solved however, one less thing to worry about, if you're bigger.
PewDiePie Videos Featuring Anti-Semitic Clips Dropped by Disney
"Can you reframe your first sentence based on the fact that a sign with "Death to All Jews" was used? "

Yes. it's like saying someone is racist for having a picture of a racist sign in an article about racism in America. Context is everything and removing it to intentionally discredit someone and destroy their livelihood reminds me of actual Hitler tactics. The self-proclaimed 'anti-fascists' are the actual fascists.

"The companies have no obligation (Aside from contractual) to work with him. He made content that they deemed to be bad enough to end their relationship, that's on him, no matter the intention."

This is a dangerous path as well. Should a conservative business owner be able to fire anyone in their company that supports abortion?

Should A trump supporter be able to fire anyone in their company that supported Hillary?

Sure, they aren't violating any laws. But we are creating an extremely divisive culture where opposing viewpoints can't be expressed without fear of reprisal and the result is violence.

A few years back, I remember when a few companies opposed supporting birth control and abortions and didn't want to pay for it through employee healthcare plans.

There were so many people (including here on HN) claiming that companies have no rights and they shouldn't even be given the choice.

Now that it supports your political opinion, companies have the right to not do business with anyone they wish.

So hypocritical.
That's a fair assessment. But I'm assuming they will make it do more "SQL" things in the future. I could be wrong though.

Either way, they are trying to abstract away having to think about eventual consistency with this offering.