3 ms·
Facinating how this sounds - to different people - like event sourcing, functional programming and "software transaction memory". Are people interpreting using
by blowski 4y ago
Facinating how this sounds - to different people - like event sourcing, functional programming and "software transaction memory".
Are people interpreting using their own experience, or is there a big overlap?
- greenbit 4y agoTo a hammer, everything looks like a nail?
- mrkeen 4y agoEvent sourcing is one way to approximate functional programming in the large. STM provides (compositional) thread-safety within a single process. It requires FP but other than that I don't see the comparison.
- marcosdumay 4y agoTo me, it sounds a lot like the part of functional reactive programing that nobody bother to explain or specify. But, well, I'm not really sure people mean that when they talk about it, because it's left unespecified. And when people implement FRP they always seem to take obvious "shortucts" with significant downsides and that avoid implementing something like this.
- thwayunion 4y agoThere's a big and historical overlap. Now these are all distinct topics of study, but in the 80s when these ideas originated there were precious few CS departments. Most all of the software scientists knew each other and were kind of swimming in the same primordial soup of ideas.
- quickthrower2 4y agoAnd React/Redux :-)
- aappleby 4y agoAuthor here. There is a _huge_ overlap between a _wide_ variety of programming terminology, which is why one of the motivations of temporal programming is to bring all these various ideas under one relatively simple umbrella.