elm-ui VS hotwire-rails

It's been a few years, but last time I built a non-trivial Elm app, I used elm-ui. Otherwise, I've used either vanilla CSS with the Meyer reset (am I dating myself?) or SCSS.

"clean" means you are used to it. ELM is a totally new language (not like JS and TS) based on a paradigm (functional programming) that you are probably not used to. And it is based on the ML type system (different from what you are used to). So it is a lot of new things at once. "Reinventing the wheel" is an unfortunate side-effect of using a different way to do things. Some things can be copied verbatim, some are totally different. Check out "elm-ui" (https://package.elm-lang.org/packages/mdgriffith/elm-ui/latest/) for a very different and refreshing view in UI code in ELM (that will appeal to the mostly-backend developers in your workplace).

I use Elm for my project. Once you accept thinking the way it wants you to, it's a delight to develop front-end with it.

Side advantage, Elm-UI frees you from CSS: https://package.elm-lang.org/packages/mdgriffith/elm-ui/late... it's like Tailwind but deeply intertwined with the language.

https://elm-lang.org

The last advice I could give is to try elm-ui (https://github.com/mdgriffith/elm-ui) for your user interface. It's amazing how great that is compared to traditional ways of building a frontend layout.

The library elm-ui makes it easy to create a nice user interface. I am unaware of anything similar for Rust+WASM, so I would have been forced to deal with HTML and CSS.

There are several things named elm-ui. It's the author of a different library than what is usually understood when someone refers to elm-ui (which is https://package.elm-lang.org/packages/mdgriffith/elm-ui/late...)

Foregoing CSS all together by using a different approach to UI construction (elm-ui)

Right now I'm just using the built in from the UI library I used for the sake of ease as I didn't find a perfect solution and it seemed good enough for now: Github Link to source, which it looks like would classify your laptop as a tablet, whoops!

Applications generated with Rails 7 will get Turbo and Stimulus (from Hotwire) by default, instead of Turbolinks and UJS. Hotwire is a new approach that delivers fast updates to the DOM by sending HTML over the wire.

For Ajax-y stuff, I am really excited by the new crop of "HTML-as-a-Service" or "HTML-over-the-wire."

https://htmx.org/

https://hotwired.dev/

For all the turbo/stimulus/hotwire mix, you want to add a new feature just for the sake of adding it? or do you have a use case that fits the feature? if you have then you probably already have an implementation with a different technology (stimulus reflex? some custom websockets or ajax implementation? something with anycable?) and you have to check how to migrate from that technology to hotwire. If you just want to use the feature with no real need for it to practice then just pick any tutorial from the internet (like the intro in the official website https://hotwired.dev).

I was recently interested in similar topic. Here are 3 similar solutions I found:

* https://htmx.org/

* https://unpoly.com/

* https://hotwired.dev/

My personal preference is Unpoly (the idea of "layers" is awesome). But the best explanation of concept as a whole (HATEOAS, keeping app state on server using partial page updates, etc) is at HTMX homepage, and in these essays:

* https://htmx.org/essays/hateoas/

* https://htmx.org/essays/locality-of-behaviour/

At the end of 2020 the Basecamp team released a collection of Javascript libraries called Hotwire. Modern web stacks have popularized javascript-rendered front ends and JSON transmissions. Hotwire's primary motivation is to reduce the Javascript footprint and allow application front ends to be created in primarily HTML. It pairs very nicely with the Ruby on Rails ideology and is often demonstrated in that context. I aim to write a series on how Hotwire can be used in any application to simplify development and reduce the need for heavy Javascript downloads. Hotwire currently consists of two javascript libraries: Turbo and Stimulus. The first part of this series introduces Turbo.

I've been doing that a while until I just got sock of the JS spagetti and often duplicated code and went full on Angular CSR and never looked back. That being said, I've been seeing a lot recently about Laravel's Livewire and Symfony and Ruby on Rail's integration with Hotwire (stimulus+turbo).