Having worked on a large website with an Elm front-end, I probably wouldn't use myself if faced with a similar task, but I'm a big fan of the model, view, update architecture.
1
Discussion
Loading...
@[email protected] Spicy take! Now I'm curious: why would you choose both MVU and not to use Elm?
1
My instincts are against leaky abstractions. You can't forget JS when using Elm, and you have to worry about the bridge. Why not just take the excellent MVU architecture and implement it in TS? Also I have a personal taste for curly brackets. Irrational I know.
1
@[email protected] No, that's fair and I'm on record as liking Elm for teams but not reaching for it for personal projects (partly because of JS interop) so I get where you're coming from.