skysight-inc/HackerNews huggingface dataset:
He does have a tremendous amount of (IMO) anecdotal evidence as to when the various populations crashed, but at the end of the day I came away with a simpler conclusion: there just isn't enough reliable evidence to know what did or did not happen, but it seems very plausible there were huge populations of American peoples pre-columbus doing extraordinary things.

As per population crashing, his general thesis were:

- Disease spreads faster than explorers (people who would create records)

- For many reasons, European diseases were more deadly to Americans than American diseases were to Europeans.

- It's a lot easier to conquer a people if they are in the midst of an epidemic. Imagine an immune army invading Europe in the midst of the Bubonic Plague.

- In South America, severe climate events triggered massive wars that destroyed agriculture, leading to population collapse.

As per the tech, I would argue it did spread. Remember corn, potatoes, peppers, tomatoes, avocados, peanuts, sunflowers, and beans all came from Indians. As did the idea of a free people — the basis for America itself! We just don't tend to associate these ideas with "technology" as much as we do wheels and hammers. Much of the Eurasian technology we celebrate today was impractical and unnecessary in the Americas (What good is a wheel if you're climbing the stairs to Machu Picchu? What good is a horse if its hooves rot in the jungle?).

All that being said, I would recommend the book even though I have extremely mixed feelings about it. It was one of the most frustrating books I've read in recent memory, but at the same time, the material is extremely fascinating to me. I definitely came away realizing how ridiculous the history of Americas I learned in school was, but I can't say I came away with a better view of what the Americas looked like either. I'm really hoping for more research and writing on this subject — I think we have a lot to learn from the Old Americas, especially wrt to agriculture, agroforestry, and managing wildlands.
Surely that's just a release build, though...? How would this bottleneck productivity for a team?
Users aren't clicking on it? Better shove it in their face so it's noticed.

I like the solution of not showing the navbar unless the user scrolls up.

IMO, fixed navbars are almost as bad as popups.
I've seen "flamework"-style code go horribly, undeniably bad. But if your goal is "simple and fast and damn the technical debt"-development then I have no qualms with anyone who does it.
So what are the strong solutions? Every high end conference room AV system I've ever seen was total garbage from a UX perspective.
Back in 2003 I saw him (Danny Wegman) just seeming to observe people inside the Pittsford store.

I approached him and spoke to him for a couple of minutes - primarily about some additional British products I thought they should have in that section of the store.
Craig from Citus here. Thanks for the kind words. We've seen a lot of people scale-out transactional workloads with Citus as well. In particular, we've seen a lot of multi-tenant apps that need to keep scaling beyond a single node when they're running into memory or compute issues.

If you are looking for something that is more Postgres flavored (meaning we're just an extension to it so you get all the good stuff of Postgres such as JSONB, PostGIS, etc.) then we hope we'd be a good fit. And we run a managed service on top of AWS as well (https://www.citusdata.com/product/cloud) built by the team that built Heroku Postgres. If curious on pricing you can find it at https://www.citusdata.com/pricing/
While I was at Twilio (mid-2011, through late 2013), every new employee was required to respond to 20 tickets regardless of role. It may have been a hold over from when we were really small but I always thought it was a great reminder that at the other end of that API were people building real projects that might make or break their company, teach them something new, or might be having a bad day that you can help just a little.
"Talk to my lawyer."
Unless I'm mistaken, per-use means you aren't billed for the server when it's powered down.

If the server is up, even if you use 0% CPU, you're getting charged.

Per-use is a lot cheaper for people that spin up servers to meet demand and kill them once things slow down.
"touching naivete"is a good way of putting it.
I used to use Linode for some projects, and really appreciated their speed and server quality, which seemed better than Digital Ocean at the time.

But after using them for 12-18 months, and losing several days of data due to the 2015 DDoS, and reading about more and more security issues, I switched back to DO and haven't looked back. The performance differences aren't noticeable to me, and I'd rather have my hosting through a company with a better security record than Linode.
Or scramble the numeric keypad on every try, but that would get annoying fast.
> And asks you to login to Facebook

Your very clean, presentable looking Facebook account which is heavily manicured, and ready to be presented at a job interview.
I’ll never bring my phone on an international flight again. Neither should you
Typed-rx-emitter: Totally Typesafe EventEmitter for TypeScript, with Rx Support
I don't know what your load balancer architecture is, but It's disappointing that using a load balancer has to cost $20/month, which is fine when you need it, but drastically increases your costs when you don't.

It would be really nice to see someone offer a solution that can actually scale from a single node to multiple nodes as necessary. Being able to run my application on the load balancer inside a container would be pretty nice.
I answer second level support. I hate doing it, but it is true that we get to see some of the things that confuses our customers.

Plus it is therapeutic, you are never going to feel like you will look stupid to a support person again.
That's a great way to never get into the country.
Can you scale up and scale down seamlessly?

Yes

Can you turn off unused instances?

Yes

Can you automatically and seamlessly move to the latest hardware running on-prem?

Yes

Do you want to focus some significant percentage of your time on managing infrastructure...

We spend about 10 minutes per day looking after the stack, with about 4 to 6 hours every 6 weeks looking at if and where we can improve things. We then spend about a week or so in depth once every year roughly evaluating different providers, and we typically end up moving to a different provider, which takes a few days.

...or do you want to focus on making what you sell to customers better?

This (infrastructure) is a big part of what we sell to our customers. What we do (and have been doing for about 15 years) is what you kids appear to be calling "devops" now. I was an early adopter (and discarder) of CFEngine...
http://deletionpedia.org/ is a small project to cope with this in a positive way. A couple of years ago, when I was frustrated by deletionism once again, I wrote a bot that automatically copies articles that are about to be deleted.
Integrating D3 into React
Yelp love
In a word; redundancy.
Microservices is a double-edged sword – Tips and challenges
If anyone's interested I've got thoughts on how to improve wikis here: https://housejeffries.com/page/4

My main issue with current wikis is that if you make a contribution and it's deleted, it's gone from the web. I think that if you're making heavy contributions to a page they should start on a personal wiki and then be pulled into the main wiki "pull request" style.

That way if some over-aggressive editor deletes your work it stays on the internet, just on your personal wiki instead of the main site.
There's not much overlap between the wind belt and where people live. But there are many round farms in the wind belt. The unused corners of round farms would be good places for windmills. There's road access in place. Extra revenue for farmers. Won't bother the crops.

Collecting up the power and shipping it somewhere useful is a problem. That requires new high voltage transmission lines and collection at substations for conversion to DC and long distance transmission.
To further my point: what I'm getting at is that EFS has the chance to be the answer to persistent storage for docker swarm and just persistent storage for docker in general. But at .30 cents a gig it's just too much right now.
I love Milo not because of who he is, but because he pokes the bear that is social convention.

His message is almost entirely abhorrent, but he has his right to do so in a free society. Checks and balances.
Which means things work as they're supposed to, doesn't it?
You've left out a lot of context there.
Where does one find an android phone for $5? I must be misunderstanding?
> Git and mercurial have tools like rebase and cherry pick

darcs had incredible cherry picking about ten years ago.

Instead of saying "get this commit" and solve merge conflicts manually, like git does, darcs would get one patch and every other that was necessary for it.

It effectively made cherry picking work as in "I want this feature from that branch" instead of "I want some code from that branch".

It was glorious, other than the little detail of occasionally exponential merge times...
"We've eliminated most of the joins we do, so we haven't tested Cloud Spanner's join performance."

Makes sense given Quizlet's scale and sharding approach. Anyone else have early experience to share with joins?
Sure, but to compare accurately we should look at where that impacts performance in practice. How many writes can Aurora's largest instance handle? What's the write latency from other parts of the globe?
> "Is this your main phone?"

This is my main phone I use when crossing constitution-free zones.

> it's a felony to lie to a customs & border patrol officer

That makes me livid: "Oh, sorry, the constitutional laws (that apply to us) don't apply here, see it's not technically the US because reasons." [lies to officer] "FELONY!".
That's the entire premise behind reCAPTCHA - if you've solved it, then we've sold useful real-world problems and can move onto the next ones.

The original premise of reCAPTCHA was to help crowdsource the digitization of books by providing spam bot prevention. It's slogan was "Stop Spam, Read Books." up until 2014.
Unpopular speech does not need any more protection. It's already afforded the same protections as popular speech.
You can give Spacemacs or emacs+EVIL mode a try. It's basically emacs+vi keybindings.
Can we stop ignoring the fact that Linode has been hacked several times and responded terribly in every case?
Stack Overflow did well with this. Now I wonder if GitHub will chime in with why they decided to redesign their header recently to, in my opinion, a hideous design.
> The fact is that it's 2-3x the cost because someone decided to be greedy and purchase lots of tickets that people would have bought. Imagine if you go to buy a bar of chocolate, and it's $1 as it usually is. Then one day you've found out that the only way to buy it is from the weird guy outside the shop, who has purchased the entire supply of chocolate and is selling them at $3. I would be upset about it. The actual original price it irrelevant, no matter how cheap it is to get it. The fact is that you're making someone pay 3x as much which is frankly horrible behaviour

You do realize the price is not set by the scalpers, but by the market? This is basic market economics (there is also time-decay so perhaps not completely basic but still). The supply is small, and the demand high. The price will move to a level where all tickets are sold. The scalpers certainly don't want to have any tickets leftover because then they become worthless.

People incorrectly think that if scalpers were removed they would be able to attend all the events they want to attend at some very low price. This is flat out wrong.
You win :D
Services like Cloud66 let you target many different cloud providers, so the complexity of apps you deploy doesn't need to be any different on DO than AWS.

When you attach a load balancer, in AWS, it uses ELB; in DO it spins up an HAProxy instance. There are likely advantages to having parity between the stacks, having the load balancer higher in the stack.
In the referenced case the introduced error involved a reference to a null pointer but there was still no exploitable security hole. The exploit was enabled when the compiler removed an explicit check. The null dereference was an error, but it was not a security issue on its own.
Option 1: "No, I left my phone at home."

Option 2: If you're at the US border and a US citizen, "Sir, I'm an American citizen and just want want to get home" -- citizens can't be blocked from re-entering at the border.
The parent comment doesn't seem to specify "consumer level" and the loss of businesses having their own infrastructure is equally troubling. Everyone is putting a lot of eggs in a very small number of baskets.
So essentially a marketing buzz. "It's always available because we spent a lot of money to make it available"

CAP is about how the system deals with partitions not whether it has partitions or not.
> 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?

If they can give a good reason like it influencing public perception and damaging business, then yes.
Snowfall in slow motion
After commenting, I suspect that the TicketMaster system meets the requirements of most bands. This is noted in the article for the reason you mentioned, but I think the current situation provides additional business utility to the performers.

$70 tickets don't segment the market in the same way $700 tickets do. The expected lifetime value of one $700 a ticket fan is probably much more than the expected lifetime value of a $70 a ticket fan. The $70 a ticket fan might be stretched and is less likely buy a hoodie and get drunk on craft beer and use valet parking...all of which the band gets a cut.
A few areas that I feel we've lost functionality:

* MP3 players: I used to have a device with buttons that fit into my pocket that was able to locally hold my entire music library. I could control the device through my pocket without needing to look at it or hold it in my hand, it presented a filesystem with folders that I could simply drop music into (or whatever files I wanted, at the time 20/60gb in your pocket was a big deal). Since everythings' transitioned, first into library-based management and then into touch interfaces, actually using an MP3 player (or more specifically, whatever music program is on your phone) sucks so much more now

* Software used to work regardless of what happened to its creator. Desktop software still largely does. Nowadays it's almost like entrepreneurs enjoy writing emotional sunset posts, completely oblivious to all the customers they've fucked over because they suck at business

* Computer internals and abstractions were more exposed. Computing is slowly moving away from keeping users close to abstractions -- using modern software it feels like Product Managers want to erase and destroy users' concepts of things like files and folders. Cloud services would much rather you think of their software as an interface to their silos, and the kind of interoperability that you used to get for free by sticking to a 'protocol' of files and folders, is no longer there. (How hard is it to examine iOS or Android at the individual file level? How hard did it used to be?)

* I used to be able to open most software on my phone without being nagged with a popup for some reason or another. If it isn't a "HEY LOOK AT THIS NEW FEATURE YOU STUPID USER WHO NEVER EXPLORES ANYTHING" it's a "PLEASE VOTE ME FIVE STARS". Software talks too much, and I don't want to have a relationship with its creator. Leave me alone!

* I used to be able to boot up my computer (or, hell, even my Playstation!) without being bombarded with update requests. Software used to be finished, and as a program matured you could expect patches and update frequency to fall off dramatically. Our brave new world of evergreen programming means I am perpetually hassled with updates that I don't want, don't care about, and are frankly unnecessary. Sometimes those updates even remove features, sometimes even features that I am using! (How the fuck is that acceptable nowadays anyway? In what industry is it acceptable to take something away from users that they have paid for? We have compromised our standards too far!)
http://lolmythesis.com/ is essential reading for everyone in this subthread
I think blaming third parties in this scenario is silly and Google should be broken up.
He's still on Youtube, he can continue to speak. Google only ended a partnership with him and is no longer going out of their way to promote him. Google doesn't have an obligation to tie their brand to one that's engaging in unpopular speech, as that would defeat the purpose of a promotional relationship.
I wish I would have seen this thread yesterday!

My advice to almost everyone is to prioritize consistency and enjoyment over perfect planning. For almost all working professionals, their plans fail on consistency instead of selecting optimal exercises. If you like bouldering, give it a shot. Jiu-jitsu / wrestling is another good activity that'll keep you strong. You'll be better off with either of those than a lifting regiment where you miss days often.

As for weightlifting, the problem people have with handling heavier weight isn't necessarily knowing the form, but being able to keep form as their numbers go up. Core strength is one of the most obvious problems, but you can also have other muscles that aren't quite as strong and those deficiencies become problems when you're doing heavy compound lifts. A good coach won't just teach you form, but identify the areas you need to improve in order to safely handle heavier weight.

If you want to pursue weightlifting / powerlifting, my best advice is to find a gym with a lot of lifters you can make friends with and elite level lifter or two. You'll pick up a lot from observation (in addition to the coaching you get) and the social aspect will make it easier to keep coming back.
Umberto eco's The Name of the Rose has numerous ruminations from different perspectives on the symbolism and semantic objectives of medieval illustration - or as it's more properly called, illumination.
No, he/she didn't. They addressed the above comment.

If the Pie's point was to show they you can pay people to do dumb things there are other ways to do that without being blatantly offensive.

>>> 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.

^ This response is spot on.
Intelligence agencies aren't stupid. Evidence of attempts to thwart or subvert intelligence gathering is itself suspicious. If the feds seize what looks to them like a burner phone, that may be grounds for them to detain you without trial indefinitely; and may itself become a crime.
For some cases of software I agree with you, my IDE should not be made less powerful just to make it easier to master, however even so it should be built up logically - e.g if editor settings are in one place, the option for which font to use should not be elsewhere. If the shortcut key to rename is ctrl+r r, the shortcut key to inline is ctrl+r i and the shortcut key to add a new method is ctrl+shift+m then that is a bad design.

Most software should aim for simplicity though, I am interested in using your software to pay my bills then get back to reddit, I don't want to learn a complex system.
> I like the solution of not showing the navbar unless the user scrolls up.

Oh man, I've gotta strongly disagree with this. To me, those are just distracting and in practice often end up being fidgety. For tall webpages I think an easy and simple alternative is having a link like <a href="#">top</a> at the bottom of the document or wherever it makes sense. Unfortunately it seems like many designers don't really go for easy and simple.
$ alias pjl 'pijul'

... much better now..
The beauty of redux itself is the lack of magic. It's essentially just a design pattern and is trivial to follow.

So the "edit" part of your comment is key here: frameworks built on top of redux, including middlewares, store enhancers and stuff can definitely lead to an app that is hard to reason about with side effects happening in places you don't expect.

IMO that ends up being the worse of both world: even with all that tooling, Redux is far from terse (in favor of being explicit), but you also get the drawback of a deeply layered framework. This isn't worth it. There are other frameworks and tools that do this better. If you want to be terse, and don't mind throwing in a lot of layers on top of your code to achieve it, use one of the countless other (mainstream!) solutions to do so.

Redux really excel at "putting the code in your face", giving you easy to follow logic where very little is abstracted (and when it's abstracted, it's just via simple function composition). And at doing that, it is amazing and is my pattern of choice. At anything that diverge from that though, it is so bad it's not funny. Right tool for the right job :)
Sorry, this is duplicate. For some reason it didn't just join the one on the front page here: https://news.ycombinator.com/item?id=13645825
As a developer, I hate ops people for making my job slower, but I can't say they're wrong. They make stuff reliable and backed up.
Why didn't the kernel panic when it tried to access NULL?
I am not closed to the idea of management. I will likely try it once (once qualified enough) to get a feel for it and decide for myself if I like it or not.

My impression doesn't come from the pop culture portrayals but rather from people who have been/are managers and hearing them on podcasts. But my opinion isn't based on that.

To me (which is a very narrow worldview at the moment), the only measurable things in management are:

- product delivery
- product cost
- customer satisfaction
- dev team satisfaction

And two of those cannot be measured in any meaningful way. Whereas in coding (and I don't like these measures) I have lines written/deleted, work items fixed, product completion, feature parity with the design document (and quite a lot more I'm sure) and most of them are measurable.

This is the basis for my view.

PS: Thanks for sharing your views and telling me that management can also allow you to see impact of the work.
Also, I do think that more managers are needed who are knowledgeable (or at least willing to learn/work with other who know) with business, development and have domain knowledge of the product (like an EPR dev should have at least used an ERP) so I also want to improve the situation by going into management if I like it.
You're implying that people should behave in a manner that is a serious felony in the United States and likely other places.
Guts V. Graphs: Using Data-Driven Design
That's amazing. Just two questions

1) on quicksort:

const less = list.filter(i => i < pivot);
const greater = list.filter(i => i > pivot);

Wouldn't this be faster:

less = what's < pivot
greater = the rest

2) What is the algorithm people use?
I think it works wonderfully well. I get to see popular events if I'm willing to pay, and I've seen less popular events for less than face value of the ticket.

When I lived near a pro-sports team, my wife and I would go down on Sundays and play good cop/bad cop at kick-off time, and pit the scalpers against each other trying to get rid of their final tickets. Rarely did we ever pay above face value.
Or the 2013 discussion of Wi-Fi signals enable gesture recognition throughout entire home here on Hacker News with links to other related ideas in the comments.

[1] https://news.ycombinator.com/item?id=5824286