3 ms·
I understand there's already some ruby feature to avoid full page refresh? I'm a js Dev currently working with a ruby backend. Honestly for what we're doing we
by lecarore 7y ago
I understand there's already some ruby feature to avoid full page refresh? I'm a js Dev currently working with a ruby backend. Honestly for what we're doing we could have just made a plain old html page and that would have been best, with some partial reload sprinkled here and there.
I'm not sure if there's a market for this, but it's nice to see that you try new things.
Right now I feel the pain of having a large react codebase while most of the team prefers working in ruby.
The risk with such project imo is to have insufficient abstractions and to end up debugging js code in the browser anyway.
How about code splitting, hot reload, automatic assets compiling, etc .. that we've come to expect when developing front ends ?
- pdoub 7y agoSince we're not compiling Ruby into JS (I think Opal/Hyperstack does this) debugging can be done using the Vue Dev Tools in the browser, so you're not worse off there. Most basic use cases (show/hide/rerender on event, deferred loading, onclick...) are part of the Matestack core and have good test coverage. For special use cases there's a guide on creating custom dynamic components, but yeah we could add some more info on debugging I guess. Not sure if my comment helped?