inai

This is useful! Thanks for writing this out. I find in-process REST intriguing as it stands a little in contrast with OOP techniques. One possibility I’ve found with in-process REST is that it seems to make live patches feasible - more feasible than in erlang. I use the idea as the core of Inai - https://github.com/imaginea/inai (post describing it https://labs.imaginea.com/inai-rest-in-the-small/) ... so am curious to play with that aspect of ObjS.

A shameless plug - but I'm attempting to build a kind of "deploy first and develop as you go" kind of system for this, inspired by the Smalltalk IDE and VM. Link - https://github.com/imaginea/inai Associated post - https://labs.imaginea.com/inai-rest-in-the-small/

A bit of a shameless plug, but really looking for feedback .. I've been experimenting with Inai [1][2], a framework that can help build modular microservice-like software with similar Dev team independence properties but can independently be built and deployed as a monolith or as separate services operationally. So far, I've had fun building an internal project at much higher speed than I've managed any similar project and had more fun doing it. I feel the idea (which is still nascent) has some merit, but would like to know what folks think. [1] source - https://github.com/Imaginea/Inai [2] blog post describing Inai - https://labs.imaginea.com/inai-rest-in-the-small/ PS: I've had some difficulty characterising Inai (as you can tell).

At some point, this would be come close to the AppleScript protocol or Symbian OS. > So the drawing part of an application would just be a process that sends the screen/compositor process a message describing the state of its window as a tree, and receives messages for events in response. I've been toying with an interpretation of this here - https://github.com/Imaginea/inai - and kind of having fun with it .. and even built a prototype internal app using it. Super early stage and so stuff won't necessarily make sense at the outset .. or possibly ever. Thoughts welcome though. > A big advantage is it makes the semantics of composing GUIs a lot more reasonable "replace this leaf of my tree with this other process' tree" ... The "dom" service in Inai pretty much feels like that. I felt like an idiot to try and (for lack of a better expressi

> direct his anger to "make good art" Here is one from me with the solo-dev/small-team in mind - https://github.com/imaginea/inai . Good or not I don't know. It came out of some reading I was doing and I'm having fun with it due to the "deploy first and then dev" mindset it encourages.