The Elm Architecture
github.com
The Elm Architecture
1–10 of 38 posts
Re: The Elm Architecture
#2So out of all the compile-to-javascript languages out there, elm is easily my favorite, despite not being usable outside the browser. This article is one illustration why it is so attractive: app architecture that is blindingly simple (its all just state machines under the cover, which is exactly what a UI is).
Now all we need is an elm that compiles to native code that somehow can do what React Native is doing for the native interface. I would easily pay 3-5x Xamarin's prices to be able to do so. Who's up for it?
Re: The Elm Architecture
#3My experience with Elm was that it's very elegant and fun to work with if you are building a purely clientside application, but once you need communication with server the APIs are not very well developed and it becomes a major headache.
Note that none of the examples in this page (or in any Elm tutorial I found) flesh out interaction with a backend.
Re: The Elm Architecture
#4So out of all the compile-to-javascript languages out there, elm is easily my favorite, despite not being usable outside the browser. This article is one illustration why it is so attractive: app architecture that is blindingly simple (its all just state machines under the cover, which is exactly what a UI is). Now all we need is an elm that compiles to native code that somehow can do what React Native is doing for t…
Haskell with an FRP library may work for what you want to do.
Reactive-banana looks good, though I haven't used it.
Re: The Elm Architecture
#5My experience with Elm was that it's very elegant and fun to work with if you are building a purely clientside application, but once you need communication with server the APIs are not very well developed and it becomes a major headache. Note that none of the examples in this page (or in any Elm tutorial I found) flesh out interaction with a backend.
Consuming data isn't hard. Creating a dashboard that displays the values sent down on an interval over a websocket is super easy.
Sending data isn't hard. Sending the mouse coordinates on a click to the server over a websocket is super easy.
There is, however, no easy way to consume data and send a response. To write an echo server, for example, you currently have to send the data to a javascript port and then read from the port to send it back.
Re: The Elm Architecture
#6So out of all the compile-to-javascript languages out there, elm is easily my favorite, despite not being usable outside the browser. This article is one illustration why it is so attractive: app architecture that is blindingly simple (its all just state machines under the cover, which is exactly what a UI is). Now all we need is an elm that compiles to native code that somehow can do what React Native is doing for t…
Haskell with an FRP library may work for what you want to do. Reactive-banana looks good, though I haven't used it.
I'll echo this. Elm was a bit of a gateway drug for me getting into Haskell. Haskell itself has a lot of very powerful tools.
Re: The Elm Architecture
#7My experience with Elm was that it's very elegant and fun to work with if you are building a purely clientside application, but once you need communication with server the APIs are not very well developed and it becomes a major headache. Note that none of the examples in this page (or in any Elm tutorial I found) flesh out interaction with a backend.
Consuming data isn't hard. Creating a dashboard that displays the values sent down on an interval over a websocket is super easy. Sending data isn't hard. Sending the mouse coordinates on a click to the server over a websocket is super easy. There is, however, no easy way to consume data and send a response. To write an echo server, for example, you currently have to send the data to a javascript port and then read f…
Yep, it was specifically when I wanted an application that would run a game loop involving round trips to the backend for every step that I ran into a lot of difficulty. Ports were not very clearly documented and I didn't find any examples, so I wound up writing Javascript instead.
Re: The Elm Architecture
#8My experience with Elm was that it's very elegant and fun to work with if you are building a purely clientside application, but once you need communication with server the APIs are not very well developed and it becomes a major headache. Note that none of the examples in this page (or in any Elm tutorial I found) flesh out interaction with a backend.
Consuming data isn't hard. Creating a dashboard that displays the values sent down on an interval over a websocket is super easy. Sending data isn't hard. Sending the mouse coordinates on a click to the server over a websocket is super easy. There is, however, no easy way to consume data and send a response. To write an echo server, for example, you currently have to send the data to a javascript port and then read f…
Yep, it was specifically when I wanted an application that would run a game loop involving round trips to the backend for every step that I ran into a lot of difficulty. Ports were not very clearly documented and I didn't find any examples, so I wound up writing Javascript instead.
Re: The Elm Architecture
#9My experience with Elm was that it's very elegant and fun to work with if you are building a purely clientside application, but once you need communication with server the APIs are not very well developed and it becomes a major headache. Note that none of the examples in this page (or in any Elm tutorial I found) flesh out interaction with a backend.
Consuming data isn't hard. Creating a dashboard that displays the values sent down on an interval over a websocket is super easy. Sending data isn't hard. Sending the mouse coordinates on a click to the server over a websocket is super easy. There is, however, no easy way to consume data and send a response. To write an echo server, for example, you currently have to send the data to a javascript port and then read f…
I ended up implementing this in JavaScript using Rx, but the core concept is the same:
Incoming requests: --a------------->
Requests to server: ---b------------>
Responses from server: -----------d---->
Updates to app state: ---c--------e--->
b - Handler for that action queues a request
c - Handler for that action also queues a local update
d - Server responds with the sent message
e - Handler for that response queues a local update
Re: The Elm Architecture
#10My experience with Elm was that it's very elegant and fun to work with if you are building a purely clientside application, but once you need communication with server the APIs are not very well developed and it becomes a major headache. Note that none of the examples in this page (or in any Elm tutorial I found) flesh out interaction with a backend.
[deleted]