4 ms·

Will do. Thanks for the pointer. Do you have any suggestions offhand?

• seanmcdirmid 12y ago
  Start at the beginning: http://conal.net/fran/tutorial.htm http://conal.net/fran/tutorial.htm Warning: FRP is much more purest than Rx (which is just data flow) or Elm (which is more FRPish but asynchronous). You probably don't want FRP but something more pragmatic like the fore mentioned systems.
  • newgame 12y ago
    From what I understand, although Conal Elliot coined the term FRP first in a relatively narrow sense, today the term FRP is used much more freely to describe reactive programming using functional building blocks (especially combinators like map, filter etc.). There are some nice papers that give an overview of the FRP landscape. “A Survey on Reactive Programming”: http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.416.1589&rep=rep1&type=pdf http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.416... “Towards Reactive Programming for Object-oriented Applications”: http://www.guidosalvaneschi.com/attachments/papers/2014_Towards-Reactive-Programming-for-Object-Oriented-Applications_pdf.pdf http://www.guidosalvaneschi.com/attachments/papers/2014_Towa...
    • platz 12y ago
      These papers actually look readable. I'll give them some time, thanks for posting!
    • seanmcdirmid 12y ago
      This is not true at all. It is only recently and only in the SF hacker bubble that FRP has been co-opted to mean anything that is functional, reactive, and programmed. Outside, FRP still means FRP, and using the term will automatically put your work in a certain specific bucket that you might not want to be in.