3 ms·
For me, the only possible explanation is that Microsoft had nobody with actual experience left. The entire Teams team seems to be cheap junior developers togeth
by fxtentacle 4y ago
For me, the only possible explanation is that Microsoft had nobody with actual experience left. The entire Teams team seems to be cheap junior developers together with CoPilot.
It's not just that Teams is failing at solved problems, it's also that they aren't using Microsoft's own SDKs and APIs themselves anymore. Windows has good fast UI frameworks and all that cool stuff like SuperBoost which can make app startup appear instantly. Why is nobody using it?
And there is no useful integration to speak of. Why do I need to re-upload an OneDrive file into Teams? The exact same file is already stored on the exact same server. Does nobody there know about the magic of SHA512?
And how come if the internet has a hiccup while I upload a file, I have to re-upload the whole damn thing? In 1980 we already had resumable uploads via FTP.
Oh and who's the vendor creating one of the best performance tracking and optimization tools? Microsoft themselves. Did nobody ever dare to run this in a proper Visual Studio?
- jtwaleson 4y agoThey need to support Mac, Linux, iOS, Android too. It’s nice if you can do that on the same codebase.
- NovaDudely 4y agoIt is possible but then, for example, Windows has always had some degree of amateurish stuff in it. Rumour was, so take this with a grain of salt, that the CD loader in Windows 95/98 was developed by a high school intern over a summer holiday. Would make sense how it was stall out the entire system while when you put a CD in until it has been verified.
- prometheus76 4y agoI'll add another absurdity to your list: why doesn't Teams use the Office dictionary (which has customizable functionality) instead of making an undocumented hard-coded call to the Google Chrome repository and using their dictionary (which is not augmented with a customizable dictionary)?