Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Killed by Microsoft

killedbymicrosoft.info

Post reply on HN
Print view View original

341–349 of 349 posts

Re: Killed by Microsoft

#341

Post by codyogden »

Marcus10110 wrote: post #59
rvba wrote: post #26

Earlier quoted context omitted.

The "killed by microsoft" site looks like a rip off of the well known "killed by google" site. Id day that they really try to push fake controversy and extend the list e.g. Microsoft Edge just switched its technology and still exists.

It's not just a rip-off, it's build directly on top of the killedbygoogle repository! https://github.com/fabianoriccardi/killed-by-microsoft is not a fork, but it has many of the commits from https://github.com/codyogden/killedbygoogle The earliest commits from fabianoriccardi include git messages like: > replacing "Google" with "Microsoft", removed PressCoverage Anyway, great code recycling at least right? It's a fu…

Hi! Creator of Killed by Google. The code that runs Killed by Google has always been licensed under MIT, and it's changed significantly since the Microsoft version was cloned. There are multiple 'clones' that have popped up over the years using my repo as the base, and Fabiano is one of the few who kept my license in tact. The Microsoft version has been around for over a year, I think.

I agree that it is cool to see how it's been reused. :)

Re: Killed by Microsoft

#342

Post by Aissen »

chrisdirkis wrote: post #214
johnnyanmac wrote: post #147

Earlier quoted context omitted.

>Kinect => It's not dead ??? Is it alive? It very much has an immensely passionate community of students and hobbyists using it in ways well past its intended use (e.g. it's some of the cheapest mocap hardware you can buy). But I don't think you've been able to officially purchase one for 4+ years now. Hard to call that "alive" in a business sense. Honestly a real shame that Xbox hasn't pivoted it into some other tea…

The Azure Kinect was released as a successor for the research and business applications[1]. I know one roboticist who has used one, but no one aside from that. Definitely dead as a consumer gaming device, but a product evolving towards a discovered usecase is a surprisingly happy outcome from MS. [1] https://azure.microsoft.com/en-au/services/kinect-dk/

The page says "Call to order", which is quite a bit different from a publicly available product.

Re: Killed by Microsoft

#343

Post by BizarroLand »

px43 wrote: post #160

Things NOT killed by Microsoft: Clear text passwords collected and stored in LSASS.EXE long term. SMBv1 Machines spraying their local user's password hashes all around the network constantly. LLMNR Symmetric (password based) authentication. SPNs with Domain Admin privileges whose password hashes can be queried by any user at any time. Full mappings of every user, machine, privileged level, authentication metadata, an…

Things that need to be killed by Microsoft:

Their online manuals that when you try to find something like how to script a very specific powershell event you instead get to read about what powershell is, what commands you could conceivably write, every word that powershell knows, who made powershell, why powershell is so important, how you can get certifications in using powershell, and other functions powershell can do but you cannot find in microsoft's online manual how to specifically write the command you need to write to achieve the specific goal you want to achieve.

For that you have to go somewhere else or figure it out on your own.

Their online manuals are the lexical equivalent to having to memorize the entire World Book Encyclopedia to be capable of ordering a hotdog with mustard.

Re: Killed by Microsoft

#344

Post by B1FF_PSUVM »

EvanAnderson wrote: post #205
B1FF_PSUVM wrote: post #162

Earlier quoted context omitted.

> It's ridiculously inefficient. You mean that simple tasks take many billable hours? Hmmm ...

Irresponsible use of disk space, CPU cycles, and network bandwidth is more what I'm referring to. I've scripted some cleanup of profiles to take care of disk space exhaustion in a couple of situations. Cleaning up after Teams hasn't been a revenue generator for me, but it has created complaints. Anything that causes me to receive complaints from users draws my ire. (I subscribe to the "sewer system" theory of sysadmi…

Just for kicks, a little gedanken-experiment:

Product A costs 2 bazillion, and is perfect - for a 10 year lifetime, it works perfectly and requires no support. Zero additional cost.

Product B does about the same, costs only 1 bazillion, but is rather shoddy - over a 10 year lifetime, it will require a further 3 bazillion worth of fixes, support and extra resources. That does feed a lot of families, though.

Take your guess at what happens.

Yeah, me neither.

Re: Killed by Microsoft

#345

Post by EvanAnderson »

B1FF_PSUVM wrote: post #344
EvanAnderson wrote: post #205

Earlier quoted context omitted.

Irresponsible use of disk space, CPU cycles, and network bandwidth is more what I'm referring to. I've scripted some cleanup of profiles to take care of disk space exhaustion in a couple of situations. Cleaning up after Teams hasn't been a revenue generator for me, but it has created complaints. Anything that causes me to receive complaints from users draws my ire. (I subscribe to the "sewer system" theory of sysadmi…

Just for kicks, a little gedanken-experiment: Product A costs 2 bazillion, and is perfect - for a 10 year lifetime, it works perfectly and requires no support. Zero additional cost. Product B does about the same, costs only 1 bazillion, but is rather shoddy - over a 10 year lifetime, it will require a further 3 bazillion worth of fixes, support and extra resources. That does feed a lot of families, though. Take your…

I feel like fractional reserve banking and the broken windows fallacy fit in here somewhere too. >smile<

Re: Killed by Microsoft

#346

Post by randomsearch »

Kuinox wrote: 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…

IoT Core is dead. Can’t recall the details but I wanted to use it and it no longer supports modern platforms.

Re: Killed by Microsoft

#347

Post by iratewizard »

coolspot wrote: post #165
iratewizard wrote: post #96

Earlier quoted context omitted.

I can't name a single messenger with worse user experience.

Try Skype?

Even shitty Microsoft Skype isn't as bad as teams. Skype never just held onto messages without delivering them. Teams can't even do the core thing it's supposed to do correctly - send messages.

Re: Killed by Microsoft

#348

Post by blagie »

bscphil wrote: post #172
blagie wrote: post #166

Earlier quoted context omitted.

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

No, all of these were places where uses were left stranded.

If you started a business which relies on functionality in Manifest V2, and Google wants to block ad blockers with Manifest V3, you're SOL. If you started a small business which makes Workspace apps for local companies, and Google starts requiring a $50k security audits which are greater than your profits, you're SOL, and those local businesses are SOL. And so on.

There is no migration path, at least which allows you to stay in business. I'm not talking about changing chat clients. I'm talking about Google razing thousands of small businesses to the ground because they don't matter to a $1.8T goliath. All of these businesses were Google's partners in a Google ecosystem, not competitors.

Microsoft -- at least modern Microsoft -- doesn't do this.

This is why I always advise people never to rely on Google for B2B. It's transactional; it's fine for making a quick buck if you've got something you think will make you a mint for a year or two, but it's not fine for building a sustainable business.

Post reply on HN