Live data from Hacker News

Anomalous CPU utilization on Windows build node caused by ads

twitter.com

21–30 of 261 posts

Re: Anomalous CPU utilization on Windows build node caused by ads

#21
post #2

The duality of modern Microsoft is absolutely astounding. How they can simultaneously do incredible things for Github, and open source Windows components, while continuing to not fix the most user hostile Windows ever produced, is completely bonkers. My litmus test for whether Windows is finally fixed is whether of not it’s possible to install it without Candy Crush, but unfortunately without killing the network and…

> My litmus test for whether Windows is finally fixed is whether of not it’s possible to install it without Candy Crush

https://mspoweruser.com/rejoice-windows-users-candy-crush-is...

What's you new litmus test?

Re: Anomalous CPU utilization on Windows build node caused by ads

#22
post #4

Earlier quoted context omitted.

Seems to me that DirectX is the last remaining barrier to finally getting the majority of the Windows user base to migrate to Linux. That and driver support.

You are ludicrously incorrect, just as everyone for the past 2 decades has been when they have predicted the year of the Linux Desktop. This trend will continue until Linux Desktop people stop underestimating what users actually do with computers.

Play XBill and write manifestos with LaTeX?

Re: Anomalous CPU utilization on Windows build node caused by ads

#23
So the objection is that Internet Explorer has msn.com as its default homepage. This is fair, it's ridiculous and a relic from a long gone age.

But so is Internet Explorer. What kind of super old Windows version were these people running? What caused IE to open out of the blue? Windows has plenty flaws but randomly open browsers is not one I'm familiar with.

Re: Anomalous CPU utilization on Windows build node caused by ads

#24
post #4
post #2

The duality of modern Microsoft is absolutely astounding. How they can simultaneously do incredible things for Github, and open source Windows components, while continuing to not fix the most user hostile Windows ever produced, is completely bonkers. My litmus test for whether Windows is finally fixed is whether of not it’s possible to install it without Candy Crush, but unfortunately without killing the network and…

Seems to me that DirectX is the last remaining barrier to finally getting the majority of the Windows user base to migrate to Linux. That and driver support.

[deleted]

Re: Anomalous CPU utilization on Windows build node caused by ads

#25
post #2

The duality of modern Microsoft is absolutely astounding. How they can simultaneously do incredible things for Github, and open source Windows components, while continuing to not fix the most user hostile Windows ever produced, is completely bonkers. My litmus test for whether Windows is finally fixed is whether of not it’s possible to install it without Candy Crush, but unfortunately without killing the network and…

Honest question and I am absolutely not starting an argument, but what have they done for Github? All I'm aware of is making private repos free, but I haven't seen anything beyond that. I must be out of the loop.

Re: Anomalous CPU utilization on Windows build node caused by ads

#27

The guy probably has infected machine... which is far more likely than MS runing ad farm

Have you used windows 10 recently? I didn't realize how bad it was until I installed a fresh copy of windows 10. My backup windows machine has so many registry patches to disable the crapware that I didn't recall how bad it truly is by default.

Re: Anomalous CPU utilization on Windows build node caused by ads

#28

The guy probably has infected machine... which is far more likely than MS runing ad farm

We have all the proof we need that MS is running an ad farm from the base windows experience. What proof do you have that he was infected with malware beyond that?

Where's that proof? I also run windows 10 at home, no issues with cpu or ads. The build servers at work? Same. no IE cpu hogs, no ad farms ... That's why i think this is some malware that has gotten by, and not ad farm.

Re: Anomalous CPU utilization on Windows build node caused by ads

#29
post #2

The duality of modern Microsoft is absolutely astounding. How they can simultaneously do incredible things for Github, and open source Windows components, while continuing to not fix the most user hostile Windows ever produced, is completely bonkers. My litmus test for whether Windows is finally fixed is whether of not it’s possible to install it without Candy Crush, but unfortunately without killing the network and…

> My litmus test for whether Windows is finally fixed is whether of not it’s possible to install it without Candy Crush https://mspoweruser.com/rejoice-windows-users-candy-crush-is... What's you new litmus test?

Funny that you're being downvoted for presenting evidence contradicting the OP. The groupthink in this thread is overwhelming.

Re: Anomalous CPU utilization on Windows build node caused by ads

#30

So the objection is that Internet Explorer has msn.com as its default homepage. This is fair, it's ridiculous and a relic from a long gone age. But so is Internet Explorer. What kind of super old Windows version were these people running? What caused IE to open out of the blue? Windows has plenty flaws but randomly open browsers is not one I'm familiar with.

The comment on randomly opening windows is fair (I don't see what caused it either), but this was a build VM, not a workstation - there is no reason to upgrade the browser. A more pertinent question is why are MS still shipping IE by default.
Post reply on HN