search

komposable / komponent

An opinionated way of organizing front-end code in Ruby on Rails, based on components
http://komponent.io
MIT License
426 stars 31 forks source link

Future of Komponent #169

Open Spone opened 3 years ago

Spone commented 3 years ago

I would like to gather feedback, to figure out what the future of Komponent should look like.

We created Komponent in 2018 when we felt that there was no convincing solution to organize our front-end code into components. Now in 2021 I feel like ViewComponent is the new standard for this. It is popular, very fast, well maintained and follows Rails conventions more closely than Komponent.

As you know, it's quite some work to maintain and evolve an open source project, and we haven't been up to the task in 2020. So we're considering deprecating Komponent, but we'd like to provide a path forward.

I currently work on a dozen projects heavily using Komponent (most of them still Rails 5.2), and some of them are migrating (or considering migrating) to ViewComponent.

If you are using Komponent, can you please tell us:

Thanks in advance!

EDIT: I've started working on a draft to help you migrating to ViewComponent. Please review and contribute!

Spone commented 3 years ago

cc @andrzejsliwa @olimart @gkemmey @MittchoBaroco @stevschmid and other contributors, I would be happy to read your opinion on this!

florentferry commented 3 years ago

Hello here,

Seems a long time I don't have contribute to Komponent, mainly because I don't use it.

As you mentioned, it's difficult to maintain open source project, and even more when we don't actively use the projet in production. @Spone, and some others folks contributes to the projet, and it's nice to see people involved into it.

Rails introduced ViewComponent, and seems to be the standard, I don't use it either. Some projects in Ouvrages use Komponent, and should use it in future too, or not, depending or what ViewComponent has to offer. Komponent was born because there had no alternatives to components-view system in Rails ecosystem. Now with ViewComponent a Rails Way is rising.

Today, I make front-end only with javascript tools like React, and use Rails only for back-end. But Hotwire is a Rails Way solution to compete with javascript frameworks. Maybe tomorrow, we will some projects with Hotwire, and ViewComponent.

So, for me, working on tools to ease the migration seems a good solution for people which want to use the Rails View without losing time and money.