[simion314]

Just a rant about MS , people here claim how good they are with backwards compatibility. Bullshit, we were using an MS Azure TTS API, MS also had anew similar API but in alpha so we could not use that one back then. The old API has still more then 1 year of support but the MS "very nice guys" /sarcasm started breaking it, like one day one end point returns a different response structure, I fix it and next weak other endpoint changes the response structure, and the results start to bug out, returns success but transcription is incomplete etc .

In the end I did the work and move the new API, I am not sure how much this new one will work, maybe the nice guys at MS will want to restart things again with some new even more shiny thing.

Some fanboy will claim this is just a mistake and MS team are just incompetent and have no tests, and support if busy with other stuff.

[foul]

MS in fact is good with backwards compatibility only under windows/related software and maybe xbox, those bragging about MS' love of legacy aren't wrong, they are just focused on their almost historical product, what made Microsoft.

We can't say "no big deal" tbf, because for example Office files had fairly good longevity across updates (not perfect, a lot of file broke).

BUT anything else (embedded, cloud, AI, when they poisoned web standards, etc) isn't really under that much lauded backwards compatibility AFAIK.

[simion314]

Right, but in my case the API still has 1 year of support , so is negative backwards compatibility, MS devs break things before it;s end of life. Maybe I should be sorry, soem poor guy is tasked too work on the old API while the "cool" devs play with the new toys and maybe sabotage the other guy.