Live data from Hacker News

The Day AppGet Died (2020)

keivan.io

41–50 of 132 posts

Re: The Day AppGet Died (2020)

#41

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.

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

I mean, there's the old Windows-only SAPI from the Windows XP days that they haven't been developing for several years now, and the current Azure Cognitive Services, which is just a REST API with a pretty standard auth scheme. There's an official .NET package for wrapping that REST API, but it's certainly not necessary to use it if you know how to handle REST APIs. Is that what you're talking about?

Re: The Day AppGet Died (2020)

#42

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.

What? You have all the power. You send an email and then stop buying their services.

'To whom it concerns, you guys are shitty so I'm cancelling services.'

Re: The Day AppGet Died (2020)

#44
post #24
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…

Well in my book the order is still something like Google About Windows 11: I switched my home desktop PC to Linux when I upgraded it early last year. I still have Windows 8 lying around mostly unused on a partition, but since it's a 32 bit version I would have to do a complete reinstall, and most of the software I'm using (including most games, thanks to Steam) runs just fine on Linux, so I haven't worked up the moti…

Apple and Microsoft are equals.

Re: The Day AppGet Died (2020)

#45

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…

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). Consol…

This is a lame excuse, say what after the forced account migration is my pourchase invalid? Will Microsoft just drop the db table with my purchase and logins? Will they refuse to migrate people after?

No, they have to keep all that data and confirm even 2 years from now that I paid for this game and migrate my logins ,

Tell me know what is more expensive

1 Keep the Mojang logins for Java edition. do nothing

2 Write ton of code to force migrate Java edition players into the XBox ,Microsoft accounts.

It is not lke I can play from Linux PC with an XBox person multiplayer so there is Zero benefit for me, just some mangers and develoeprs at MS getting busy. They fucked up my skype account move so this is why I don't like when they are trying to move me to their shit account, Now what? when they block my MS account I lose Skype and Minecraft too?

Re: The Day AppGet Died (2020)

#46

Earlier quoted context omitted.

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.

What? You have all the power. You send an email and then stop buying their services. 'To whom it concerns, you guys are shitty so I'm cancelling services.'

Sure, just delete your iCloud account, Microsoft account, Amazon account, Netflix account and Google account. It's so easy that anyone could do it!

Re: The Day AppGet Died (2020)

#47
post #5

Don’t ever forget that at its core Microsoft is still the same company we grew up with. Just because they’re singing sweet songs now doesn’t mean they’re fundamentally different. I know that there are a lot of developers on here that disagree with me and are all in on the ‘new’ Microsoft. I can’t change your mind. Ive watched Microsoft since the early 90s though and they’ve never really changed—-and buying GitHub and…

Just a nit: I fully agree with you that deep inside, Microsoft is still as evil as in the past (competition forced them to hide it a bit better is all). But I'm still all in on the `new’ Microsoft. I don't think these two necessarily exclude each other. I mean the alternatives are Linux, which I haven't the patience for, or Apple which is also evil but just in different ways.

You deserve what you get then.

Re: The Day AppGet Died (2020)

#48

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…

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). Consol…

> You want separate logins for every service?

I want a separate login for Minecraft than for MS services, yes.

> the client (who has to remember multiple passwords)

I'd guess that the majority of Mojang accounts don't have a corresponding MS account already.

> "Every user changes their workflow" is not a practical solution.

But that's precisely what MS are enforcing - you have to migrate your Mojang account to an MS account.

Re: The Day AppGet Died (2020)

#49

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…

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). Consol…

> You want separate logins for every service?

In short: yes.

In long: I want separate logins for different domains. In no universe should Minecraft share a login service with Azure cloud engineering. And I shouldn't have to log in to use offline applications locally. And teams should support different logins for many accounts, like Slack figured out ages ago. By forcing changes to the login pattern for negligible to negative consumer benefit, it's clear Microsoft continues to be broken.

Microsoft and login services are terrible, and uniting them under one login to rule them all doesn't help.

Re: The Day AppGet Died (2020)

#50

Earlier quoted context omitted.

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

I mean, there's the old Windows-only SAPI from the Windows XP days that they haven't been developing for several years now, and the current Azure Cognitive Services, which is just a REST API with a pretty standard auth scheme. There's an official .NET package for wrapping that REST API, but it's certainly not necessary to use it if you know how to handle REST APIs. Is that what you're talking about?

Yes, the Azure API, there are 2 different things under the hood, the short and login APIs, that are different names, different auth headers, different voices supported, voices with same name that have different styles supported. Bad errors messages that popup and get fixed in a few days but only on one of the APIs. The issue is that I am trying to combine the short and long APIs in one product and I am hitting this big inconsistencies, I see lcearly there are 2 teams and do things different , if you use only one section you have a completly different experience.

Edit. I do the REST calls directly, not via an SDK and use the documentation from MS for the REST API so no SDK documentation or SDK code that hides the issues.

Post reply on HN