Live data from Hacker News

The Microsoft 365 Copilot launch was a disaster

zdnet.com

581–590 of 591 posts

Re: The Microsoft 365 Copilot launch was a disaster

#581
post #294

Microsoft making questionable decisions lately, the official RDP client on Mac was renamed to "Windows App" some weeks ago. It's hard to come up with a worse name, Windows App is what I name any software product that runs natively on Windows. RIP all the helpdesk employees who have to explain this to end users

I'm not sure if it has to do with the UI redesign and renaming, but I don't feel the new app is as reliable as before. My RDP connections now fail all the time.

For me, the connection always fails the first time and after retrying it works.

Re: The Microsoft 365 Copilot launch was a disaster

#583

Earlier quoted context omitted.

> The real story nobody is saying out loud is that CEOs are much more replaceable by AI than are software engineers. Sorry, but that’s not true at all. It doesn’t really make a lot of sense. Who is replacing the CEO of a company with AI? The board? The board doesn’t want/can’t run the company. They will hire someone to “run the CEO AI”? Won’t that just be a CEO using AI? Maybe that makes it so the CEO is paid less Be…

Lets say that CEOs are no more or less replaceable with AI than all the other jobs. Throwing away all the humans to replace them with AIs is a move only an AI CEO would make, because and AI couldn't give less of a shit if something it does blows up in its face. Well, apparently real CEOs couldn't care less either. Imagining you're going to run a successful software organization (once you've hollowed out the people wh…

> Well, apparently real CEOs couldn't care less either.

Some healthcare ones did for a few weeks, after one of them got whacked by someone truly over their bullshit.

Re: The Microsoft 365 Copilot launch was a disaster

#585
post #413

Earlier quoted context omitted.

Well, that's not quite fair. NT is a very interesting and definitely original kernel design, for example; NTFS is a file system with unique properties, and AJAX was an API devised at Microsoft (that one absolutely lacks taste, but at least it's an original idea). That being said, I agree that the company and the brand evoke nothing but negative emotions in me, and I don't know anyone that would have anything better t…

NT is a very interesting DEC VMS clone (developed by the same team). In fact 9x was much more original design.

As/is was 95% of Apple's "innovation" over Xerox, but here we are.

I will admit Jobs put "style" and "finish" on things that MS never does.

Re: The Microsoft 365 Copilot launch was a disaster

#586

Earlier quoted context omitted.

Every single thing in which M$ has market capture is shockingly bad. Windows, Office, Azure.

Simple as this statement is it is also underrated. When you seriously consider their various products and properties it truly is a shocker at how consistently awful they all are.

The fact that they have such consistently terrible products, but yet still have over $3T market cap and are one of the 3 most valuable companies in the world is extremely frustrating and disappointing.

Re: The Microsoft 365 Copilot launch was a disaster

#587

Earlier quoted context omitted.

Yes, and I was already struggling to understand what Microsoft 365 actually meant. Adding AI and renaming it all to Copilot is the straw that breaks the camel's back.

Microsoft 365 = Word documents without absolute positioning. I tried it once to make a lost cat poster and ended up just using Krita.

[deleted]

Re: The Microsoft 365 Copilot launch was a disaster

#588

Earlier quoted context omitted.

Windows 2000 was pretty revolutionary

It was a security nightmare, but it was so close to what we're still using today it's not even funny.

I was around for the development, launch, and replacement of windows 2000. It was absolutely not a security nightmare when it came out and completely revolutionized desktop security (though not enough and was further enhanced through today)

Re: The Microsoft 365 Copilot launch was a disaster

#589

Earlier quoted context omitted.

Windows 2000 was pretty revolutionary

Compared to 9x? Sure, but it’s not like it was born in a vacuum. Compared to NT 4? Not really, I think. There were significant new things (MMC, Windows Installer, a first-party USB stack). I think there was a grand total of one headline new feature for developers (COM+, a continuation of MTS, a non-partition-tolerant distributed transactions thing). It’s not nothing, surely, but I don’t really see anything that deser…

Compared to Linux?

Compared to Solaris?

Compared to OS/2 Warp?

Compared to the completely underdeveloped operating systems of the time?

Don’t stop your comparisons at the low hanging fruit :D

Re: The Microsoft 365 Copilot launch was a disaster

#590

Earlier quoted context omitted.

Compared to 9x? Sure, but it’s not like it was born in a vacuum. Compared to NT 4? Not really, I think. There were significant new things (MMC, Windows Installer, a first-party USB stack). I think there was a grand total of one headline new feature for developers (COM+, a continuation of MTS, a non-partition-tolerant distributed transactions thing). It’s not nothing, surely, but I don’t really see anything that deser…

Compared to Linux? Compared to Solaris? Compared to OS/2 Warp? Compared to the completely underdeveloped operating systems of the time? Don’t stop your comparisons at the low hanging fruit :D

What I wanted to say is, many of us remember Windows 2000 as this watershed moment—I know I do—but the more I look at the contemporary developer docs, the more it appears to me that innovation in core OS services at Microsoft had largely already stopped at that time.

Quite a few things that were promoted as Windows 2000 features to developers ended up being deprecated into oblivion (transactions started implicitly due to entries in the Windows Registry, why did anyone think this a good idea?..), abstracted away (thankfully nobody remembers that Windows Installer has a half-baked SQL underlying it), forgotten on the curb of advancing technology (you can still use asynchronous monikers to define custom protocols for IE, but why would you), or just slowly turning into yet another stratum in enterprise software archaeology (WMI/CIM).

So if it was a watershed moment, it seems like it was more for Microsoft marketing than for general-purpose Microsoft APIs: Windows 2000 was the first NT promoted to consumers, as well as the first NT to run acceptably on respectively contemporary consumer hardware, and the contrast with 9x was indeed stark. But if we are speaking about when Microsoft innovated in its OSes, it really does seem like the period between maybe 1998 and 2005 was a lull, and that contrast that so shocked us then had little to do with the Windows 2000 release specifically and could just as well have happened for NT 4, if only RAM had been cheaper back in 1996. (Recall that Windows 95, née 93, was supposed and even announced to be the last release built on the Win16—or “Windows”—foundation.)

That’s not to say that Microsoft was idle. USB, PCI PnP, ACPI (and before it APM—remember APM?) are all bound to have taken serious kernel-level work, let alone the great Vista video driver rewrite. DirectX for X≠3D basically died, but that last part got really really important. HyperV I hear is competent and people do actually run it.

On the application side, Java was going to be the next big thing on Windows before it was shot in the head, .NET was of course unveiled shortly after Windows 2000, then Vista came along with transactional NTFS and the transactional registry and transactions everywhere were going to be the future (and you can see how that followed from the DCOM/MTS/COM+ work even if it wasn’t marketed that way). And there was WCF and WPF and XAML and XPS’s attempt to displace PDF and replicate Display PostScript and then COM was reborn as Metro/WinRT. And you see how a lot of that last paragraph is a mix of the unhinged (WCF) and the genuinely cool that ended up going nowhere either way? Much like the new Windows 2000 stuff I listed above was a grand vision of the future that fizzled out, there are like a half-dozen grand visions of the future here that were all at various stages at fizzling out at the same time.

Again, none of this is lazy, much of it is even novel. Yet somehow none of it ended up truly significant. Transactional NTFS could have been as large a shift as ZFS—but it wasn’t. Vista’s libraries could finally have brought BeOS’s filesystem-as-a-database to the mainstream—but it didn’t. And now ads in the Start menu are entering their second decade. Part of it is probably the slow death of the desktop in general. I can’t help thinking it’s not all of it, though. In retrospect, Windows 2000’s largely unused new features feel like the start of a trend.

Post reply on HN