Consider removing this from the landing page if you want to be taken seriously: "we are in the pursuit of greatness. fueled by
caffeine, nicotine, and pure chaos"
Agreed, maybe a forest fire or lightning strike might have made it more obvious that charring preserved. Charcoal in a campfire could have easily disappeared in the next fire.
They do give Leonardo a lot of credit for a single sentence, but it may be the first documented instance of this charring technique.
I found that Node 22 had ~50ms slower coldstarts than Node 20. This is because the AWS Javascript V3 SDK loads the http request library which became much heavier in Node 22. This happens on the newly released Node 24 as well.
I recommend that if you are trying to benchmark coldstarts on Lambda, you measure latency from a client as well. The Init Duration in the logs doesn't include things like decrypting environment variables which adds ~20ms and other overhead like pulling the function code from S3. The impact of this manifests when comparing runtimes like llrt to Node, the Init Duration is faster than Node, but the E2E time from the client is actually closer because the llrt bundle size is 4-5MB larger than Node.
This is not about the AWS Console. It is talking about the customer's site hosted on CloudFront. It is possible to cross wires with user sessions when using CloudFront if you haven't set caching granular enough to be specific to an end user. This scenario is customer error, not AWS.