TEA

[ShalokShalom]

Do you want to request a feature or report a bug?

Feature

What is the current behavior?

FRP

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

http://elm-lang.org/blog/farewell-to-frp

What is the expected behavior?

I have no expectations :slightly_smiling_face:

What is the motivation / use case for changing the behavior?

Simplicity

Which versions of ReactiveUI, and which platform / OS are affected by this issue? Did this work in previous versions of ReativeUI? Please also test with the latest stable and development snapshot

All until

Other information (e.g. stacktraces, related issues, suggestions how to fix)

[ghuntley]

?

[ShalokShalom]

Why is functional reactive programming used, instead of the TEA concept?

Is there any difference in this project, which counters the benefits?

How is the Elm architecture eventually implementable into ReactiveUI?

[quinmars]

The word/abbreviation isn't used at all in the linked article.

@ShalokShalom may you explain what it is and how ReactiveUI can profit from it?

[ShalokShalom]

It means "The Elm Architecture"

Elm basically invited FRP and it turns out that they found another, similar concept, which works out to be simpler. :slightly_smiling_face:

It is also implemented in OCaml with Bucklescript-TEA and F-Sharp by Fable-Elmish

[marcpiechura]

If you want to use TEA with WPF you can use https://github.com/Prolucid/Elmish.WPF

Elm basically invited FRP

Not really, ReactiveUi has implemented FRP before Elm exist and the concept is probably even older. Also I don’t think WPF and TEA fit well together. Once you need to handle big lists or grids immutability will kill performance in WPF.

GitHub

Prolucid/Elmish.WPF

Elmish.WPF - WPF bindings for fable-elmish.

[ShalokShalom]

.Net is for more as Windows.

[marcpiechura]

Haven’t said otherwise just gave you some options for WPF and afaik Don Symen is working on Elmish for Xamarin Forms.

[ShalokShalom]

Thanks :)

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want this issue progressed faster please start a conversation about raising a pull-request or coordinating your pull-request with a maintainer to get it merged. Understand that if folks like yourself don't contribute, ReactiveUI won't grow. You may or may not know this but ReactiveUI is maintained by unpaid volunteers. The maintainers put up a big marketing front but at it's core is a couple of passionate folks. ReactiveUI cares about open-source sustainability as maintainers have a serious load on their shoulders. Consumers shouldn't be naive in thinking that the latest update to a nuget package just magically materializes from the ethers. These things happen because our peers make them happen. No-one wants a tragedy of the commons situation. I urge you to get involved. Thank-you.