![]() If I were you, I'd ask myself if I'm more comfortable with Ruby/Rails or Elixir/Phoenix, and I'd ask what other constraints (or motivators) exist and whether one of them would be a better fit - for example, if it's a work project and your company already mostly does Ruby stuff (in which case continuing with Ruby might be smart), or you know you'll need a mobile application, in which case you may have to build out that API back-end regardless.Ībsent other constraints (and assuming I'm working on it by myself), I'd probably start with whatever language/framework I know best and go from there, then solve problems like scale and usage as I run into them.įor me, this would mean building it with Phoenix and LiveView (though I've been using Ruby and Rails for about a decade). I haven't paid as much attention to the Ruby/Rails ecosystem since turning Elixir into my primary language a few years back. This has been steadily improving over the last few years from what I understand. In the past, Rails applications had somewhat limited support for web socket connections. ![]() The primary benefit to LiveView over Hotwire is you get the BEAM, plus the joy of a functional language and some built-in tools (the Presence API, Pub/Sub, GenServers and dynamic supervisors, etc.) that might make this problem more tractable, though not without the initial cost of learning. If you're dealing with large amounts of activity, you'll need to deal with that in some fashion. ![]() Both Hotwire and LiveView will give you the experience you're looking for.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |