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
Realistically, though, a year from now nobody will care. I mean, I started in this industry in the "MS is outright evil" era. How many people did they screw over? If I remember correctly, there was even a guy who was owed a pile of stock/stock options and when he got cancer they suddenly went missing (no need to pay the dead guy!). Day by day, year by year, these misdeeds are seen as irrelevant. MS is a different company these days (almost literally). Should we hold them accountable for their past sins forever? (I have a friend who still refuses to buy products from Nestle given their ancient "poison in baby formula is OK as long as it saves us money" stance. That's older than I am!)

In reality, these kinds of antics just don't hurt companies significantly -- even ridiculously horrible things that are arguably crimes against humanity (have I invoked Godwin's law?) In comparison to some of the incredibly awful things companies do (and get away with), this is minor to the point of not even being a footnote in the annals of evil (note to self: don't google that term to check the spelling...).

However, there will be a few of us who will be reminded of why we don't do business with MS (and hence will have no need of WinGet). It won't make any difference, but it will be there.

>>mikekc+qG
About Nestlé's poison baby formula: I though their baby formula was safe, but the problem is that they gave it away (maybe still do?) for free to new mothers in developing countries and when the mothers stopped lactating (because their own milk wasn't being drunk) they made the price hopelessly unaffordable so now the babies couldn't drink from either source, or at least needed to over-dilute the formula.

Totally reasonable to still boycott them, makes more sense than getting annoyed at Microsoft in a situation like this (which is also deserved but more minor in the grand scheme of things).

>>quietb+rT
That's more recent. A long time ago (and I'm working from memory, so best to fact check anything I say, because my memory is terrible) it was common to use a particular rat poison in dry milk (and I forget exactly what it was). There were certain standards as to how much rat poison you were allowed to have. It was well known that this would kill a small percentage of babies, but it was thought to be a reasonable tradeoff at the time. To be fair, it wasn't just Nestle. In Japan, the dairy giant Morinaga had the exact same problem. I believe there were law suits that dragged on for literal generations and eventually things changed.