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.
Yup, and Linux probably boots faster. On my NVMe w/ full-disk encryption (not through the disk’s microcontroller, through an outside FS), I boot to desktop in like 5 sec or less, and the desktop is fully usable. If I want to launch a program, I type the name and hit enter, and it launches in a couple seconds.
My M3 Mac is a little worse, since it gets confused about launching an app vs looking for a file, and it takes a bit longer to boot (20-30 seconds?).
But my SO’s Windows machine is something else. It takes a minute or two to boot, and after that it takes a minute or two to “settle.” I have no idea what it’s doing, but I generally get up and get a drink or something when my SO asks me to get something pulled up. Why is it so crappy?
xxx@xxx:~$ systemd-analyze Startup finished in 1.514s (kernel) + 3.331s (userspace) = 4.846s graphical.target reached after 3.328s in userspace.My machine is instantly usable in <5 seconds.
You’re letting me down firmware!
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?
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.
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).
I completely trust Systemd to accurately report on itself, the same as I trust American cops to police themselves.
Back when I used a HDD in my laptop, I was able to get my boot down to 20s or so. I don’t understand what MS is doing…
Someone once wrote something that compiled the Linux kernel on bootup with TinyC. Even this would be faster.