3 ms·

It's a bit worrying that the steering committee for such a widely used technology, one which billion-dollar companies have built stacks around, could fracture b

by strken 9y ago

It's a bit worrying that the steering committee for such a widely used technology, one which billion-dollar companies have built stacks around, could fracture because of a twitter fight. Without knowing the facts, the fact that we even know this happened and that it briefly ended up on the front page of HN is concerning.

mcphage 9y ago
> It's a bit worrying that the steering committee for such a widely used technology, one which billion-dollar companies have built stacks around, could fracture because of a twitter fight. Any group of people leading an organization can fracture because of a fight; it's nothing new, and the fact that it happened on twitter is immaterial. > Without knowing the facts, the fact that we even know this happened and that it briefly ended up on the front page of HN is concerning. Agreed. Given the list of problems was removed from the GH issue, I have no idea what this is about, and no way of forming an opinion on any of it. I at least will flag it.
- rhapsodic 9y ago
  > Agreed. Given the list of problems was removed from the GH issue, I have no idea what this is about, and no way of forming an opinion on any of it. I at least will flag it. There is plenty of information in the comments to this post to get an idea of what it is about. I respectfully suggest that you get some insight before suppressing the post through flagging.
- slang800 9y ago
  Well, it ended up getting archived before the list was removed. Whether that's right or wrong, the info is out there: https://web.archive.org/web/20170821212745/https://github.com/nodejs/TSC/issues/310 https://web.archive.org/web/20170821212745/https://github.co...