Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Day AppGet Died

keivan.io

Post reply on HN
Print view View original

441–450 of 566 posts

Re: The Day AppGet Died

#441

Post by npongratz »

JoeAltmaier wrote: post #404
sillysaurusx wrote: post #380

Earlier quoted context omitted.

I flew to Seattle on December 5th to have a full day of interviews/meetings at Microsoft HQ. I met with four different people; three of the meetings were more like your typical interviews; the meeting with Andrew was more about what we should do once this is all over and how we would migrate AppGet’s process and infrastructure to be able to handle Microsoft’s scale. We talked about some of our options, but in general…

Yes sometimes it means that. But if the company is desirable, knows its desirable and knows the interview means a lot to the interviewee, then its the height of arrogance and cruelty to 'ghost' them. Screw that 'just business', its not just business, its shitty behavior out of a company that has the resources to do the right thing.

> Screw that 'just business', its not just business, its shitty behavior out of a company that has the resources to do the right thing.

To put an even finer point on it, a business is made of people. Individuals. The individuals involved behaved exceptionally poorly (to be charitable) toward another human being. How shameful of these individuals to act that way, and then (presumably) hide behind the collectivist shield of "the business".

Re: The Day AppGet Died

#442

Post by Conan_Kudo »

throw_m239339 wrote: post #399
Conan_Kudo wrote: post #189

Earlier quoted context omitted.

> GitHub Pagure[1] is a good option here. > TypeScript You could just use JavaScript? > npm There aren't any at this time, as far as I know. > Visual Studio Code (besides Atom) Sublime Text[2] is a favorite of many, though I use Emacs[3]. [1]: https://pagure.io/pagure [2]: https://www.sublimetext.com/ [3]: https://www.gnu.org/software/emacs/

> npm / There aren't any at this time, as far as I know. yarn?

Hmm, I assumed we were talking about the server-side aspect of npm, which there is no alternative for. Yarn uses it too.

Client side has a couple of options, including Yarn.

Re: The Day AppGet Died

#443

Post by [deleted] »

hoytschermerhrn wrote: post #428
macspoofing wrote: post #382

Earlier quoted context omitted.

>Ah yes. The new Microsoft, same as the old Microsoft. I wouldn't say that. It's a big company thing.

Saying that it’s just “a big company thing” is giving Microsoft a pass here. Look at their recent PR: wanting to embrace the developer community [1], their love of open source [2], etc. While AppGet may be an isolated story, I’m inclined to believe that MSFT is simply acting they way they’ve always have — by embracing, by extending, and by extinguishing. 1. https://arstechnica.com/information-technology/2017/05/micro…

[deleted]

Re: The Day AppGet Died

#444

Post by Wowfunhappy »

cerberusss wrote: post #205
Wowfunhappy wrote: post #111

Earlier quoted context omitted.

From the article, it sounds like he did pursue. After some interviews Microsoft dropped contact.

Which I don't find all that weird. Quoting OP here; "after visiting the campus, I wasn’t too sure I wanted to work for such a big company, also moving from Canada to the U.S. wasn’t something I was too excited about". In the past, I've been in talks with an employer about a job, and my enthousiasm was only so-so, and that tended to put a brake on the proceedings.

I don't find it particularly weird either, but it makes for a much more nuanced narrative compared to "Microsoft wanted to hire you for your package manager and you rejected them."

I just think Microsoft should have found a way to credit the guy. Even just a footnote in their WinGet announcement blog post would have been better.

Re: The Day AppGet Died

#445

Post by teekert »

knolax wrote: post #373
teekert wrote: post #344

Earlier quoted context omitted.

Get used to it, this is going to be the bulk of the "Linux" users from now on. Edit: Imo not a bad thing, it's just how it is. A lot of people will learn (of) Linux through WSL. Linux as a runtime.

Considering the fact that there are five times as many Android devices as Windows devices, and the greater ease of use of Termux compared to WSL. I find that highly unlikely. Anecdotally every newbie programmer I've seen try to use WSL has just ended up installing Linux in frustration.

Termux is a terminal emulator, WSL is a subsystem. Did you try [0]? And WSL2?

It's pretty compelling, I predict they will pull in a lot of Apple (who use it for the terminal) devs and make a lot of Windows first devs very happy. And there are a lot.

Btw, am I downvoted because my original comment in not constructive or do people not agree with me?

[0] https://www.microsoft.com/en-us/p/windows-terminal/9n0dx20hk...

Re: The Day AppGet Died

#446

Post by SifJar »

knolax wrote: post #373
teekert wrote: post #344

Earlier quoted context omitted.

Get used to it, this is going to be the bulk of the "Linux" users from now on. Edit: Imo not a bad thing, it's just how it is. A lot of people will learn (of) Linux through WSL. Linux as a runtime.

Considering the fact that there are five times as many Android devices as Windows devices, and the greater ease of use of Termux compared to WSL. I find that highly unlikely. Anecdotally every newbie programmer I've seen try to use WSL has just ended up installing Linux in frustration.

> greater ease of use of Termux compared to WSL

pretty subjective, I'm guessing most people find terminal-based stuff easier/nicer on a computer with an actual keyboard, rather than a (relatively) small phone screen with a touchscreen keyboard.

I believe Termux is also pretty majorly restricted by Android 10 (can only run binary code included within the application package, so no downloading additional linux packages or compiling things locally, I believe)

Re: The Day AppGet Died

#447

Post by perfectstorm »

allenu wrote: post #108

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 pe…

This is probably what happened. As a hiring manager i want to tell the candidates whenever we reject them but sometimes recruiting drops the ball and never reaches out with rejection email or call (our team usually calls them).

This happened to one of my referrals so i know this firsthand.

Re: The Day AppGet Died

#448

Post by bcrosby95 »

hoytschermerhrn wrote: post #428
macspoofing wrote: post #382

Earlier quoted context omitted.

>Ah yes. The new Microsoft, same as the old Microsoft. I wouldn't say that. It's a big company thing.

Saying that it’s just “a big company thing” is giving Microsoft a pass here. Look at their recent PR: wanting to embrace the developer community [1], their love of open source [2], etc. While AppGet may be an isolated story, I’m inclined to believe that MSFT is simply acting they way they’ve always have — by embracing, by extending, and by extinguishing. 1. https://arstechnica.com/information-technology/2017/05/micro…

What happened to AppGet is not what embrace, extend, extinguish means. This strategy refers to writing software compatible with existing dominant software surrounding some shared interop (e.g. a file format they can both read, web standards they both implement, a networking protocol so they can communicate with eachother, etc), gaining market dominance, then making your once compatible software incompatible. Absolutely none of this happened with AppGet.

Re: The Day AppGet Died

#449

Post by mumblemumble »

philliphaydon wrote: post #412
tiagod wrote: post #385

Earlier quoted context omitted.

How does AppGet compete with apt-get?

I thought AppGet was a pun on apt-get and thought the name was clever. I thought it was better named than Chocolatey or Scoop. Edit: plan > pun. (no idea why I wrote plan, i think I wanted to write play)

Chocolatey is a pun on NuGet, which is presumably inspired by apt-get.

Re: The Day AppGet Died

#450

Post by orthoxerox »

mumblemumble wrote: post #431
wpietri wrote: post #346

Earlier quoted context omitted.

Ah yes. The new Microsoft, same as the old Microsoft. I am really sorry this happened to you. On the scale of Microsoft, or even on the scale of what they're putting into this effort, it would have cost approximately nothing to give you an "acquisition" you would have been happy with. If the job didn't work out, they could have given you a fat consulting contract for a year or two. Or they just could have written you…

Reducing this down to a Microsoft thing is a bit hasty. Apple has done it. IBM has done it. And, when I was working for a less well-known company, I once burned a whole lot of social capital trying to prevent it from happening. At least in that instance, there was never anything overtly malicious happening. It was just your garden variety "banality of evil" situation. The existing corporate decision-making structures…

It's not even American. I can easily imagine it happening in any large company.

This "Andrew" is isolated from everything by multiple levels of bureaucracy and regulations. Even if he wanted to make right, he would've just burned his accumulated clout it vain. Hire as a contractor? No matching position. Write a check? No such budget line item. Give a shout-out? Leave marketing to the marketing dept.

Post reply on HN