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

The Day AppGet Died (2020)

keivan.io

Post reply on HN
Print view View original

31–40 of 132 posts

Re: The Day AppGet Died (2020)

#31

Post by magpi3 »

transfire wrote: post #9

What open source license did AppGet use? Seemed to me we need some carefully worded clause that help provide some compensation if something like this happens. But M$ should be ashamed of themselves for not at least offering some compensation.

Apache. And winget-cli is licensed under the MIT license. So although the licenses are incompatible, the end result would have been the same even if Microsoft had simply forked winget with the Apache license, although in that case they would have had to credit the original author, and the lack of credit is the original author's main issue with how this was handled.

Re: The Day AppGet Died (2020)

#32

Post by jjoonathan »

luciusdomitius wrote: post #30
alias_neo wrote: post #7

I've read this several times before, and every time I do it hurts just as much. Every time I read of another person who built something useful, so much so that it gets recognised by big-corp X, and being called in by Google or Microsoft, promised the recognition (and pay) they deserve, then having the rug pulled at light-speed from under them, I take it personally. I'm amazed, every time I read "The Day AppGet Died"…

Well. Cold reality is that even 5-year old kids know what sort of company MSFT is and what sort of people work for them. He acted like an useful fool, got treated like one. I even smirked a bit at his misery, even though I am normally not that kind of person. Had he instead reacted to the phone call with some extremely aggressive licensing, maybe even a software patent, now he would be discussing the terms of the out…

Yes, that's an important takeaway, but

> I even smirked a bit at his misery

smirking at someone for getting rolled is low.

Re: The Day AppGet Died (2020)

#33

Post by teh64 »

justsomehnguy wrote: post #14
causi wrote: post #10

Earlier quoted context omitted.

Just because they’re singing sweet songs now doesn’t mean they’re fundamentally different. Frankly I think it's only because Google, Facebook, et al. invented new kinds of evil too fast for Microsoft to keep up that they seemed warm and fuzzy at all. They're still the company that force-upgraded users to Windows 10, and they're still the company that's requiring you to have a Microsoft account for future versions of…

> requiring you to have a Microsoft account for future versions of Windows 11. How quickly people forgot about mandatory iTunes activation... > They're still the company that force-upgraded users to Windows 10 This is response for all those cries what MS should take the security of the OS seriously. No wonder what after a decade of disabled Windows Update on the endpoints (to conserve resources, to not to receive WPA…

> mandatory iTunes activation

Did macOS ever have mandatory activation? Because I have used it for a long time and have never needed that. You need some way to get a new OS version, which was buying a new macOS version on a disk (back in the day), then on the app store, and then it was a free upgrade from the app store. But you never needed an account to run the actual OS.

Re: The Day AppGet Died (2020)

#34

Post by simion314 »

moron4hire wrote: post #17
simion314 wrote: post #12

Earlier quoted context omitted.

And they are the company that bought Skype, forced me to create Microsoft accounts and then mess things up, now they boutght Minecraft and I just receive an ultimatum to switch my Mojang account to a Microsoft account. F U MS, can't you let me login with existing shit,. On a different topic, I am using some MS APIs at work (TTS stuff) and my impression of this MS products is bad, it feels like different teams that ha…

What are you talking about? Microsoft's Text-To-Speech APIs are the best on the market. Google's are definitely a distant second: not as many languages, not as many voices, and the output is nowhere near as good. After those two, there isn't really anything left worth mentioning.

I am talking about they have one documentation but if you look deeper there are 2 products, thay say here are 2 options long and short API , but look closer and see one uses names like "Name", "Voice" the other "name", "voice" , the list of voices of this 2 options are not the same , and you randomly get weird errors with shit message that will solve themselves in the next few days. If my memory is correct you authenticate in2 different ways.

So I would prefer MS do this;

1 this is our 2 completly different and incompatible APIs , they might look similar but are not the same, outpiut can differ even if you send same params to each one

2 give me good error messages, like if is your fault a request fails make it clear , if is my input the problem make it clear it is me and what is wrong

Re: The Day AppGet Died (2020)

#35

Post by causi »

zidad wrote: post #25
causi wrote: post #18

Earlier quoted context omitted.

Microsoft's Text-To-Speech APIs are the best on the market. Wow, I had no idea they were that good. Is there a way to get at them from a consumer level? For example, there are plenty of e-reader apps that use Google's TTS to read epub books as audiobooks. Anything similar for Microsoft or is it all on the developer side?

You can just try it out here from the browser if you like: https://azure.microsoft.com/en-us/services/cognitive-service...

That's a good demo, but it isn't much use for making audio content from ebooks.

Re: The Day AppGet Died (2020)

#36

Post by AshamedCaptain »

causi wrote: post #18
moron4hire wrote: post #17

Earlier quoted context omitted.

What are you talking about? Microsoft's Text-To-Speech APIs are the best on the market. Google's are definitely a distant second: not as many languages, not as many voices, and the output is nowhere near as good. After those two, there isn't really anything left worth mentioning.

Microsoft's Text-To-Speech APIs are the best on the market. Wow, I had no idea they were that good. Is there a way to get at them from a consumer level? For example, there are plenty of e-reader apps that use Google's TTS to read epub books as audiobooks. Anything similar for Microsoft or is it all on the developer side?

They have basically been licensing L&H then Nuance until they bought it outright.

Re: The Day AppGet Died (2020)

#37

Post by smoldesu »

alias_neo wrote: post #7

I've read this several times before, and every time I do it hurts just as much. Every time I read of another person who built something useful, so much so that it gets recognised by big-corp X, and being called in by Google or Microsoft, promised the recognition (and pay) they deserve, then having the rug pulled at light-speed from under them, I take it personally. I'm amazed, every time I read "The Day AppGet Died"…

Kinda reminds me of the whole Flicktype debacle. Pretty much every company of a certain size has their fair share of bad management and traitorous corporate ladder-climbers. We, the users, are powerless to stop this.

Re: The Day AppGet Died (2020)

#38

Post by stickfigure »

simion314 wrote: post #12
causi wrote: post #10

Earlier quoted context omitted.

Just because they’re singing sweet songs now doesn’t mean they’re fundamentally different. Frankly I think it's only because Google, Facebook, et al. invented new kinds of evil too fast for Microsoft to keep up that they seemed warm and fuzzy at all. They're still the company that force-upgraded users to Windows 10, and they're still the company that's requiring you to have a Microsoft account for future versions of…

And they are the company that bought Skype, forced me to create Microsoft accounts and then mess things up, now they boutght Minecraft and I just receive an ultimatum to switch my Mojang account to a Microsoft account. F U MS, can't you let me login with existing shit,. On a different topic, I am using some MS APIs at work (TTS stuff) and my impression of this MS products is bad, it feels like different teams that ha…

I don't understand this complaint. You want separate logins for every service? You can't even argue that there are privacy issues - these are now all part of the same company.

Separate logins incur a cost to both the service operator (who has to run multiple secure identity systems, build multiple 2FA systems, manage multiple customer service teams, etc) and the client (who has to remember multiple passwords). Consolidation of identity services is natural. One secure login is better than dozens of insecure ones.

Before you yell "password manager" admit that the average person doesn't even know what a password manager is. "Every user changes their workflow" is not a practical solution.

Re: The Day AppGet Died (2020)

#39

Post by jmcgough »

luciusdomitius wrote: post #30
alias_neo wrote: post #7

I've read this several times before, and every time I do it hurts just as much. Every time I read of another person who built something useful, so much so that it gets recognised by big-corp X, and being called in by Google or Microsoft, promised the recognition (and pay) they deserve, then having the rug pulled at light-speed from under them, I take it personally. I'm amazed, every time I read "The Day AppGet Died"…

Well. Cold reality is that even 5-year old kids know what sort of company MSFT is and what sort of people work for them. He acted like an useful fool, got treated like one. I even smirked a bit at his misery, even though I am normally not that kind of person. Had he instead reacted to the phone call with some extremely aggressive licensing, maybe even a software patent, now he would be discussing the terms of the out…

How is he going to take out a patent for or aggressively license OSS? The code is already out for anyone to use at that point.
Post reply on HN