2 ms·

I hope to see the Hotwire dependency dropped one day. I love Rails and Hotwire, but I wish the latter were also a community tool. When TypeScript support was di

I hope to see the Hotwire dependency dropped one day. I love Rails and Hotwire, but I wish the latter were also a community tool. When TypeScript support was discontinued, DHH commented: > This project has been founded, funded, and maintained predominantly by the resources and investment of 37signals. We will set the direction as we see fit... With TensorFlow recently discontinuing support for Windows, it's very concerning to me that one day one person or organization decides that "we will set the direction". They don't even try to use nicer language. Don't get me wrong, I respect the work and effort. But 37signals are no saints. There was a scandal, and employee exodus not so long ago. Hotwire is so deeply integrated into Rails, so Rails is even more 37signals' tool than ever before. Before we had webpack, and JavaScript libraries that sometimes were not easy to use. Now things are easier, but instead of JS libraries we've gotten 37signals dependency, which is VERY concerning.

gherkinnn 3y ago
The Turbo incident was none. It just wasn’t. I would not have dropped TS but the change barely matters. I have only ever seen it used in a script tag and the code reads well enough in vanilla. The actual incident was a horde of morons piling on top of that repo in the days that followed.
- RomanPushkin 3y ago
  None? They ignored multiple instances of community feedback. Broke countless current PRs and upstream libraries. And moreover, going forward I expect another surprise from them. Another surprise that I ain't gonna like. Rails backend is in a good shape, but I don't like being dependent on a dictator's decisions on the frontend. I don't understand why Rails team don't understand that. But from the other side I'm thankful to DHH, because now I use more Elixir, and Crystal. Those are awesome tools, and 37signals-free world feels so much better. It's not toxic.
  - mokkol 3y ago
    For me it made a lot of sense. Ruby developers don't like types as much as in other languages. By far the majority of Javascript made by Ruby/Rails developers is vanilla. Turbo is a library used mostly by Ruby/Rails developers. As a Rails developer myself, it was much harder to contribute to Turbo. I had to learn Typescript before doing so, which makes the bridge too high. 90+% of the people who were complaining didn't even know Turbo existed. Could it be communicated a bit better? Yeah sure, I give you that. Is it bad moving forward? Maybe initially as there were broken PRs but I think eventually it is in a much better place. In my opinion.

gherkinnn 3y ago

The Turbo incident was none. It just wasn’t. I would not have dropped TS but the change barely matters. I have only ever seen it used in a script tag and the code reads well enough in vanilla. The actual incident was a horde of morons piling on top of that repo in the days that followed.

RomanPushkin 3y ago
None? They ignored multiple instances of community feedback. Broke countless current PRs and upstream libraries. And moreover, going forward I expect another surprise from them. Another surprise that I ain't gonna like. Rails backend is in a good shape, but I don't like being dependent on a dictator's decisions on the frontend. I don't understand why Rails team don't understand that. But from the other side I'm thankful to DHH, because now I use more Elixir, and Crystal. Those are awesome tools, and 37signals-free world feels so much better. It's not toxic.
- mokkol 3y ago
  For me it made a lot of sense. Ruby developers don't like types as much as in other languages. By far the majority of Javascript made by Ruby/Rails developers is vanilla. Turbo is a library used mostly by Ruby/Rails developers. As a Rails developer myself, it was much harder to contribute to Turbo. I had to learn Typescript before doing so, which makes the bridge too high. 90+% of the people who were complaining didn't even know Turbo existed. Could it be communicated a bit better? Yeah sure, I give you that. Is it bad moving forward? Maybe initially as there were broken PRs but I think eventually it is in a much better place. In my opinion.