Do you mean what's the benefit to keeping your Rails code to server-side only, rather than using it to create views/erb templates? If that's what you mean, then I think that's a great approach because:
You can separate your concerns into different directories and even different git repos if you want
You can write unit tests for each set of concerns that are easier to find and follow
If you decide you want to change the front end client that consumes your Ruby API in future, you can easily do so since they're loosely coupled
If you find yourself needing help from the open source community with your front end, the numbers of people skilled in Vue/React out there are very high
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Do you mean what's the benefit to keeping your Rails code to server-side only, rather than using it to create views/erb templates? If that's what you mean, then I think that's a great approach because: