3 ms·
This style is plenty useful in "higher level" stuff. Consider Reflex: http://docs.reflex-frp.org/en/latest/ http://docs.reflex-frp.org/en/latest/
by kmicklas 9y ago
This style is plenty useful in "higher level" stuff. Consider Reflex: http://docs.reflex-frp.org/en/latest/ http://docs.reflex-frp.org/en/latest/
- runeks 9y agoI don’t think I understand the reference. Reflex is a library, used to create applications. The actual application code doesn’t seem to adhere to any type of functor-oriented programming, as far as I can see: http://docs.reflex-frp.org/en/latest/architecture.html http://docs.reflex-frp.org/en/latest/architecture.html
- kmicklas 9y ago> I don’t think I understand the reference. Reflex is a library, used to create applications. Yes, but typical uses would be mobile apps and web apps, pretty "high level" stuff. > The actual application code doesn’t seem to adhere to any type of functor-oriented programming, as far as I can see: http://docs.reflex-frp.org/en/latest/architecture.html http://docs.reflex-frp.org/en/latest/architecture.html https://hackage.haskell.org/package/reflex-0.4.0/docs/Reflex-Class.html https://hackage.haskell.org/package/reflex-0.4.0/docs/Reflex... The entire library abstracts over its implementation via the "Reflex" class. This is not _exactly_ the style advocated in the original post, but it's basically the same spirit.