RFC: Next-gen IPC about gluon

[CanadaHonk]

Thanks for the comments and praise! Cool library as well. To briefly address each main point:

1. I am aware of this now and plan to change in the next major release.
2. Good idea, I'll likely add a dedicated ipc.store.onChange or something of the sort soon.
3. This is a pretty neat idea although don't want to make things too complicated, will discuss the idea around to get some thoughts.

Happy to talk more on Discord too.

[amiller-gh]

1. Great to hear!
2. Awesome, that'll make frontend framework integrations a breeze. Since the state objects are also user-defined-key-dumping-grounds, it may be good to consider an api like Gluon.onStoreChange(myStore, (...args) => { /* callback */ }) to avoid polluting the namespace in the same way as point 1.
3. An IPC State / Method object factory may be a nice internal model to take for code organization regardless, even if you never expose the factory functions and simply use it to create the single "global" state / method objects on Gluon.ipc used now. That would give the project the flexibility to choose to expose the factory functions in the future, even if it's buried in the documentation as an "advanced" feature. A lack of name-spaced objects would def block our larger app's adoption in the future, but 100% hear you on the complexity argument for the average user.

Will see you on Discord!