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.
Thanks for the information. If files on disk are a requirement that would be a shame. Such tools keep abstracting such that one can generate a plethora of output formats but don't abstract the input in such a way that one could programmatically add content. Even though that wouldn't stand in the way of using the filesystem as the source regardless.
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.
The fact you've copied screen.studio so closely leaves a bad taste in my mouth. On the landing page you apply formatting in Google Sheets, just like screen studio does. It's ok to be inspired by screen studio but remember they are mostly a solo dev too so try and be more original.
we live in capitalism. capitalism is competing with others to make money. there are legal protections in place for intellectual property, and those protections are already far too damaging to innovation and creativity. he's operating within legal boundaries and doing the same thing everyone else does in business. i don't see the problem as long as it isn't illegal.
if we want to talk about ethics and morals in capitalism, then we have to start with the discussion of how all of it is damaging, and not just blame isolated examples as damaging or "bad"
No one said it's illegal. They said it leaves a bad taste. I also don't think this particular comment was necessarily a critique of capitalism as a whole.
Not OP but was there 15 years (left Dec 2021) and surprised I wasn't aware of this. I was only aware of a few tools that acted like chatbots to automatically gather context or take action from chime/tt/alarms.
When I was at AWS, I built something so I could run things straight from the wiki. Think cloudwatch queries, aws cli commands etc with user inputs but without all the setup of securely getting the right credentials and formatting inputs. I've rebuilt to run stuff straight from GitHub. Here's it invoking a lambda function straight from a github wiki with user input in 4 lines of code: https://speedrun.nobackspacecrew.com/index.html#invoking-an-...
The video on your landing page is too long for my tastes. A 1-5 minute video quickly showing the features would have more impact than your 20 minute walkthrough attempting to show every detail. The 20 minute video is more suitable for the documentation.
They do give Leonardo a lot of credit for a single sentence, but it may be the first documented instance of this charring technique.