Introducing Copilot+ PCs

Post by metadat » Tue, May 21, 2024, 2:36 AM UTC

yread wrote: post #388

bambax wrote: post #272

> We set out to solve one of the most frustrating problems we encounter daily – finding something we know we have seen before on our PC. Today, we must remember what file folder it was stored in, what website it was on, or scroll through hundreds of emails trying to find it. It is indeed frustrating that one still cannot search effectively a local device, but it doesn't need AI to solve. It needs a proper search engi…

What there are still people who don't install Voidtools' Everything on all Windows PCs and assign it a global shortcut? Since I have it I don't even bother organizing stuff

Post by cka » Tue, May 21, 2024, 2:41 AM UTC

lallysingh wrote: post #359

isoprophlex wrote: post #124

Their "copilot" brand is so weird and... muddled. There's the AI code assistant thing that github actually started, there's the horrible chatbot maker GUI demoware, there's AI stuff you might be able to do with your sharepoint (if only you could get hold of the right ms sales rep to take your money), there's an app that does genai things on your personal MS account... And now there's a Surface rebrand? That org chart…

Windows Surface Copilot for Workgroups 360.Net It's kind of like those cryptographic keys they use a dictionary for: a nonsense noun phrase representing a number. Perhaps they're just encoding a SKU?

Post by mardifoufs » Tue, May 21, 2024, 2:47 AM UTC

neonsunset wrote: post #465

mardifoufs wrote: post #436

Earlier quoted context omitted.

I mean you literally work on Dotnet, don't you? That's probably why you don't have issues with the naming. I agree that it's currently fine now that it stabilized on the core naming scheme, but I don't see how it was very confusing when there's stuff like ASP.NET Core on framework, and ASP.NET Core on Dotnet core... that's just confusing, especially since other ecosystems don't usually have such a weird naming scheme…

It’s only problem in the eyes of HN because it is low-effort complaint from people who never used .NET and simply repeat what they read elsewhere. It’s just a popular thing to do, to make negative comments like this. Otherwise, this problem is completely made up in terms of anything that happened in last there-four years. And no, I don’t work on .NET save for a few simple contributions.

Post by ficklepickle » Tue, May 21, 2024, 2:59 AM UTC

mardifoufs wrote: post #475

neonsunset wrote: post #465

Earlier quoted context omitted.

It’s only problem in the eyes of HN because it is low-effort complaint from people who never used .NET and simply repeat what they read elsewhere. It’s just a popular thing to do, to make negative comments like this. Otherwise, this problem is completely made up in terms of anything that happened in last there-four years. And no, I don’t work on .NET save for a few simple contributions.

So the asp.net thing I highlighted isn't true? I'm sure the issue isn't that bad, but it sure is weird to claim that the naming wasn't horrible. Like, surely you could agree that the naming was much worse than it should've been?

Post by runevault » Tue, May 21, 2024, 3:03 AM UTC

tcpudp1 wrote: post #253

runevault wrote: post #236

Earlier quoted context omitted.

dotnet for me is the most obvious example of how terrible they are at branding. First there was .NET framework which was windows only (note I'm ignoring Xamarian because it was originally not owned by MS). Then they decided to do a reboot with cross platform support and named that Dotnet Core. This was honestly fine. But then we reach late in the 3.x timeframe and they declare for real and for true that Framework is…

[flagged]