207 karma · joined January 16, 2015
- I think they did apply methodologies of reliability that worked in hardware, to software (e.g redundancy, automatic fault detection/tracing/correction)
- Also, in the early days, software was so tied to hardware, and hardware was faaar less complex, so they probably could understand everything that was happening in the system at a given time
Another thing, that is indeed linked on GenStage's page as a reference, is Lasp language [1].
If anyone knows more about this stuff, and could say if these cited things are even related, it would be cool to hear.
[0] https://github.com/elixir-lang/gen_stage - "GenStage is a specification for exchanging events between producers and consumers."
> x = [1, 2, 3]
> x = 2 # the structure [1, 2, 3] still exists in memory, but now the variable x is bound to the value 2
All data is still immutable, the BEAM itself requires so. Dave Thomas explains this in its "Programming Elixir" book.
Btw, I bet Edward Lee¹ would like this game.
¹ http://www.eecs.berkeley.edu/Pubs/TechRpts/2006/EECS-2006-1....
(note: I'm not an English native speaker)
Interesting.