3 ms·
> Whatever you do with Rails, stay far away from their template markup languages (haml). Write the front-end in Vue.js, consuming APIs, don't do any server-side
by tdeck 6y ago
> Whatever you do with Rails, stay far away from their template markup languages (haml). Write the front-end in Vue.js, consuming APIs, don't do any server-side rendering of anything.
This is far from a consensus opinion. Depending on your application you can actually get great results with Turbolinks, meaning you write very little client side code. It's worth reading up on that option as well.
- wallflower 6y agoOk, we can agree to disagree. Given the OP’s stated personal choice of using Vue.js, I assume that they want to build a SPA. In my understanding, using Turbolinks makes use of most every JavaScript client-side framework, including Vue.js, more difficult as the JavaScript components have to be adapted to work with Turbolink caching.
- tdeck 6y agoIndeed, I wouldn't recommend using them together either if OP goes with Vue.
- wallflower 6y agoThanks for the clarification, we will agree to agree :) I still have not-so-fond memories of using Rails 4.x to render HAML partials to "support" basic JavaScript dynamic interactivity.