Live data from Hacker News

Anomalous CPU utilization on Windows build node caused by ads

twitter.com

231–240 of 261 posts

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

#231

Earlier quoted context omitted.

Where are you buying graphics cards with less than two years of warranty? If your GPU budget is that slim, you should probably be relying on integrated GPUs.

Probably in every place that is not the European Union which mandates 2 year warranties. Rest of the world iirc is 1-year.

I did check about five brands of AMD graphics card on Newegg US before posting, and didn't see anything shorter than two years, with three and five years quite common. I also once bought an AMD card with a lifetime warranty, though I believe that particular manufacturer has since stopped offering those terms on any of their models.

So the question remains valid: what are the GPUs being sold with super short warranties, and are they even worth buying in the first place?

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

#232
post #6

A related observation: I have between 4-8 *nix, MacOS, iOS, machines running on my home network at any given time. I’m using piHole (with base config) to block ad traffic. My blocked percentage hovers around ~10%... until I boot up my one Windows 10 machine, which spikes the blocked ad traffic to ~25% and remains that high -with zero applications running mind you - until I shutdown the machine, after which it quickly…

Windows Defender's realtime protection in Windows 10 is also terrible. Practically monopolises an entire core at all times. To make things worse, you cannot permanently disable it without a GPO. And Microsoft is known to keep taking GPOs out of Pro.

reg add "HKLM\Software\Policies\Microsoft\Windows Defender" /v "DisableAntiSpyware" /t REG_DWORD /d "1" /f

reg add "HKLM\System\CurrentControlSet\Control\WMI\Autologger\DefenderApiLogger" /v "Start" /t REG_DWORD /d "0" /f

reg add "HKLM\System\CurrentControlSet\Control\WMI\Autologger\DefenderAuditLogger" /v "Start" /t REG_DWORD /d "0" /f

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

#233
post #230

Earlier quoted context omitted.

How long do you think a major OS should have 32 bit support? Everything cant be supported forever.

Aside from the noticably lower memory usage due to smaller pointers - Microsoft found that x86_32 is the lingua franca for WoA emulation. If all the binaries are x86_64 and there are legal problems emulating it, there might be problems switching Macs to ARM CPUs.

> and an emulation layer is a legal nightmare

It really isn't. And Apple can win that fight even if Intel tries to cause trouble.

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

#234

Earlier quoted context omitted.

> 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?

Mac OSX comes with chess. What's the difference?

Chess is a noble activity.

Candy Crush is pure garbage.

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

#235

Earlier quoted context omitted.

I wonder if WINE will ever be enough to cover all these cases. Though the cost of Windows licenses is generally trivial for businesses and they want support. I don't know how good RHEL for Workstations is but maybe that'd get more adoption in business if WINE was perfect and that desktop experience was as good as/better than Win10, or even had a DE made to be as similar as possible to Win10 to make it easier for empl…

How can WINE ever be as good as Windows when it is forever doomed to play catchup with a vast team of developers and decades of secret compatibility hacks that make Windows behave differently for different applications on purpose? I know that the hacks exist in a special shim layer and Windows has a database of applications that require certain sets of shims enabled. But details like an actual documentation of the in…

Maybe if a big company started funding it.

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

#236

Earlier quoted context omitted.

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.

> people stop underestimating what users actually do with computers Oddly, this is the factor that underlies most of my personal beefs with both Microsoft and Apple. What's wrong with my wifi? At least I can look in journalctl on linux. My laptop doesn't have enough screenspace - I can use i3wm on linux. I want double-click to include '*' and '/' and ':' in a "word", hey I can change xterm config. I want left-mouse-b…

Trackpad drivers on linux are not even close of the kind of gesture MacOS allow, with the help of a third party app.

And to configure the said trackpad, I have a nice GUI allowing me to define dozens of mouvement, triggers and response events for whatever application. No need to study the obscure documentation of xinput or whatever, if you're even successfull to find it on the web, only to dicover the possibilities doesn't go over of what you were able to do 10 years ago, which was very basic, e.g single tap, double tap, 2 fingers tap and that it. Last time I checked, 3 fingers swipe was not even registered.

Desktop interface of Linux computers feels like outdated copy of Windows. XFCE and LXDE looks like windows 95. Gnome, Mate and Cinamon never made it past 2008 and KDE is buggy as hell and a mess to configure.

And most desktop application feels like they have been made by a company going broke before being able to polish the interface.

With MacOS, you have the best of both world: a standard nix system, with a nice interface, a repository system (brew, macport) and polished commercial applications from an app store or from the wild.

Linux is good for niche applications: server, embedded systems, and a few specialized distro like kali or tails. For regular desktop application, that's still functional, but without the happiness.

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

#238
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?

Sadly, this story is wrong and stems from a misunderstanding of how this feature works. The OS bootstraps these suggested apps from a configuration hosted by Microsoft servers, not anything present in your ISO. (e.g. https://twitter.com/thurrott/status/1122847063312613377)

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

#239
post #156
post #8

Earlier quoted context omitted.

> The duality of modern Microsoft is absolutely astounding. See: http://bonkersworld.net/organizational-charts I don't work there, but I've heard Microsoft is more like a federation of organizations than one giant consistent, cohesive team.

Because its buried far down and I can’t edit my post, I want to hijack this post to point out that it turns out in newer builds MS has actually removed the Candy Crush auto installation. https://mspoweruser.com/rejoice-windows-users-candy-crush-is... I didn’t notice because my Windows 10 image is out of date, presumably getting the latest ISO would fix the problem.

Nope. This feature bootstraps from the web and it's still in the latest update post-fresh install. This article is incorrect.

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

#240

Earlier quoted context omitted.

Probably in every place that is not the European Union which mandates 2 year warranties. Rest of the world iirc is 1-year.

I did check about five brands of AMD graphics card on Newegg US before posting, and didn't see anything shorter than two years, with three and five years quite common. I also once bought an AMD card with a lifetime warranty, though I believe that particular manufacturer has since stopped offering those terms on any of their models. So the question remains valid: what are the GPUs being sold with super short warrantie…

The situation was much different 5 or 10 years ago.

One year was the best you'd get, 90 days was common.

Post reply on HN