Hey if you know anyone who works on WSL, this thread is really scary for those of us who want to depend on it.https://github.com/Microsoft/WSL/issues/2448#issuecomment-341932033 …
1: So I want to say: I appreciate the attention to detail, but your comment missed something important: this bug is a regression
-
-
2: that affects a dominant use case for WSL (Node). Security is one reason to high-tail a fix. So are regressions like this.
-
3: The reason I was concerned about this thread is that treating a regression of this magnitude as not-urgent doesn't match how I was
-
4: thinking of this project. If wifi stopped working for common chipsets, the fix would be treated as urgent.
-
5: I work on significant projects so I understand the very difficult tradeoffs here, and why this is so hard. But I want to know whether
-
6/6: significant regressions in WSL will be treated as significant regressions or minor problems with a hobby feature.
-
Significant regressions have and do get treated with some urgency. We have fast tracked fixes for major issues before & will again
-
But, while enormously annoying though a regression like this is to the affected audience, it's not an overwhelming outage to the majority
-
And FWIW, WSL is far from a hobby feature - it's now an essential tool to MANY devs inside and outside Microsoft. We take this v. seriously
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
