Richard Bucker

something to try in erlang

Posted at — Dec 22, 2014

I have been working on a flow based programming implementation that would be implemented in go. Part of what would make it successful is that all of the nodes would exist in one package… even main. In this way all nodes are global.

While I have yet to figure out if there are practical limits to the number of public objects in a package I’m also wondering whether or not modules are necessary in erlang. As the major downfall of hot plugging is that the version is by module only and if you have to update multiple modules the transaction repro is sacrificed. But if the application were implemented in a single module as I suggested the FBP application then would hot plugging be more reliable?