zlacker

>>lostms+(OP)
This was definitely not a great experience, but my hunch is what happened is some higher ups decided no, they don't need to hire you, the original team tells recruiting to notify you, recruiting drops the ball somehow, team goes on with their lives believing that you were told they were no longer interested, and everyone (except you, since you never got notified) believed the whole thing was resolved.

The original people (not recruiters) who reached out to you should've connected after the decision was made. They probably figured the recruiters would do their dirty work, so no need to engage.

Full disclosure: I worked at Microsoft for over a decade, so I know how slow and lumbering it can be. I bet some emails were missed and people didn't follow up because "they had a lot of other things they were tracking".

>>allenu+2o
> some higher ups decided no, they don't need to hire you

Total misjudgment on their part. Thanks to this one HN post they already lost in terms of developer good will way more than his potential salary would be.

Every time anyone who uses WinGet, who read this, will think 'oh, yeah, that's the tool that Microsoft build their version of behind original author's back, while stringing him and ghosting for few months".

>>scotty+Qt
Yes. Microsoft really dropped the ball on this one.

So much of what Microsoft has been doing — GitHub, .NET Core, NPM, Visual Studio Code, Windows Subsystem for Linux, etc. — has been to build goodwill with “developers! developers! developers!” Taking the resources to do an acquihire (or hire + bonus) right is small relative to the PR hit.

>>divbze+tI
> Windows Subsystem for Linux, etc. — has been to build goodwill with “developers!

WSL has been built for webdevs not to flock to *NIX from Windows, nothing else.

Even naming it "Windows Subsystem for Linux" is an insult, since it sounds as if it was something for Linux, when in reality it's a "Linux Subsystem for Windows" and doesn't benefit Linux itself in any way.

>>AsyncA+0e1
> Even naming it "Windows Subsystem for Linux" is an insult…

The developers of WSL have said* that was mostly a legal concern. Calling it “Linux Subsystem for Windows” (listing “Linux” first) has wider implications for copyright/licensing:

> Just who is allowed to call a product or service Linux, anyway?

> Linus Torvalds has an answer for that: Nobody. Not without his say-so.

> The term "Linux" is a trademark and Torvalds owns it. His assignee, an organization called the Linux Mark Institute (LMI), is empowered to collect licensing fees from companies and individuals who want to use the word commercially.

> - https://www.infoworld.com/article/2671387/linus-gets-tough-o...

*I think it was during a Microsoft Build 2020 Q&A with the WSL team, but I can't find the video on YouTube.

>>modern+Ye1
Are you telling me MS could not be bothered to even ask Linus? And if there's a fee to pay it? They're a multi-billion dollar corp telling us they love Linux now.

Alternatively, calling it something like Nix subsystem for Windows or maybe just LSW would also do the trick, this seems like a lame excuse.

>>AsyncA+Bf1
It was more that he could have said "No" to them, where as in this case he cannot really say "no" (or "yes" for that matter).