dirtydroog

I'm not talking about what I see in my browser, I'm talking about services communicating in a private cloud, and I'm quite sure the author was too.

Thanks for the list of HTTP/2 implementations. I hope they all interpret the spec the same and so can all be used with each other.

HTTP is overly verbose, is a pain and slow to parse, and there are various interpretations of what the protocol spec allows and disallows. If machines are communicating why should it be in a human readable format? Binary is far quicker

HTTP1.1 only closes the connection if one party sets Keepalive: Close. It was HTTP1.0 that was one-shot. There was also pipelining support added but apparently nobody bothered to support it.

Somewhat related to the RPC argument, but HTTP is a total joke, adn therefore so is REST.

In adtech you send 204 responses a lot. The body is empty, just the headers. Headers like 'Server' and 'Date'. Apache won't let you turn Server off... 'security through obscurity' or some nonsense. Why do I need to tell an upstream server my time 50k times per second?

Zip it all up! Nope, that only applies to the body which is already empty.

Egressing traffic! A cloud provider's dream. I wonder what percentage of their revenue come from clients sending the Date header.

I remember similar things being said about nokia

20mb? My latest nvidia 'driver' download was over 500mb and prompted me to log-in to something before installing.

medium.com articles define the software development practices of most companies.

It's a bit of a joke.

Well, we moved to it from Cassandra. It's yet to fall over and we're querying it maybe 200k times per second. No changes were needed from the client driver side of things too. YMMV.

Exactly. When markets are volatile I imagine they find it difficult to manage risk and so just shut everyone out and blame it on IT.

If you used Scylla you'd have only needed 90 nodes. (Don't believe the instability rumours)

Companies like Robinhood regularly go down when markets are volatile. It was quite frustrating when the financial crisis was in full swing not being able to log in to my trading account. I reckon I would have made a killing.

As so that's what Improbable do. They're tried to hit me up on LinkedIn several times.

The amusing thing is that he complained about this on Twitter. Twitter... the 4chan of messaging.

As far as I'm aware, node.js is a wrapper over libuv which is a truly asynchronous socket IO library. It fakes file IO async ops with thread pools because on Linux file IO isn't async at all.

Why. Why should I have to google it?

I can recall being taught about acid rain in Ireland in the 1980's

I didn't believe you but you're right. The uint8_t gets promoted to int, not unsigned int.

https://godbolt.org/z/icQHw3

> It takes O(n*n) time to add the n integers.

Eh?

What 'YC' is wasn't explained by the end of the first two paragraphs so I stopped reading.

Twitter is a joke. I don't know why anyone uses it.

About a year ago I was writing a personal profiling framework in C++. To test it I profiled how long it took to get the time and if it was scalable (multiple threads making the same call don't interfere) ran it on Windows, and a Linux guest on a Windows host, and an AWS instance. Your post finally explains why the AWS graphs were all over the place!

Github's diffs are pretty much instantaneous, Bitbucket just gives up, "now that's a lot of code!". No, it was a one line change actually.

Still miles better than BitBucket.

We actually did have a dedicated Googler who oversaw our move from AWS to GCP. I asked him about it but never got a reply.

Anyway, yes. It caused us problems. Attempts to connect to machines outside of GCP would fail repeatedly due to the NA dropping the SYN. This would mean our connect() call would timeout repeatedly. There was an ICMP response I could see with tcpdump:

ICMP host aaa.bbb.ccc.ddd unreachable - admin prohibited filter, length 68

Same

Did your instances have external IPs? We had connectivity issues when using NAT due to it dropping SYN packets. We just gave everything that needed to talk to external IPs their own external IPs.

We moved to GCP from AWS because we thought it'd be cheaper. Turns out it wasn't that much cheaper at all. But Google paid for the transition so there's that...

'if twelve cows are lying down it's gonna rain'

QED

I was in Nokia at the time. As soon as it was released onto the intranet news feed, a couple of thousand employees immediately stopped caring and were more focused on hanging around for their redundancy payment.

The Nokia London office had an emergency Town Hall session in The Oval cricket ground building where execs tried to convince us that Symbian was safe. Those claims were met with actual laughter from the crowd.

Not true, Symbian was highly locked down. You needed permission for pretty much anything, and some of them required you to ask Nokia for permission. It's probably part of the reason why it didn't take off in the US.