---
title: "Comment by Neil Douglas on \"Why Ruby on Rails Needs Components\" | Hashnode"
description: "Have you seen a Phlex though?"
url: "https://hashnode.com/posts/why-ruby-on-rails-needs-components/64c8fc9dc2a93e868eaab545/comment/64d0abd8fd5742f91b971967"
---

[Discussion](https://hashnode.com/posts/why-ruby-on-rails-needs-components/64c8fc9dc2a93e868eaab545)

Comment [Why Ruby on Rails Needs Components](https://hashnode.com/posts/why-ruby-on-rails-needs-components/64c8fc9dc2a93e868eaab545)

[Neil Douglas](https://hashnode.com/@NeilDouglas)

[Aug 7, 2023](https://hashnode.com/posts/why-ruby-on-rails-needs-components/64c8fc9dc2a93e868eaab545/comment/64d0abd8fd5742f91b971967)

Have you seen a Phlex though?

[Avi Flombaum](https://hashnode.com/@avinyc)

[Aug 7, 2023](https://hashnode.com/posts/why-ruby-on-rails-needs-components/64c8fc9dc2a93e868eaab545/comment/64d0abd8fd5742f91b971967#reply-64d0d17c6644e2f8eb7f9526)

I totally have and love it. What this is about is a pattern for how we would share components, Phlex, ViewComponent, between applications and how we should create more component libraries that do that, regardless of the underlying implementation.
