4 ms·
In their architecture diagram they're comparing their stack to one with distinct native UIs for each device type but they don't really explain how they're repli
by jayd16 7y ago
In their architecture diagram they're comparing their stack to one with distinct native UIs for each device type but they don't really explain how they're replicating that functionality. Unless there's some trick there should still be 3 UI blocks in the Ruby side of their diagram.
I won't go so far as to say this makes things worse but it seems like you're just moving things around. You can still have distinct client code on the Ruby side. If your goal is to simply move all this work out of JavaScript and into Ruby because you like Ruby, it seems fine.
You no longer have the explicit rest API to force a separation of UI and business logic but you can just enforce that with coding practices. You lose the ability to decouple UI dev entirely though.