Basically the author reduced himself with Rails happily to a subset of the options, yet does not want do it in the JS world. The question is why? In my experien

Basically the author reduced himself with Rails happily to a subset of the options, yet does not want do it in the JS world. The question is why? In my experience it's fear. Fear of somebody coming along and criticizing him for using X instead of Y, for not using the shiny new Z, fear of basically feeling inadequate. So get over it. The task of a developer is to make something useful. The users don't care about technology unless it's something that improves their life. They don't care about your SPA or not, and they especially don't care about the package manager your project uses. If Ruby helps you do that, go for it, but otherwise just let go snd do things. Somebody will always nitpick.