Live data from Hacker News

Killed by Microsoft

killedbymicrosoft.info

301–310 of 349 posts

Re: Killed by Microsoft

#301

Earlier quoted context omitted.

Nice list! You forgot Microsoft hardware, too. Do they still make webcams? The Z-80 soft card? And what about the software they made for the Apple 2e?

I did mention one hardware product in my list – Z-80 SoftCard (expansion card for Apple IIs which had an embedded Z80 CPU so they could run CP/M software) Yes they still sell webcams: https://www.microsoft.com/en-ww/accessories/products/webcams... I don't think Microsoft had many software products for Apple IIs. A large part of the point of the Z-80 SoftCard was that then their CP/M 8080/Z80 product line would run on…

I believe multiplan also existed for the TI 99/4a on cartridge.

Re: Killed by Microsoft

#302
post #238
post #148

Earlier quoted context omitted.

What promise did Google break with Stadia?

One example: https://www.destructoid.com/google-stadia-facing-class-actio... The subpar game library is another.

> The suit, originally filed back in October 2020 and moved to a New York federal court last week, alleges that Google, alongside developers Bungie and id Software, stated that the Stadia service would feature 4K resolution support, but did not walk back or correct this statement once it was openly reported that Stadia was upscaling several titles from resolutions such as 1080p and 1440p, rather than offering “true” 4K resolution.

That's one flimsy ass lawsuit. Upscaled 4K for some titles ( admitted by Google themselves) is still 4K.

For the game library, did Google promise they'll have every game on it? What promise was broken? They worked with game developers directly, paying to get games ported ( be it indie or Ubisoft/EA/Rockstar). They should have done more, but it's not like Stadia was advertised as "the platform you can play all games on" and then it turned out you only have 20 games.

Re: Killed by Microsoft

#303

I really miss Windows Phone. It was a great alternative to iOS and Android and I used it for years (Omnia 7, then Lumia 920) until I switched to iPhone as WP was into inevitable demise by Microsoft. The interface was beautiful, smooth, modern looking. Whoever designed WP (and Zune) probably deserves a much better place than Microsoft as they were just too good. I love Apple's design aesthetics in many ways, but still…

WP was the realistic 3rd alternative mobile ecosystem. Sad how the industry gave up without a fight to the global duopoly.

Re: Killed by Microsoft

#304
post #78

Earlier quoted context omitted.

Teams is unbelievably shit though. It’s like they don’t even care.

Slack is much better as a corporate chat app, but I’m not sure that’s necessarily good in the broader picture because I’m not sure you want to maximize chat engagement in a corporate setting. There are weird cultural effects to that, and paradoxically having a shittier app for that might get you the benefits of being able to chat with your coworkers and ask them questions without the weird social effects.

Depends. Who owns the data contained in the chat?

Re: Killed by Microsoft

#305
post #291
post #50

Contrary to Google, Microsoft often provide a migration path to another of their service covering the same usecases. Examples: Skype For Business => Teams. Microsoft Edge => Chromium Edge. Windows 10 IoT Core => It's not dead ??? Office Viewer => Web Based Office Kinect => It's not dead ??? Microsoft Anti-Virus for Windows => Windows Defender Come on, microsoft has big flaws but backward compat/keeping old product al…

Not always, XNA (C#) => DirectXTK (C++) C++/CX => C++/WinRT (back to ATL / Visual C++ 6.0 dev experience) Form/WPF => UWP (.NET Native / C++/CX / WRL) => WinUI 3.0 (.NET with CsWinRT, C++/WinRT) .NET Framework => .NET Core All of them require rewrites, leave relevant use cases behind, at least they leave the lights running for them to still be targeted, which makes many stubborn to keep using the stuff that actually…

Your migration from .NET Framework to .NET Core required a rewrite? Unless you are doing low level things, I doubt. All ours library and apps survived the migration without a rewrite.

Re: Killed by Microsoft

#306
Lync, Skype, Skype for Business, Teams, and probably few more intermediate apps. Practical diversion of corporate communication. Many people stuck to Lync as it had been working surprising long until it stopped, then folks started to use Skype but every time the wrong version of it. Now Skype is dead and MS reinvents video calls from scratch.

Re: Killed by Microsoft

#309
post #305
post #291

Earlier quoted context omitted.

Not always, XNA (C#) => DirectXTK (C++) C++/CX => C++/WinRT (back to ATL / Visual C++ 6.0 dev experience) Form/WPF => UWP (.NET Native / C++/CX / WRL) => WinUI 3.0 (.NET with CsWinRT, C++/WinRT) .NET Framework => .NET Core All of them require rewrites, leave relevant use cases behind, at least they leave the lights running for them to still be targeted, which makes many stubborn to keep using the stuff that actually…

Your migration from .NET Framework to .NET Core required a rewrite? Unless you are doing low level things, I doubt. All ours library and apps survived the migration without a rewrite.

WCF, Forms/WPF (3rd party controls), Sitecore, SharePoint, Dynamics, SQL Server managed runtime, App Domains,...

Re: Killed by Microsoft

#310

Earlier quoted context omitted.

What about Teams makes you think that? My experience has been the opposite. But that could have just been that it fitted our setup well. Or that I haven't tried better.

Search through messages doesn't give any context or even let you jump to the context. Very unresponsive scrolling. Notifications have been unreliable for me.

They finally fixed search so you can jump to the context a month or so back. I have no idea why it took so long, but search is actually helpful now
Post reply on HN