Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Technology choice (Stimulus) #85

Closed
yhoiseth opened this issue Apr 20, 2021 · 3 comments
Closed

Technology choice (Stimulus) #85

yhoiseth opened this issue Apr 20, 2021 · 3 comments

Comments

@yhoiseth
Copy link

Thanks a lot for this initiative. It is sorely needed.

I’m curious about the choice of Stimulus over alternatives. For example, it’s not immediately obvious to me that Stimulus is a better fit than Unpoly or htmx.

I think documenting the reasoning behind the choice would make it more motivating for me to use Symfony UX by removing some doubt. It would also be useful when trying to choose between different alternatives.

@mindtechmedia
Copy link

I assume the thinking was in the line of Stimulus being already field tested in the Rails community and having Basecamp as a big company behind it using it on a big production site while unpoly and htmx are basically dependent on one person and not used in bigger projects.

Now with the unexpected implosion of Basecamp and the people providing 99% of the source code leaving with no new developers taking over in sight it might be a good time to look into alternatives @tgalopin @weaverryan ?

@nicolas-grekas
Copy link
Member

To be considered maybe also: https://github.github.io/catalyst/

@weaverryan
Copy link
Member

I assume the thinking was in the line of Stimulus being already field tested in the Rails community and having Basecamp as a big company behind it using it on a big production site while unpoly and htmx are basically dependent on one person and not used in bigger projects.

This is definitely a big part of the thinking 👍

Now with the unexpected implosion of Basecamp and the people providing 99% of the source code leaving with no new developers taking over in sight it might be a good time to look into alternatives @tgalopin @weaverryan ?

This is definitely unfortunate :/. However, Turbo and Stimulus (both of which are years old libraries - Turbo as Turbolinks previously) are still used widely, for example in the Ruby on Rails community and also on hey.com. For the time being, both libraries are in great shape. Of course, longer-term, we will need to see what happens. For now, I'm recommending a "wait and see". Again, both libraries are solid - so if we ever did need to pivot to another technology, it is not something that would need to happen even remotely quickly. My hope is that new leadership rises up for both technologies and continues to iterate on them - they are both wonderful.

To be considered maybe also: https://github.github.io/catalyst/

This looks very promising and has a big company behind it. It's also brand new :). Again, the best path right now is to keep moving forward and keep our eye on how the ecosystem develops. The good news is that all of these technologies (Stimulus vs Catalyst or Turbo vs Swup) are fundamentally the same.

Cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants