it's a good opportunity to dive deeper into Hotwire (a modern HTML-over-the-wire solution)
I feel that's a big undertaking. Learning a framework like that I think would require a lot of new abstractions, best practices, and pitfalls to know about. If you're committing to using rails and want to double down on that, then I think hotwire may be useful here.
If the goal is to deliver, I would focus on a workflow you're already familiar with. Keep it "stupid simple". I recommend pursuing a workflow where you're able to easily write tests as you work.
Good point. The thing with Hotwire is that we already use it to build some views at my work. I haven't got space to work with, but I have some good examples on how to integrate it correctly.
I'm still going to just build simple HTML server rendered views in the beginning and then try to add some upgrades using Stimulus and Hotwire to make user experience better, but this assumes I'll already have something working.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I feel that's a big undertaking. Learning a framework like that I think would require a lot of new abstractions, best practices, and pitfalls to know about. If you're committing to using rails and want to double down on that, then I think hotwire may be useful here.
If the goal is to deliver, I would focus on a workflow you're already familiar with. Keep it "stupid simple". I recommend pursuing a workflow where you're able to easily write tests as you work.
Good point. The thing with Hotwire is that we already use it to build some views at my work. I haven't got space to work with, but I have some good examples on how to integrate it correctly.
I'm still going to just build simple HTML server rendered views in the beginning and then try to add some upgrades using Stimulus and Hotwire to make user experience better, but this assumes I'll already have something working.