Generators => OS

[Mototroller]

Hi! Firstly I want to say I'm impressed by such a project, and wish good luck for all its (future) contributor(s)! :)

My point is about possible extension of the project: for example, I've used generators-based approach to develop a skeleton of lightweight serializable operating system. For now it's just a beginning, and I'm in the middle of some game engine reworking, but I think it can be interesting for contributors to use generators-based design to implement their own schedulers and even whole OS'es.

The implementation mentioned above uses only lodash library and ES6 features (which are available in the game), I'll be happy if it would be useful for someone. More information about Screeps OS'es and crazy community can be found at this Slack channel.

[CGamesPlay]

Hey! I absolutely agree, an operating system is an essential companion to this tool. I am currently working on a simple kernel to help test the limits of this system and I'll gladly accept bug reports on one you work on as well. Here are some things to think about as you build one out:

• When the code for a generator is changed, the generator is immediately aborted. The OS for the API needs to embrace processes (generators) that crash and provide tools to allow them to resume.
• Only local variables are serialized, so storing a reference to a global variable as a local variable will cause the referenced object to be cloned after serialization. This will lead to crazy bugs, so the OS should provide a mechanism for ensuring they get serialized or else strongly discourage using global variables.
• The OS will need to manage Memory. More processes = more Memory, and you'll run out eventually. I might even go so far as to think about how you can use RawMemory to set precise memory limits per process.