There's a game I play (Old School Runescape) that does network ticks every .6s. Mac does some sort of aggressive optimization on the network hardware/software, so network this infrequent doesn't keep the layers "hot", and you end up getting delayed ticks regularly, meaning you learn what should be happening in the game .2-.5s late. This optimization for (I assume) battery life makes the software not work as intended.

Playing anything that streams, like video, or triggering TCP connections (e.g. curl) at a more frequent clip while the game is running fixes the problem.

No way other than hacks that I've found to fix it, and I have no idea how you could report this to the right team at Apple to get it actually fixed.

You could easily make human approval workflows for this stuff, where humans need to take any interesting action at the recommendation of the bot.

> It's made from a renewable resource (wood) and there's some 400+ million metric tons of paper production yearly

They don’t mean production volume, they mean physically. You can’t increase the thickness of paper by 1000x to just make thicker, stronger, paper. It’s a different material entirely.

That's pretty much always been true for greenfield that doesn't require large swaths of boilerplate (e.g. integrations)

It’s literally right at the end of their recommendations list in the article

Unless Extreme Potato Counter was sponsored by Big Potato...

Can I bet on the contrary odds? Could throw down my whole retirement with confidence

Support for the types of metaprogramming/metadata that annotations are used for is a useful attribute of languages in general

That’s exactly the pattern I use for most Go development

I think the most important one you get is that inputs/outputs must always be < 6mb in size. It makes sense as a limitation for Lambda's scalability, but you will definitely dread it the moment a 6.1mb use case makes sense for your application.