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

71–80 of 566 posts

Re: The Day AppGet Died

#71

Post by thayne »

benatkin wrote: post #24

I don't want to support this company. What are good alternatives to GitHub, TypeScript, npm, and Visual Studio Code (besides Atom)?

> github

Gitlab, many other lesser known alternatives (such as the aforementioned sourcehut, although that has a different paradigm than github)

> Typescript

Facebook's flow is probably the closest. There's also dart, and many, many other languages that can compile to JavaScript.

> npm

Yarn is the obvious one (although it still uses the npm repo). Or you could leave node altogether and use deno. There are probably other alternatives.

> Visual Studio Code

(Neo)vim and emacs are both good options, although they have a steep learning curve. There's sublime text if you don't mind something proprietary. Probably others I'm less familiar with.

Re: The Day AppGet Died

#72

Post by lostmsu »

fraggle222 wrote: post #16

Not sure how MSFT usually handles it, but when I was acqui-hired (by a different large tech company, not quite on MSFT scale, but no trifle) I dealt almost exclusively with a person from Business Development. Maybe it is a bad sign that they had you discussing with people in their engineering group directly. Sounds like they were gathering data from you with no real plan to acquire. Then again every company may do it…

Out of curiosity, how long the process took until the deal was signed?

Re: The Day AppGet Died

#73

Post by leonidasv »

FridgeSeal wrote: post #30
benatkin wrote: post #24

I don't want to support this company. What are good alternatives to GitHub, TypeScript, npm, and Visual Studio Code (besides Atom)?

>GitHub Github I guess? > TypeScript, npm, I don't know if you'll be able to avoid NPM, but _maybe_ you could try ReasonML if you're doing frontend stuff with TS? Don't really know tbh > Visual Studio Code (besides Atom)? Sublime Text 3 with plugins for general stuff, one of the JetBrains IDE's for more language specific work if so desired.

ReasonML is a pretty decent choice. Small learning curve, JS interop, fast compilation, functional goodies.

Plus a thing called "Structural typing" that gives you the flexibility of dynamic typing without losing the guarantees from static typing.

Re: The Day AppGet Died

#74

Post by [deleted] »

person_of_color wrote: post #60
apetresc wrote: post #22

I have a sneaking suspicion that part of the reason for the sudden radio-silence after his on-campus interview is that someone up the chain realized he is also the creator of Sonarr and just nobody wanted to take ownership of that potential liability.

This. Choose your side projects wisely.

[deleted]

Re: The Day AppGet Died

#75

Post by FridgeSeal »

leonidasv wrote: post #73
FridgeSeal wrote: post #30

Earlier quoted context omitted.

>GitHub Github I guess? > TypeScript, npm, I don't know if you'll be able to avoid NPM, but _maybe_ you could try ReasonML if you're doing frontend stuff with TS? Don't really know tbh > Visual Studio Code (besides Atom)? Sublime Text 3 with plugins for general stuff, one of the JetBrains IDE's for more language specific work if so desired.

ReasonML is a pretty decent choice. Small learning curve, JS interop, fast compilation, functional goodies. Plus a thing called "Structural typing" that gives you the flexibility of dynamic typing without losing the guarantees from static typing.

Plus, if they are doing front-end stuff, it's my understanding that ReasonML will also output native code, which should theoretically go a long way to making a OS-native app significantly easier right?

Re: The Day AppGet Died

#76

Post by kayone »

person_of_color wrote: post #60
apetresc wrote: post #22

I have a sneaking suspicion that part of the reason for the sudden radio-silence after his on-campus interview is that someone up the chain realized he is also the creator of Sonarr and just nobody wanted to take ownership of that potential liability.

This. Choose your side projects wisely.

I really doubt it was it. Sonarr was one of the topics we talked about during the first meeting at Microsoft Vancouver.

Even if that was the case, I have no regrets.

Re: The Day AppGet Died

#77

Post by michaelmrose »

apetresc wrote: post #22

I have a sneaking suspicion that part of the reason for the sudden radio-silence after his on-campus interview is that someone up the chain realized he is also the creator of Sonarr and just nobody wanted to take ownership of that potential liability.

There is no liability of a pre existing side project that they had no part in.

Re: The Day AppGet Died

#78

Post by sansnomme »

yjftsjthsd-h wrote: post #38
pavlov wrote: post #12

The story reminds me of Andy Hertzfeld’s Switcher: https://www.folklore.org/StoryView.py?project=Macintosh&stor... The difference is that, in 1984, Bill Gates immediately offered $40k and Steve Jobs offered $100k for plugging a hole in their operating system. In 2020, Microsoft just strings you along on vague promises while they simultaneously rip you off.

I love how those stories of the early years are so different from what I think of looking at companies today - > Jeff picked me up at the airport, and we drove to Microsoft's main building where we were joined by Neil Konzen, a talented 23 year old who was Microsoft's main systems programmer on the Macintosh. I knew Neil from his days as an early Apple II hobbyist, when we collaborated on adding features to an assemb…

Windows NT is designed out of the box for extending and embracing Unix. The whole Linux Subsystem thing isn't something new that required deep reworking of the kernel.

Re: The Day AppGet Died

#79

Post by leonidasv »

lostmsu wrote: post #45
colejohnson66 wrote: post #37

Earlier quoted context omitted.

What’s wrong with AGPL?

AFAIK AGPL permits linking without disclosing linked code like LGPL does. Meaning they can still distribute it as their own, train models and serve them with a simpler framework. Just can't build services powered directly by it.

AGPL is as strict as GPL. It's just that GPL allows you to modify the source, serve them as a web application and not have to disclose the code.

AGPL addresses that by putting code distributed as a web application in the same category as compiled code.

Re: The Day AppGet Died

#80

Post by kayone »

Author here, Because it's sure to come up here is a comment I wrote on Reddit that clarifies somethings, I haven't updated the original article since I'm not sure what the etiquette for updating a highly shared article is.

------

Code being copied isn't an issue. I knew full well what it meant to release something opensource and I don't regret it one bit. What was copied with no credit is the foundation of the project. How it actually works. If I were the patenting type, this would be the thing you would patent. ps. I don't regret not patenting anything. And I don't mean the general concept of package/app managers, they have been done a hundred times. If you look at similar projects across OSes, Homebrew, Chocolaty, Scoop, ninite etc; you'll see they all do it in their own way. However, WinGet works pretty much identical to the way AppGet works. Do you want to know how Microsoft WinGet works? go read the article (https://keivan.io/appget-what-chocolatey-wasnt/) I wrote 2 years ago about how AppGet works.

I'm not even upset they copied me. To me, that's a validation of how sound my idea was. What upsets me is how no credit was given.

Post reply on HN