941
Microsoft AI CEO pushes back against critics after recent Windows AI backlash — "the fact that people are unimpressed ... is mindblowing to me" (www.windowscentral.com)
submitted 8 months ago by to c/technology@lemmy.world
436 comments fedilink hide all child comments
 

Microsoft's AI CEO, Mustafa Suleyman, has shared his opinion after recent pushback from users online that are becoming frustrated with Copilot and AI on Windows. In a post on X, Suleyman says he's mind blown by the fact that people are unimpressed with the ability to talk fluently with an AI computer.

His post comes after Windows president Pavan Davuluri was recently met with major backlash from users online for posting about Windows evolving into an agentic OS. His post was so negatively received that he was forced to turn off replies, though Davuluri did later respond to reassure customers that the company was aware of the feedback.

you are viewing a single comment's thread
view the rest of the comments
[–] 6 points 8 months ago (1 child)

What the hell kind of hardware are you running, son? Is your system waiting for the superconducting magnets of your particle accelerator to cool? Is your 400 lbs Honeywell tape drive running self-assessment tests? Is the communications array realigning to restore the connection to your hidden villainous moon base? What is taking fourteen seconds?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 8 months ago (1 child)

    That'd at least make sense, this is a (literal) black box. Seriously, my monitor takes long enough to wake that it's at the boot loader screen by the time it's ready.

    I found a post on Reddit claiming it's a RAM thing, and I should enable XMP to avoid it. But I've already got XMP enabled so I need to poke around it again.

    And also disable the 5 second delay in the bootloader, not like I'm ever using that fallback option.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 5 points 8 months ago

    The usual suspect in this scenario is crappy USB devices, hubs in particular. Unplugging all USB devices and rebooting to check the difference is always a solid and easy first diagnostic step. If that turns out to be the issue you can add them back piecemeal to isolate the offender(s).

  • permalink
  • fedilink
  • source
  • parent