saltysugar

Just reproduced here from US soil :). It answers all other elections but refuses to answer about 2020

Isn't everyone pelican-maxxing these days?

Having worked for AWS, one of the things we got a lot push back from was offering something free and then walk back from it.

AWS really strongly focuses on gaining customer trust, and they will only lower price, and never increase price. They won't turn off things until the last customer stops using it (they might stop new customers from onboarding)

I did not enjoy working for AWS so I left pretty fast, but some of the customer obsession there really impressed me.

And in Berlin the cashier eyed me suspiciously when I tried to use Google Pay. He was totally expecting the payment to not go through

Amazon employee here, but the statement I'm making is of my own.

Internally we treat customer names and email addresses as the second highest data classification. The highest one is credit card/financial/password data.

What does it mean? It means that there are a bunch of requirements that a software team must fulfill and pass (reviewed by an SDE trained in the process outside the team). This makes accessing this sort of data a PITA for a lot of people, and I can see why they why they would send out notifications when a breach like this happen. Amazon takes security very seriously, and it in fact creates quite a bit of friction to many engineers. However, I'd rather than than the break things and ask for forgiveness model like some other companies (not going to name names here)

> Given that segfaults almost never happen in the JVM (I've never seen one)

I've seen 5 segfaults over the last week in our system. Unfortunately we don't enable core dump in our system (yet) so we haven't really had a good sense of what might cause the system. We've been seeing about 30 SIGSEV's over the last three months, but we haven't been able to root cause it yet.

Anything that's convenient for them, I guess?

You don't even bother to read past the section about the limitations that the engineers were well aware of in advance - they re-emphasize a common concern for people who question their choice of JVM.

The next line reads: "As a result of these factors using the filesystem and relying on pagecache is superior to maintaining an in-memory cache or other structure—we at least double the available cache..."

And if you don't know about pagecache, it's an in-memory cache managed by the OS and has nothing to do with JVM's memory at all.

And you forgot that C++ isn't the easiest language when it comes to designing a distributed system. Scala, as I mentioned, offers many other features that suit the needs of the team. Of course if you're a good engineer you'll know that there are trade-offs such as compiling time, but that's the same for every engineering decision.

My flickr account is created with Google login. I wonder whether they'll force me into singing up for Flickr cause it's the service with most storage for photos out there (albeit the lack of desktop sync).

Yes, from the server side's mishandling of TXT extension. Probably the server put the MIME type in the HTTP header as "HTML" instead of TXT, and the browser renders the page as such.

Father? It's the second item on the list for me (and I use incognito)