iced VS elm-architecture-tutorial

I've worked with Iced .NET Assembler in the past, and it shouldn't be too much trouble to use it make a trampoline.

An unfortunate name clash with one of the best x86 decoders I've ever used, also written in Rust[1].

[1]: https://github.com/icedland/iced

I'm learning Haskell right now, pure functional language, but if anyone is interested, Elm is based on Haskell and much easier to learn. Elm is a web development language that compiles to JS. https://guide.elm-lang.org/

Elm is a different approach that compiles into JavaScript. In the extreme case, you have Emscripten which will compile many language into JavaScript but will feel really clumsy compared to using JavaScript in a lot of cases.

And if you want to stay in the UI realm, Elm is a good introduction into functional programming.

If you want to get better at data structures you should strongly consider learning a functional language. A huge part of functional programming is manipulating data structures. The language Elm is a great place to start for you since it's frontend specific. For example, check out the doc page for the Dict data type and see if that kind of stuff is what you're looking for.

https://guide.elm-lang.org/ for a high level guide, and an unstyled button example https://elm-lang.org/examples/buttons.

I hope this tiny guide was helpful, and that you learned something new today. If you want to learn more about Elm, you should check out the official guide or say hello in the Elm Slack #beginners channel

https://guide.elm-lang.org/ is always a solid example for me

After going through the whole Introductory Guide to the Elm Language and reading the Elm in Action book, I already felt quite comfortable developing webapps in this paradigm. I liked Elm so much that I started a project to teach programming to beginners using this language and made the first classes available on the website elm.dev.br (in Brazilian Portuguese).