Live data from Hacker News

Introducing Copilot+ PCs

blogs.microsoft.com

591–600 of 614 posts

Re: Introducing Copilot+ PCs

#591

Earlier quoted context omitted.

I mean in KDE. Using Dolphin.

I think Valve disable baloo (understandable since you don't want file indexing while gaming). That's probably why the default KDE search will perform poorly. You should be able to use KFind which will work kind of like the Windows XP search.

Thanks. While looking up KFind I found FSearch. That's almost VoidTools Everything.

Re: Introducing Copilot+ PCs

#592

Earlier quoted context omitted.

Yeah, “ARM-based Linux laptop with 22h battery life” is much more interesting to me than “Windows 11 ARM-based AI PC”. If the TPU can eventually be utilized by open models under Linux that’s just a cherry on top.

Personally agree. But let's be honest: the big shift to ARM in desktop will only happen with Windows.

Acorn tried very hard, but without a critical mass of software ported to the platform it was nearly impossible - Apple was the only other platform that survived.

Now, with open source, it’s easier to open up a place for other architectures. Android and iOS took over a lot of space traditionally reserved to Windows and Microsoft is not oblivious to that fact.

Re: Introducing Copilot+ PCs

#594
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…

It's really baffling, isn't it? A part of me wonders if Microsoft is simply unable to figure out how to make a good Windows search and so is looking for AI to do it for them. But it seems like shooting a mosquito with an elephant gun.

It is less baffling when you consider decisions are not being driven by engineers. Investors don't want a search engine. Investors (and other non-engineers) want "AI"

Re: Introducing Copilot+ PCs

#595
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…

I don’t understand why you say it doesn’t need AI. It’s like saying a financial application doesn’t need a database. Maybe it can use something else, but who cares what technology is used as long as it’s good? I’m willing to believe that AI is making this tech much more effective

Re: Introducing Copilot+ PCs

#596
post #252

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…

Do you expect anything else from the company that introduced "Plays For Sure" branding over a wide ecosystem, only to kill the ENTIRE thing (not just the branding) less than 5 years later? (as in, all purchased content became unplayable)

I was peripherally involved around that time. Trying to go through in my head what caused a lot of that, it feels like meetings were MBA heavy and light on engineering and design; whereas other startups have had more balanced meetings where the grunts could push back against the totally out-of-touch ideas of the pointy-hairs.

(I think where I was working we pushed back hard enough on this name that it never got launched... www.webaudionet.com was a really, really bad name: https://web.archive.org/web/20020401235841/http://www.webaud... )

Re: Introducing Copilot+ PCs

#597

Earlier quoted context omitted.

> "power-efficient" is a weird thing to claim, anyhow. What does it mean? Cycles per Joule, or cycles per second per watt. While staying at the laptop-level available power envelope. > PPC were much faster per socket than maybe even server class chips by intel The absolutely top POWER chips were at the time _somewhat_ superior to Intel (and AMD), but not by much. And that superiority was achieved by raw strength, the…

> The relationship between Apple and IBM has been rocky at times. Apple openly criticized IBM for chip delivery problems, though Big Blue said it fixed the issue. More recent concerns, which helped spur the Intel deal, included tension between Apple's desire for a wide variety of PowerPC processors and IBM's concerns about the profitability of a low-volume business, according to one source familiar with the partnersh…

> furthermore, if you look past the "Intel is just too slow for the power envelope" that you stated:

Well, yes. Intel was not able to deliver fast mobile CPUs on time. So Apple decided to give up and do it on their own.

> PS3 underpowered?

Yes. It was terribly underpowered. I worked with it back then, and it was slower than a 1GHz Pentium for practical tasks. The CPU in PS3 was clocked at around 3GHz, but it had full in-order execution. So any code with branches just died.

Sony's way around it was SPUs - special coprocessors, that were even more underpowered with little local memory. But there were 8 of them, and the common data bus was pretty fast.

It worked great for graphics and for something computation-heavy like Folding@Home. Kinda like modern GPUs. But it sucked for general-purpose code.

> Also if you compare like for like, the CPUs IBM put out in 2005 with 3.2ghz had a TDP of 75W. Intel CPUs in 2005 at 3.2GHZ used 130W TDP. both used 90nm processes.

Now compare their performance for actual tasks. You'd be surprised.

Cell architecture bombed. As a result, Sony switched to a regular architecture for PS3.

Re: Introducing Copilot+ PCs

#598

Earlier quoted context omitted.

Microsoft appearingly random naming conventions make me want to actively avoid using their products because I know the web searches will be heavily polluted. I thought big companies like this would have some sort of internal committee that decides if a new products branding makes it easier for customers to understand what the product is and where it fits in their offerings.

Having had to come up with a name for a corporate product and deal with things like trademarking, I can understand why they seem to repurpose names frequently. It is enormously time consuming to generate, vet, and apply for a trademark. There are so many other products and names and trademarks out there that it’s no wonder drug companies end up with unpronounceable gibberish for new product names.

This makes sense. I guess I didn't take namespace or government bureaucracy into consideration.

Come to think of it open source software has this issue too where two projects exist with the same name.

Re: Introducing Copilot+ PCs

#599
Really seems like their play is to use their business suite to sell huge privacy invasive tools under the guise of computing improvements.

This iteration of Microsoft products gonna really go for the throat.

Post reply on HN