4 ms·
Haskell with an FRP library may work for what you want to do. Reactive-banana looks good, though I haven't used it.
by wz1000 12y ago
Haskell with an FRP library may work for what you want to do.
Reactive-banana looks good, though I haven't used it.
- phamilton 12y agoI'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.
- platz 12y agoThis post builds the intuition for something like the Netwire library http://blog.jle.im/entry/effectful-recursive-real-world-autos-intro-to-machine http://blog.jle.im/entry/effectful-recursive-real-world-auto...
- photex 12y agoThe trouble though comes about once you have to start working with a UI library. It's a mess and a half unless you use C++. I'd like to try using Elm, or Purescript for UI work using atom-shell or nw.js. That opens almost the same can of worms (how easy it might be to 'bind' your engine to your UI/view). I've written a non-trivial application using QtWebkit entirely for the UI and it was a very agreeable experience. The engine of this app was C++ but it got my gears turning.
- pjmlp 12y agoActually that I my opinion from any web based UI, a mess of JavaScript/CSS trickery and HTML. Native UI development feels so much more advanced and user friendly. Saying this as a UX developer since the mid-90's.
- photex 12y agoMy comment was in reference to using native toolkits from a language other than C++ and not the status of using native toolkits in general. <friendly-joke>I have a hard time believing that you've been using native UI toolkits using Haskell since the mid-90s.</friendly-joke> :)
- pjmlp 12y agoNo, but I was using Turbo Pascal followed by Delphi. Also played with C++ Builder, but by then Visual C++ had taken over as Borland was going through their Inprise phase.