rux-rails VS view_component

We’ve been using ViewComponent in a number of applications at The Gnar and we really like it. It seems we’re not alone given the splash it’s making in the community. There are a good number of projects that are layering functionality on top of ViewComponent which is a promising sign. Enter rux. This library (and its rails companion) was inspired by JSX will allow you to write HTML tags in your ruby code. This isn’t something we’ve used yet but we’re keeping our eyes on it. Grab your popcorn for the inevitable debates about the separation of concerns. 🍿

When searching for examples of table components built with the ViewComponent gem, I was surprised to find none. After some inquiries, I came across examples that worked like this:

View components offer two primary ways to interact with the component: passing arguments to the initializer and using slots:

For example, splitting out views into partials? Or the new ViewComponent feature that's becoming quite popular - https://viewcomponent.org/

I used to do "pure ruby" approach to that -- but basically wound up realizing I was re-inventing github's view_component. Their design goals were similar enough to what I was trying to do, that it made more sense just to use that, rather than try to re-invent it myself.

ViewComponent

The linked one is my Rails implementation, written for ViewComponent. The official version uses Nunjucks.