But RoR does support having node integrated and it was the default for a long time. tailwindcss-rails could've just used Node.
Instead your application is now packing a 100M binary just for your CSS framework. Even when you are already using Node.
I see no benefit, imagine if every component of your application shipped its own runtime. Imagine if erb in RoR packaged its own version of ruby. That would be crazy right?
The application is not packing the binary - it is the gem that you use to build CSS, and I _think_ it's only active during development, but don't quote me on that. In production there is a generated built asset which contains all the Tailwind-generated CSS classes you are using across your templates.
Instead your application is now packing a 100M binary just for your CSS framework. Even when you are already using Node.
I see no benefit, imagine if every component of your application shipped its own runtime. Imagine if erb in RoR packaged its own version of ruby. That would be crazy right?