3 ms·

imo rails without react and leveraging hotwire is going to be the next big thing in web dev. react is a huge increase in complexity for not much appreciable gai

imo rails without react and leveraging hotwire is going to be the next big thing in web dev. react is a huge increase in complexity for not much appreciable gain. you are not facebook and don't have facebook's needs. rails is nimble by itself.

kirso 4y ago
I would love to learn more about this. As a complete beginner though I tried to find resources for full-stack Rails and unfortunately there is nothing much there that teaches you the new front-end or shows how to build an MVP. Compared to that JS ecosystem perhaps has too much :)
- weaksauce 4y ago
  Hotwire is pretty new but there are some guides out there. it's a progressive enhancement thing generally so you build it normally and then sprinkle in the extra stuff. 1000 foot overview: https://boringrails.com/articles/thinking-in-hotwire-progressive-enhancement/ https://boringrails.com/articles/thinking-in-hotwire-progres... a tutorial: https://www.hotrails.dev/turbo-rails https://www.hotrails.dev/turbo-rails a video tutorial: https://www.driftingruby.com/episodes/hotwire-introduction https://www.driftingruby.com/episodes/hotwire-introduction probably a good paid option: https://pragmaticstudio.com/hotwire-rails https://pragmaticstudio.com/hotwire-rails and then there is the main site: https://turbo.hotwired.dev/ https://turbo.hotwired.dev/ cheers!
  - kirso 4y ago
    Thank you!
JeremyNT 4y ago
I'm a fan of this too, and it honestly confuses me that people would do a Rails API with React for a MVP. If you're already doing the backend in rails, it's hardly any more work to just do hotwire with server side rendering at the same time, and you can switch to a SPA later (if you really do need to).
- 0xblinq 4y ago
  Most people in this thread are not suggesting a stack for an mvp. They’re just listing their favorite stacks, that’s it. There’s a comment of somebody saying that just Postgres and Go. How on earth is that a good stack for building an mvp?? You’ll have to write a shit ton of code or glue together 10 thousand libraries.
- weaksauce 4y ago
  it's also not a ton more work to pivot and turn the rails app with hotwire into an ios/android app with a minimal amount of work. and yeah you can also sprinkle react in if you need some component or two or even do the api that way and drop into a full SPA if you really need that. but at that point you are doubling the amount of work on the frontend for little gain in my view. I liked the idea of react and have used it but i don't feel like it improves the situation enough for 95% of the sites out there to justify it and the enormous extra work there is in getting state/routing/etc to jive with the backend. I'm hoping strada, if it ever comes out, will be a large improvement to turbo native and at least provide a very compelling alternative react native.

kirso 4y ago

I would love to learn more about this. As a complete beginner though I tried to find resources for full-stack Rails and unfortunately there is nothing much there that teaches you the new front-end or shows how to build an MVP. Compared to that JS ecosystem perhaps has too much :)

weaksauce 4y ago
Hotwire is pretty new but there are some guides out there. it's a progressive enhancement thing generally so you build it normally and then sprinkle in the extra stuff. 1000 foot overview: https://boringrails.com/articles/thinking-in-hotwire-progressive-enhancement/ https://boringrails.com/articles/thinking-in-hotwire-progres... a tutorial: https://www.hotrails.dev/turbo-rails https://www.hotrails.dev/turbo-rails a video tutorial: https://www.driftingruby.com/episodes/hotwire-introduction https://www.driftingruby.com/episodes/hotwire-introduction probably a good paid option: https://pragmaticstudio.com/hotwire-rails https://pragmaticstudio.com/hotwire-rails and then there is the main site: https://turbo.hotwired.dev/ https://turbo.hotwired.dev/ cheers!
- kirso 4y ago
  Thank you!

JeremyNT 4y ago

I'm a fan of this too, and it honestly confuses me that people would do a Rails API with React for a MVP. If you're already doing the backend in rails, it's hardly any more work to just do hotwire with server side rendering at the same time, and you can switch to a SPA later (if you really do need to).

0xblinq 4y ago
Most people in this thread are not suggesting a stack for an mvp. They’re just listing their favorite stacks, that’s it. There’s a comment of somebody saying that just Postgres and Go. How on earth is that a good stack for building an mvp?? You’ll have to write a shit ton of code or glue together 10 thousand libraries.
weaksauce 4y ago
it's also not a ton more work to pivot and turn the rails app with hotwire into an ios/android app with a minimal amount of work. and yeah you can also sprinkle react in if you need some component or two or even do the api that way and drop into a full SPA if you really need that. but at that point you are doubling the amount of work on the frontend for little gain in my view. I liked the idea of react and have used it but i don't feel like it improves the situation enough for 95% of the sites out there to justify it and the enormous extra work there is in getting state/routing/etc to jive with the backend. I'm hoping strada, if it ever comes out, will be a large improvement to turbo native and at least provide a very compelling alternative react native.