> Microsoft Comic Chat
I'd say teams is a rather comic implementation of chat... or, hmmm, perhaps more like tragic.
Killed by Microsoft
171–180 of 349 posts
Re: Killed by Microsoft
#172Earlier quoted context omitted.
> Contrary to Google Don't know that I really agree with this. Google does have experimental services and tools that they've killed (RIP Google Reader), but they have always provided migration for their core services. Look at Messaging, for example. Gmail chat -> Hangouts -> Hangouts Chat(?) -> Allo(??) -> Hangouts (again?) -> Android Messages. The problem is not that they leave users completely stranded, the unendin…
Nope. I've been left stranded by Google over and over. Talk to all the happy GSuite/Free users around now. Or people who developed Chrome Extensions prior to Manifest V3. Or who were banned from Google Fi, Youtube, or your app store of choice by an automated, broken algorithm. Or who developed Workspace Docs prior to mandatory security audits at price points which will break most independent developers. Or.... The ke…
I think you're lashing out at Google for a variety of different (and very good!) reasons, but they're outside the range of my comment. People getting banned from Google services because of broken automation is bad, of course, but it has nothing to do with the issue of whether migration paths are provided when services are sunsetted at Google.
My point is that for Google's core services, they generally due try to migrate users to a product that provides the same basic features, but that this isn't good enough. Forcing users to migrate because of pointless churn in your app offerings is already the problem, regardless of whether the migrations are handled well. Google is worse than Microsoft in this area not because they leave users stranded (usually), but because they're constantly switching their focus in products like messaging.
Re: Killed by Microsoft
#173Wasn’t there also a Groove that was a collaboration tool build by Ray Ozzie?
Re: Killed by Microsoft
#174Contrary 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…
https://killedbygoogle.com/ contains Nexus. That was clearly replaced by Pixel.
Disclosure: I work at Google, but not on anything related to this.
Re: Killed by Microsoft
#175Microsoft Works was an amazing piece of software. Always incredibly fast, with a small footprint, and had enough features to satisfy most personal and business needs.
[deleted]
Re: Killed by Microsoft
#176I like seeing the list of services, but I wish it was called "Microsoft Graveyard" instead of "Killed by Microsoft". Some of those wouldn't be around today regardless of the controlling organization, such as Silverlight and Encarta. To me, "Killed by Microsoft" makes it sound like Microsoft chose to discontinue a product that otherwise would still be "alive" today.
The HTML , site header, and domain are all clearly made to parallel https://killedbygoogle.com/
The only difference is .info vs .com .
Re: Killed by Microsoft
#177Contrary 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…
My oldest kid is just aging into gaming. We’ve got the Disneyland Adventures game and a Kinect for her.
Can confirm, Kinect is dead. You can only get them refurbished now, they’re no longer manufactured. The new consoles no longer support Kinect, we had to dig out an original Xbox One for her.
When the Kinect launched, Microsoft had trouble getting a critical mass of players that would attract developers. Without developers adding support to their games, Microsoft had a hard time marketing the device. This led to them bundling it with the Xbox One, but consumers were upset that they were being forced to buy the accessory.
I’m impressed they held out as long as they did, but eventually Microsoft caved and removed the Kinect from the bundle and dropped the price of the Xbox One. At that point, the Kinect was essentially dead. They quietly stopped manufacturing them and the new consoles no longer support them (though I’ve heard rumors you can buy 3rd party USB adaptors).
It’s a shame. That device is SO much more engaging and approachable for kids than trying to teach them to use a controller.
Re: Killed by Microsoft
#178Contrary 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…
> Contrary to Google Don't know that I really agree with this. Google does have experimental services and tools that they've killed (RIP Google Reader), but they have always provided migration for their core services. Look at Messaging, for example. Gmail chat -> Hangouts -> Hangouts Chat(?) -> Allo(??) -> Hangouts (again?) -> Android Messages. The problem is not that they leave users completely stranded, the unendin…
I feel like your example disproves more than it proves. The difference between Micrsoft Edge and Edge Chromium was that one day you launched the browser and it looked/worked a little different. Using Google for chat on the other hand is still extremely difficult because there is no clear path (as indicated by all your question marks) who is to migrate where and when they're supposed to do it.
Re: Killed by Microsoft
#179OneNote not being able to use local files is annoying as hell.
Re: Killed by Microsoft
#180Contrary 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…
Came here to make this point. Also, killing off products is not unhealthy. I for one am glad that eventually someone had the sense to kill off Bob. Sometimes- like for devs invested in Silverlight- it can be frustrating, but no reason to keep inferior or outdated products afloat.
Yeah, sometimes I wish MS would be a little more aggressive about killing off products. There are a few developer technologies that are in an awkward no man’s land: just barely supported without much of a future, but MS won’t say that so it makes for a lot of confusion if you’re new to the space and wondering what technology to use.