view_component

> The context here is whether or not they're still happy with it. In 2018 GitHub got acquired for 7.5 billion dollars. Rails got them to that point and they've been up and running since 2008. I'd say that's a very big success. Given GitHub's contributions to Rails master and other activity around projects like https://github.com/github/view_component, from the outside it looks like they're still very happy with it. It's hard to say if we'd ever get a real answer on what they think internally, it would be pretty unlikely that their CTO is going to publicly write an official company blog post on "I wish we didn't choose Rails".

There seem to a lot of ruby pieces falling into place for Rails 7. The Achilles Heel of Hotwire apps has previously been the low number of supported websocket connections and high memory usage when using ActionCable and Puma but I have high hopes that Falcon[1] will take care of that. That along with Github's View Components[2] and Tailwind make me really please with the way Rails is heading right now. 1. https://github.com/socketry/falcon 2. https://github.com/github/view_component

I was a Tailwind skeptic too, but pairing it with a tool for building 'componentized' user interfaces (like GitHub's ViewComponent gem for Ruby web apps[1]) makes it incredibly easy to build attractive, consistent, easy-to-change UIs. [1] https://github.com/github/view_component/ and https://viewcomponent.org

For my sideproject (https://profilehunt.net) I have been using a somewhat similar approach. I use Github ViewComponents (https://github.com/github/view_component) for componentization of Rails views. It helps with more modular views which are easier to debug (errors usually point directly to the line in view code, unlike Rails views). I use StimulusJS (https://stimulus.hotwire.dev/) for Javascript interactivity. Stimulus is great, it allows me to write more structured reusable JS controllers without global event listeners and ids. For my project I have heavily used these two to create a Trello like board which behaves like an SPA. State and routing is still on server. I just fetch HTML on clicks and render it using Stimulus. It is usually fast enough as I only fetch small components and append them to DOM, but in case it's not I use loadi

I've found it works well with [ViewComponent](https://github.com/github/view_component) if you're in to that.

My goal is to write a demo app with: - Rails - StimilusReflex - view_component (https://github.com/github/view_component) - Web components With these 4, it divides responsibilities very cleanly/pragmatically: Rails is your app framework. view_component is how you divide your view into an organized/flexible structure. StimilusReflex is the "reflexive" bridge between the 2. What happens when you need just a sprinkle of javascript to re-render a component when websockets/StimilusReflex are too slow (ie: user interacting with a color picker or something)? You could use Stimilus.js to sprinkle this interactivity... BUT you might end up with duplication between your view_components and your Stimilus.js controller. If you use webcomponents, then you can follow the open/closed rule: Your view_component can only interact with your custom webc

Made an issue based on your comment. Is this accurate? http://github.com/github/view_component/issues/495

> an entirely new way of doing all things front end. Are you referring to ViewComponent: https://github.com/github/view_component? As someone who's happily been continuing to make Rails apps for the past few years (and avoiding Angular like the plague after being burned badly with it), this seems really intriguing, but I'm waiting on the 6.1 release before I try it.

As best I understand it, ActionView::Component (now the standalone ViewComponent) only deals with encapsulating what you'd put into a partial. https://github.com/github/view_component The web socket/Stimulus Reflex/Live View approach is orthogonal.

Phoenix + Ecto has been the best web framework experience I've ever encountered. I have experience with Django, Flask, Express and Rails. I'm a huge fan of Elixir as a language and the BEAM runtime. The libraries have been pretty great too. I agree that templating could use a more forward-looking approach as a first-class concept (something like https://github.com/github/view_component).

The problem with RoR is still a Basecamp Framework. Even though it is used by Github and Shopify. Things like ActionView-Component [1] couldn't be merged because it is not used in Basecamp, even though it is used in production at Github. Auth / Devise as mentioned is another one. Active Storage problem is another one, ( which leads to Paperclip stop being maintained ) [1] https://github.com/github/view_component