You could take a look at SELÖVE, a (severely out of date) fork of LÖVE that is intended to make it safe to run arbitrary .love games. (It used to be on bitbucket, but it looks like it's gone? I'm not sure if I have the repo locally :/)
Running arbitrary code was such a problem that I just completely ruled it out for bitser. Instead of serializing functions, you can register safe functions as resources. This doesn't solve the upvalue problem, though.
Not exactly. The headline is a bit misleading imho: the article doesn't say that CO2 uptake by plants is up by 31%, rather that new estimates of the CO2 uptake by plants is 31% higher than previous estimates. That doesn't preclude a temporary collapse of carbon absorption (related mostly to forest fires as far as I can tell).
> related mostly to forest fires as far as I can tell
Just trying to parse this - does that mean "a collapse in carbon absorption" actually means "more carbon was produced for the same amount of absorption"?
I work with files every day, and I'm not sure I would have realised I'd needed to save manually with the original MapHub UI either. A web-based interface that looks like that, I expect it to be transparent. If it'd had three icons (the classic blank page, open folder and floppy disk) in the top left, then I'd assume it would need manual saving. (I'm not saying that's what you need to do, just analysing my own intuitions)
The interesting bit is that for years this wasn't a problem. Like for 5 years I got 0 support requests about missing Save. Also web apps were not auto-saving traditionally, many of them still don't do it today.
It's very possible that if you showed me the MapHub UI eight years ago, I'd have intuited that I'd need to save manually---I can't tell for sure. I am definitely aware that the way I engage with software nowadays is very different than when I started using computers in the early 2000s, and I don't doubt it is still evolving due to the changing conventions in UI and functionality.
