qidydl

I'm surprised that something like routing software is/was being distributed via snap instead of as a Docker container; snap seems much more targeted towards end-user workstations than to servers.

Python's datetime appears to have one constructor with several optional parameters, whereas .NET's System.DateTime has several separate constructors each taking a different set of parameters. The MSDN documentation is accurate and correct; your critique applies to the underlying code (which is built to be backwards-compatible to .NET 1.0, which I don't think even supported optional arguments).

It's scary this comment appears to be getting downvoted. Having more than two driven wheels does not change the contact patch on the road, does not add braking capacity, and does not grant additional steering. Being able to steer and stop is usually more important for safety than being able to accelerate, and even then, if you don't have the friction you'll just end up spinning all four wheels instead of just two. Tires are the most critical part of a car.

They addressed this in the article:

> These latency spikes definitely smelled like garbage collection performance impact, but we had written the Go code very efficiently and had very few allocations. We were not creating a lot of garbage.

The problem was due to the GC scanning all of their allocated memory and taking a long time to do so, regardless of it all being necessary and valid memory usage.

I knew Cliff first as my dad's old college buddy, so it's always a little wild when articles about him show up. He's an actual human being and a good person, so I hope the scrutiny and craziness of public attention doesn't give him too much trouble.

I have experience deploying to Fargate from ECR and we didn't need to configure any sort of S3 access to do it, certainly for the ExecutionRoleArn. ecr:BatchCheckLayerAvailability, ecr:BatchGetImage, and ecr:GetDownloadUrlForLayer on the ECR repos was sufficient.