Thanks for clearing up what you mean by concurrency. While your explanation makes sense in terms of events, time and reactors, I'm a little unsure about global effects... This example may demonstrate: 0) two reactors are linked to an event 1) the event occurs 2) one of the reactors runs and sets a g...

Could you explain how this counts as concurrency? How would more than one event be triggered at a given time? And if things are limited to non-simultaneous events and your reactors are forced to act atomically, how will the program ever have more than one active execution point at a given time? Am I...

I'm not talking about the zoom level.

To be more precise:

0) start (size = original_size)
1) emit a bubble (to move) (size = size - bubble)
2) re-absorb it (size = size + bubble)
3) your size is now bigger than the start! (size > original_size)

Fun start, but in case you didn't realise, your system does not conserve mass... If you get almost all the bubbles, then start zooming around and then collect all your bits again, you are bigger than when you started. Repeat, get bigger, etc. Until you are bigger than the entire viewable area. Is th...

Robin: Sure, you can move things to the special love dropzone, though I'd feel bad about pestering a player to jump through hoops like a monkey. On the other hand, I've though more about how the whole small-quick-n-dirty game thing works, and the way people try/discover/discard lots of games and don...

Robin: re your sandbox.lua That's kind of what I'm getting at, but totally wiping out the io table is problematic. Think of a game where part of the game world can be constructed from photographs taken by the player... maybe putting a face on a character. This needs some kind of io function outside ...

Another though... make a cage using love. For people who are worried about security, there is always the option of running love inside a love sandbox. It could be built from love instead of into love... this is the standard lua approach to dealing with untrusted code. To address the convenience fact...

Another problem with sandboxing is the assumption of what constitutes a game. Just because your game ideas don't usually need to do something, doesn't mean someone else will be happy with the same restriction. Look at all the things people have done with the net that could not have been envisioned 1...

Not sure if it was your intention, but you just did a great job detailing some of the reasons my system is gloriously emacs free. Like I said, I avoid programs that try to do too much... just a matter of taste.

Ah... well I suppose it's complex if you want it all happening in the one app. Coming from a unix background, I find it more natural to keep things simple and leverage the system for more complex functionality - in this case just tiling several xterms with vim running on a different file in each one.