4 ms·
Is there any paper describing the concepts behind this project ? Is this seems very similar in its goals from the OTP architecture (from a distance), i’m curiou
by bsaul 7y ago
Is there any paper describing the concepts behind this project ? Is this seems very similar in its goals from the OTP architecture (from a distance), i’m curious to understand more about the first principles that guides the design.
- johnson_brad 7y agoMore (and clearer) documentation coming very soon, but here's a good start for the basic SwimOS concepts (Web Agents, Lanes, and Links): https://www.swimos.org/concepts/ https://www.swimos.org/concepts/
- WolfOliver 7y agoFor what does OTP stand for? Would like to google it.
- isodude 7y agoI assume this http://erlang.org/doc/system_architecture_intro/sys_arch_intro.html http://erlang.org/doc/system_architecture_intro/sys_arch_int...
- toolz 7y agoOpen Telecom protocol....the name is basically meaningless but I'm guessing ericson had no way of know how genetically useful it would end up being at the time.
- conradfr 7y ago"Any sufficiently complicated concurrent program in another language contains an ad hoc informally-specified bug-ridden slow implementation of half of Erlang." They do tag their project as "actor-model" so there is some similarity. However I see their communication model is designed to be more protocol agnostic.
- Natales 7y agoFunny thing is that a distributed, resilient, asynchronous message passing program in Erlang, is their equivalent of a "Hello World". It's so natural, and so well baked into the runtime itself, that it's hard to do something different. Good for the SwimOS folks to keep working in this important space, but I would have expected at least some mention of Erlang/OTP in their site, if nothing else, to understand the difference in approaches.