4 ms·
I don't quite buy it. Go with Rails if you like Ruby, Rspec, rapid development and the nice ecosystem around it. Most Rails apps are CRUD and don't really need
by joelbluminator 6y ago
I don't quite buy it.
Go with Rails if you like Ruby, Rspec, rapid development and the nice ecosystem around it.
Most Rails apps are CRUD and don't really need streaming with websockets. Rails with stimulus is more than enough to create a good user experience, I don't see why you need to add the complexity of websockets.
- jack_riminton 6y agoI agree for the most part but features are increasingly demanding a ‘real-time’ feed or updates of sorts Turbo is actually a rather simple way of achieving this with rails https://turbo.hotwire.dev/handbook/streams https://turbo.hotwire.dev/handbook/streams Which is something that would be very clunky for stimulus
- joelbluminator 6y agoI can see a minority of features that would actually need it like the classsic chat room or some live feed of stocks. Sure if thats the case then Hotwire gives a nice solution. But throwing in streams just for validations? Come on. This is done just fine with Ajax/Rails Ujs etc. We're solving non problems here I think.