4 ms·

“If you liked “How to build a blog in 15 minutes with Rails,” check out the sequel, ‘How to destroy Rails in 15 minutes with a blog.’”(From https://twitter.com/

“If you liked “How to build a blog in 15 minutes with Rails,” check out the sequel, ‘How to destroy Rails in 15 minutes with a blog.’”(From https://twitter.com/sandofsky/status/1388174804985868289 https://twitter.com/sandofsky/status/1388174804985868289 )

Trasmatta 5y ago
It's a funny Tweet, but Rails is much, much bigger than Basecamp now. There's enough money invested in the Rails ecosystem at enough large and medium sized companies that Basecamp could go away entirely and Rails would continue to persist. (I realize that there's always the possibility that this post could age like milk, and everyone might be pointing at laughing at me in 5 years. But that's also pretty much true for any piece of technology, and not unique to Rails' current situation.)
- bdcravens 5y ago
  I've seen more than a few tweets in recent days from those who feel distraught as Rails developers. Perhaps it's silly, but the Rails ecosystem and culture plays a big role in its success.
  - Trasmatta 5y ago
    With core Rails team members apparently resigning as part of this we may very well see a leadership shake up in the Rails community. Despite people claiming "Rails is dead!" for the past 10 years, it's continued to be huge at pretty much all levels of development (introductory, hobbyist, contract work, startups, small, mid, and large size companies). I don't really see this changing that significantly. If we start to see an exodus off of Rails in the next few years from the big players like GitHub, then I'll start to get worried.
- bonaldi 5y ago
  Agreed, but culture and mindshare matter. You can be big like node or big like Perl. Losing cachet can be like going out of business: slow then sudden.
- aaronbrethorst 5y ago
  At least two developers resigned from both Basecamp and the Rails core team today. https://twitter.com/georgeclaghorn/status/1388131009531719680 https://twitter.com/georgeclaghorn/status/138813100953171968... https://twitter.com/sstephenson/status/1388146129284603906 https://twitter.com/sstephenson/status/1388146129284603906 I agree with you, and I wouldn't be that surprised to see this manifest as a Rails fork.
  - Trasmatta 5y ago
    I suppose a fork might happen if a large portion of the community decides to reject DHH. I think that'd be a mistake, but it could result in a schism in the community. I think what might happen is one of the other big players in the Rails ecosystem, like GitHub, might begin taking a larger role in the development and leadership of Rails.
- drailsusers 5y ago
  Maybe Rails will survive but what about Turbo and the rest of the Hotwire framework? Turbolinks was pretty much abandoned and Turbo is short of a proper release with the lead developer leaving.
  - Trasmatta 5y ago
    StimulusReflex might take over that space if Hotwire doesn't get new maintainers.
  - easton 5y ago
    Wasn't dhh working on it too? maybe there's remaining devs that can get it working. but that will really stink, considering that it was the best thing I've seen (outside of htmx) that can kill the front-end monster.
    - Trasmatta 5y ago
      Looking at the contribution graphs, it doesn't look like DHH has contributed much to the Hotwire stack.
    - deleted 5y ago
      [deleted]
- rodgerd 5y ago
  The Rails trademark is entirely and exclusively owned by DHH, so whatever you may think, it is in fact, entirely his toy.

Trasmatta 5y ago

It's a funny Tweet, but Rails is much, much bigger than Basecamp now. There's enough money invested in the Rails ecosystem at enough large and medium sized companies that Basecamp could go away entirely and Rails would continue to persist. (I realize that there's always the possibility that this post could age like milk, and everyone might be pointing at laughing at me in 5 years. But that's also pretty much true for any piece of technology, and not unique to Rails' current situation.)

bdcravens 5y ago
I've seen more than a few tweets in recent days from those who feel distraught as Rails developers. Perhaps it's silly, but the Rails ecosystem and culture plays a big role in its success.
- Trasmatta 5y ago
  With core Rails team members apparently resigning as part of this we may very well see a leadership shake up in the Rails community. Despite people claiming "Rails is dead!" for the past 10 years, it's continued to be huge at pretty much all levels of development (introductory, hobbyist, contract work, startups, small, mid, and large size companies). I don't really see this changing that significantly. If we start to see an exodus off of Rails in the next few years from the big players like GitHub, then I'll start to get worried.
bonaldi 5y ago
Agreed, but culture and mindshare matter. You can be big like node or big like Perl. Losing cachet can be like going out of business: slow then sudden.
aaronbrethorst 5y ago
At least two developers resigned from both Basecamp and the Rails core team today. https://twitter.com/georgeclaghorn/status/1388131009531719680 https://twitter.com/georgeclaghorn/status/138813100953171968... https://twitter.com/sstephenson/status/1388146129284603906 https://twitter.com/sstephenson/status/1388146129284603906 I agree with you, and I wouldn't be that surprised to see this manifest as a Rails fork.
- Trasmatta 5y ago
  I suppose a fork might happen if a large portion of the community decides to reject DHH. I think that'd be a mistake, but it could result in a schism in the community. I think what might happen is one of the other big players in the Rails ecosystem, like GitHub, might begin taking a larger role in the development and leadership of Rails.
drailsusers 5y ago
Maybe Rails will survive but what about Turbo and the rest of the Hotwire framework? Turbolinks was pretty much abandoned and Turbo is short of a proper release with the lead developer leaving.
- Trasmatta 5y ago
  StimulusReflex might take over that space if Hotwire doesn't get new maintainers.
- easton 5y ago
  Wasn't dhh working on it too? maybe there's remaining devs that can get it working. but that will really stink, considering that it was the best thing I've seen (outside of htmx) that can kill the front-end monster.
  - Trasmatta 5y ago
    Looking at the contribution graphs, it doesn't look like DHH has contributed much to the Hotwire stack.
  - deleted 5y ago
    [deleted]
rodgerd 5y ago
The Rails trademark is entirely and exclusively owned by DHH, so whatever you may think, it is in fact, entirely his toy.