4 ms·

The collective meltdown, bullying, pile-on and emotional responses over a team's decision to drop a layer of tooling is strange. Yes, I get it, for most usecas

The collective meltdown, bullying, pile-on and emotional responses over a team's decision to drop a layer of tooling is strange. Yes, I get it, for most usecases, most people today prefer TS, but in the end, the team weighed their options and they made a decision they are happy with. Open source, as strange as it sounds, doesn't mean that the maintainers need to ask for the approval of everybody who read some tweets and join the pile on. For those who disagree with their decision and are actually affected, vote with your feet, and don't rely on anything hey or dhh related. If you don't have a choice but to keep using them and you hate this change, I feel your pain. I don't know enough about turbo to know if it's a bad decision or not, but I don't mind people going against the grain. If people like that wouldn't exist, I'd still need to work with Scrum (in the end, how dare you challenge the collective wisdom that scrum is the greatest thing since slice bread). They may succeed or fail, but at least they fail in their own terms and enjoy their work on their product with the language they like.

digging 3y ago
> The collective meltdown, bullying, pile-on and emotional responses over a team's decision to drop a layer of tooling is strange. It should seem strange - that's not what's happening. People are upset about the decision to drop a layer of tooling, yes. People are also upset about a rush job of ripping out that layer, losing information and deleting documentation. People are also upset about a total disregard of feedback and extremely quick decision merging. These are all very normal things to be upset about.
- whoknowsidont 3y ago
  >It should seem strange - that's not what's happening. I just went through the thread and I classified 93% of the comments as snarky, editorial, and abrasive to the maintainers. The others are just memes. Presumptuous is a word that comes to mind. The majority of the commenters there have never contributed anything to the project (or any other project for that matter).
  - digging 3y ago
    > I just went through the thread and I classified 93% of the comments as snarky, editorial, and abrasive to the maintainers. The others are just memes. But, they're responding to the behavior and the intentions as much as the decision itself. That's my point. It's disingenuous and pretentious to insult the lot for simply reacting to the decision to remove a tool because that's not what they're reacting to, not entirely. > The majority of the commenters there have never contributed anything to the project (or any other project for that matter). Fair, but a totally separate point.
- x0x0 3y ago
  The majority of people complaining are not contributors to the project at all, or for the one or two I saw that are, had a handful of commits. Just like in this thread -- lots of people whinging about how something they don't contribute to is built, by the team that builds it. Which is both obnoxious and arrogant. Glance at the contributors page and you'll see who has earned the right to have an opinion on how turbo is built.
  - Rapzid 3y ago
    Not all contributors contribute code. There were also code contributors complaining. Further, there were project consumers complaining as the types were part of the project API previously.
ink 3y ago
I think dropping Typescript the way they did was silly, but you are absolutely correct that they should be able to do so, even if it’s unpopular.

digging 3y ago

> The collective meltdown, bullying, pile-on and emotional responses over a team's decision to drop a layer of tooling is strange. It should seem strange - that's not what's happening. People are upset about the decision to drop a layer of tooling, yes. People are also upset about a rush job of ripping out that layer, losing information and deleting documentation. People are also upset about a total disregard of feedback and extremely quick decision merging. These are all very normal things to be upset about.

whoknowsidont 3y ago
>It should seem strange - that's not what's happening. I just went through the thread and I classified 93% of the comments as snarky, editorial, and abrasive to the maintainers. The others are just memes. Presumptuous is a word that comes to mind. The majority of the commenters there have never contributed anything to the project (or any other project for that matter).
- digging 3y ago
  > I just went through the thread and I classified 93% of the comments as snarky, editorial, and abrasive to the maintainers. The others are just memes. But, they're responding to the behavior and the intentions as much as the decision itself. That's my point. It's disingenuous and pretentious to insult the lot for simply reacting to the decision to remove a tool because that's not what they're reacting to, not entirely. > The majority of the commenters there have never contributed anything to the project (or any other project for that matter). Fair, but a totally separate point.
x0x0 3y ago
The majority of people complaining are not contributors to the project at all, or for the one or two I saw that are, had a handful of commits. Just like in this thread -- lots of people whinging about how something they don't contribute to is built, by the team that builds it. Which is both obnoxious and arrogant. Glance at the contributors page and you'll see who has earned the right to have an opinion on how turbo is built.
- Rapzid 3y ago
  Not all contributors contribute code. There were also code contributors complaining. Further, there were project consumers complaining as the types were part of the project API previously.

ink 3y ago

I think dropping Typescript the way they did was silly, but you are absolutely correct that they should be able to do so, even if it’s unpopular.