News for hackers. Stuff that matters.
Re:Anomalous CPU utilization on Windows build node caused by... by Razengan on Friday July 12, 2019 @12:34PM (#20421975)
Things like these is why most Mac converts never want to return to Windows. Not just the issue in TFA/post, which may seem trivial, but the overall “telemetry” debacle and experiences like jtdev’s comment.

For all their claims of having reformed, Microsoft will always be that ex you don’t want to do anything with ever again.

There are worse horrors than the lack of a physical Escape key, waiting on the other side of the fence.

Re:Anomalous CPU utilization on Windows build node caused by... by ctrl-j on Friday July 12, 2019 @12:54PM (#20422179)
I love the idea of Apple being more privacy focused, and helping us keep our data more secure. I have a touchbar macbook pro, and a headphone-jackless iphone. I just wish they wouldn't beat me with their opinionated hardware and software choices.

Deprecating open gl. Eliminating 32-bit support. Forcing me to use dongle after dongle (ethernet, usb-A, HDMI, and SD card)

Magic mouse has such a terrible sensor, not to mention the charging port location. I actually replaced it with a logitech because it's pretty much unusable for any precision work.

Heck, I bought an eGPU enclosure recently because I had a set of nvidia cards lying around.. I can only use it in bootcamp though, because of course macs only support AMD cards...

Microsoft may be an abusive ex, but apple is pretty much the same melody with different lyrics.

Re:Anomalous CPU utilization on Windows build node caused by... by Razengan on Friday July 12, 2019 @01:00PM (#20422236)
Perhaps we should all keep and maintain a Linux machine in the event that Apple and Microsoft both decide to screw us over.
Re:Anomalous CPU utilization on Windows build node caused by... by asveikau on Friday July 12, 2019 @02:27PM (#20423101)
What do you mean keep a spare machine for emergencies? Some of us have always had them as primaries, rather than leaving that world.

20 years ago, the type of person analogous to a typical HN type would have been on Linux. Thread after thread on places like Slashdot started from a position of Linux advocacy as a common baseline. Then in the early 2000s there was a massive shift to Mac among those types.

Personally, I miss the days of rank and file in such communities being desktop Linux advocates. We lost something of our soul.

Re:Anomalous CPU utilization on Windows build node caused by... by AnIdiotOnTheNet on Friday July 12, 2019 @03:45PM (#20423796)
I, for one, don't miss it. Linux Desktop evangelists are horrifically annoying people to deal with because they look down on everyone, believing themselves superior for using it. Tell them Linux doesn't work for what you're doing and they'll say you should change what you're doing, tell them it is missing essential functionality for you and they'll insist you don't need it, tell them you don't like the way parts of the system work and they'll list a dozen reasons you're wrong. Then, after roundly dismissing all criticism, they'll gaze into the heavens and shout "why won't more people use the Linux Desktop? Is it not pretty enough!?". In short, they're condescending assholes and I'm glad they aren't nearly as prevalent as they used to be.
Re:Anomalous CPU utilization on Windows build node caused by... by asveikau on Friday July 12, 2019 @04:15PM (#20424084)
I think your comment itself is a little presumptuous of motives and commits some of what you accuse others of doing.

But that aside. The free unix-like desktop has a lot of choices to be made, and one person's setup isn't going to be the same as another's. To me, that is the opposite of looking down on somebody for what they use, if we all agree that these are legitimate choices. And there is a little bit of a spirit that if something is lacking, you can try to pave your own way, which I don't see as a bad thing, though I can see others rejecting it.

If anything I think the current community is a little too homogeneous, with a lot of people opting for stock Ubuntu or whatever, than it used to be, and that's a criticism I would make.

Re:Anomalous CPU utilization on Windows build node caused by... by AnIdiotOnTheNet on Friday July 12, 2019 @04:21PM (#20424130)
I don't have a problem with people who use Linux Desktop, they have their reasons for their choices just as I do, many of which I would agree with[0]. My problem is with evangelists, people seeking to convert others to their chosen religion of Linux Desktop. Unfortunately because Linux Desktop users have a lot of overlap with Linux Desktop developers these attitudes still pervade the community. Case in point, how often do you hear a variation on the phrase "normal users don't need that"?

[0] and in fact I have a higher quantity of my devices running a Linux Desktop than I do Windows, but my main rig is Windows and that's unlikely to change for many reasons.

Re:Anomalous CPU utilization on Windows build node caused by... by II2II on Friday July 12, 2019 @04:58PM (#20424427)
> Linux Desktop evangelists are horrifically annoying people to deal with

Agreed, and I am a Linux user. I would much rather spend my time with people who are interested in using Linux rather than promoting it. The discussions are much more meaningful. Besides, evangelists from one side tends to attract evangelists from the other side (with each side being as bad as the other). Once that happens, annoying advocacy tends to transform into belittling bickering.

Re:Anomalous CPU utilization on Windows build node caused by... by tapoxi on Friday July 12, 2019 @02:57PM (#20423359)
It's ironic, Linux today is in a better state than its ever been. Chrome is Chrome, dependency hell is more easily mitigated by containerization, desktop environments have mostly become stable, hardware from Purism, System76, and Dell is quite good.

I think a lot of us just end up with Macs because work IT hates the idea of managing Linux machines and macOS gets you 95% of what you need.

Re:Anomalous CPU utilization on Windows build node caused by... by JoshTriplett on Friday July 12, 2019 @03:05PM (#20423439)
> I think a lot of us just end up with Macs because work IT hates the idea of managing Linux machines

Many of us end up with Linux precisely because work IT doesn't manage Linux machines. (What's worse is when they think they can manage Linux machines.)

Re:Anomalous CPU utilization on Windows build node caused by... by pmikesell on Friday July 12, 2019 @04:13PM (#20424061)
Everything you say is true, but I also remember every time slashdot would publish browser usage percentages it was something like 70% IE. visible perception did not match reality, even then.
Re:Anomalous CPU utilization on Windows build node caused by... by Narishma on Friday July 12, 2019 @04:33PM (#20424240)
How much of that was people accessing the site from their workplace? IE was mandatory in many places back then.
Re:Anomalous CPU utilization on Windows build node caused by... by pault on Friday July 12, 2019 @03:15PM (#20423533)
It seems that GP forgot to include the sarcasm flag.
Re:Anomalous CPU utilization on Windows build node caused by... by chefandy on Friday July 12, 2019 @01:16PM (#20422363)
Linux machines are fantastic if you don't need to use commercial software for things like graphics, as many web-focused developers do.
Re:Anomalous CPU utilization on Windows build node caused by... by godelski on Friday July 12, 2019 @01:27PM (#20422468)
I do graphics, but on the scientific side, we all use Linux. Except when the lab provides us Macs, then we get frustrated and just remote in.

I'm just trying to detangle the type of graphics being mentioned. I do wish Nvidia drivers were better, but maybe that'll happen with ROCs coming out soon.

Re:Anomalous CPU utilization on Windows build node caused by... by marcosdumay on Friday July 12, 2019 @01:44PM (#20422666)
> I do wish Nvidia drivers were better

Get AMD. Why do people insist on getting Nvidia cards and then complain that those aren't aimed at them? Get the one that is selling to you.

Re:Anomalous CPU utilization on Windows build node caused by... by ahartmetz on Friday July 12, 2019 @01:58PM (#20422842)
Cannot reply to sibling... Nvidia doesn't have simply the best OpenGL implementation, it has the fastest and most forgiving implementation. No argument about speed (or Cuda), but by being forgiving of code that shouldn't work according to spec, it creates lock-in and makes more conformant implementations look bad.

Also, on Linux, AMD's OpenGL implementation - which is just Mesa - is very high quality.

Re:Anomalous CPU utilization on Windows build node caused by... by outworlder on Friday July 12, 2019 @02:46PM (#20423272)
> but by being forgiving of code that shouldn't work according to spec

So they are not following spec, and that's a good thing?

Re:Anomalous CPU utilization on Windows build node caused by... by esmi on Friday July 12, 2019 @03:11PM (#20423494)
If you're trying to run a non-conformat application that you are unable or unwilling to modify, then yes. It is a good thing.
Re:Anomalous CPU utilization on Windows build node caused by... by Filligree on Friday July 12, 2019 @01:53PM (#20422774)
Because you simply can't do much ML experimentation on AMD; it lacks the entire CUDA ecosystem. I'm sorely tempted to run two GPUs, but also worried they'll probably clash.
Re:Anomalous CPU utilization on Windows build node caused by... by godelski on Friday July 12, 2019 @04:59PM (#20424430)
I am interested to see ROCm. AMD has the contact for the exascale machines and there's a big push for ML at the DOE. So I hope there's some real competition coming (looks like it's already integrated into pytorch btw)
Re:Anomalous CPU utilization on Windows build node caused by... by badsectoracula on Friday July 12, 2019 @01:49PM (#20422725)
Because Nvidia has faster hardware (assuming you want that) and the best and most complete OpenGL implementation.

At least that is the reason i get Nvidia GPUs.

Re:Anomalous CPU utilization on Windows build node caused by... by godelski on Friday July 12, 2019 @05:13PM (#20424566)
Except Nvidia is selling to me. I use cuda. At the end of the day a higher performing GPU is (MUCH) more important than running displays. There's lots of legacy code using cuda as well, so there's some lock in (AMD is tackling this issue but that's to be seen. We also use data parallel primitives - good for portability between super computers and things with different architectures - for many things but not everything, so when ROCm comes around this may not be an issue at all). But as of right now I'm locked in, at least with my priorities.

So please just stop telling us to get AMDs. That trades a small issue for a bigger one. Nvidia is selling is 90% of what we want and we're annoyed that they just don't care about that other 10%.

Re:Anomalous CPU utilization on Windows build node caused by... by blihp on Friday July 12, 2019 @03:02PM (#20423406)
Because until recently, on Linux AMD's driver story hasn't been good and performance has lagged. The driver situation is improving but it will take time to win people back. It also doesn't help that they don't (yet) have a Ryzen-like story on GPUs.
Re:Anomalous CPU utilization on Windows build node caused by... by Jach on Friday July 12, 2019 @03:20PM (#20423580)
Does the new driver architecture support controlling fan speed yet? I've been on both team green and team red, and not being a purist I have just used their proprietary drivers. It wasn't until AMD shifted to their new driver architecture (with most people suggesting to use the "high quality" open source one that required baking firmware into my kernel (I run Gentoo)) and I had so many issues with both the new open source one and proprietary one that I accelerated my time-to-update-card timeline and went back to NVidia, emerged nvidia-drivers, and have never had a problem since. Nvidia has been rock-solid for me on Linux (even when I first had an old card in 2009-2012 or so) using their proprietary drivers. There's also the continuing fact that while you can get 2 AMDs to match the performance (and cost) of one Nvidia, I'd rather just have the one card every time.
Re:Anomalous CPU utilization on Windows build node caused by... by blihp on Friday July 12, 2019 @03:37PM (#20423720)
Don't know as I'm right there with you using nVidia myself right now. While I'm going to be picking up a new Ryzen-based system soon, AMD's GPU offerings aren't where they need to be for me to shift away from nVidia yet.
Re:Anomalous CPU utilization on Windows build node caused by... by TylerE on Friday July 12, 2019 @01:58PM (#20422826)
Because both times I bought an AMD (ATI at the time) card, it failed prematurely (out of warranty, but < 2 years of life) and the drivers sucked balls.
Re:Anomalous CPU utilization on Windows build node caused by... by wtallis on Friday July 12, 2019 @02:06PM (#20422915)
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.
Re:Anomalous CPU utilization on Windows build node caused by... by mschuster91 on Friday July 12, 2019 @03:15PM (#20423541)
Probably in every place that is not the European Union which mandates 2 year warranties. Rest of the world iirc is 1-year.
Re:Anomalous CPU utilization on Windows build node caused by... by wtallis on Friday July 12, 2019 @07:42PM (#20425501)
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... by TylerE on Friday July 12, 2019 @09:50PM (#20426024)
The situation was much different 5 or 10 years ago.

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

Re:Anomalous CPU utilization on Windows build node caused by... by Avamander on Friday July 12, 2019 @04:11PM (#20424041)
Even on AMD you can have awful problems. The modeset xorg driver froze for me for a month until someone finally told me there's also the radeon xorg driver, awful.
Re:Anomalous CPU utilization on Windows build node caused by... by est31 on Friday July 12, 2019 @01:38PM (#20422584)
May I ask what ROCs is and why is it making Nvidia drivers better?
Re:Anomalous CPU utilization on Windows build node caused by... by lake99 on Friday July 12, 2019 @03:47PM (#20423816)
Not ROCs, it's ROCm. AMD's GPU compute libraries. It won't make NVidia better, but will provide an alternative to those who are stuck with NVidia for doing tensorflow, PyTorch stuff.

https://rocm.github.io/

Re:Anomalous CPU utilization on Windows build node caused by... by chefandy on Wednesday July 17, 2019 @11:01AM (#20460180)
Creating scientific graphics is a much different job than doing graphic design.
Re:Anomalous CPU utilization on Windows build node caused by... by semi-extrinsic on Friday July 12, 2019 @01:29PM (#20422482)
Between Gimp, Inkscape and Krita, what are the things not covered in this domain?
Re:Anomalous CPU utilization on Windows build node caused by... by AJ007 on Friday July 12, 2019 @01:53PM (#20422768)
It’s worth mentioning Blender 2.8 too. This is software people are leaving top tier commercial 3D apps like Maya for because it is better. The stereotype of unfriendly UI and UX in open software is breaking down and does not have to be a given.
Re:Anomalous CPU utilization on Windows build node caused by... by basq on Friday July 12, 2019 @02:53PM (#20423328)
Blender is good for character animation, but it's learning curve is higher and there aren't as many QoL improvements as in other 3d software. 2.8 is a step in the right direction but I still find cinema4d to be much much much faster to get results with for my purposes of motion graphics.
Re:Anomalous CPU utilization on Windows build node caused by... by chefandy on Wednesday July 17, 2019 @11:49AM (#20460752)
Speed really is the crux of the biscuit. It's not like you can't get the same results using FOSS, but the amount of time and effort to do so is significantly increased.
Re:Anomalous CPU utilization on Windows build node caused by... by ctrl-j on Friday July 12, 2019 @02:11PM (#20422967)
For some simple photo manipulation Gimp works - but it seems a lot harder to use. Plus it's missing non-destructive adjustment layers, and the brush engine is nowhere near as advanced as photoshop.

Inkscape is similar - everything is a little harder to do - and there's some basic things that don't seem to be in the application at all. Does Inkscape support multiple artboards yet? What about exporting multiple resolutions without duplicating the assets? The symbol support also was very lackluster when I used it last.

Krita lags horribly every time I've tried to use it.

I like the notion that there are open source replacements for these systems.. and I'd love to drop my $50+ per month subscription - but the alternatives aren't yet equivalents.

Re:Anomalous CPU utilization on Windows build node caused by... by komali2 on Friday July 12, 2019 @02:29PM (#20423114)
You're not wrong, but we all know why it's not better: nobody's paying to make it better, so the only way to get it better is via adoption and a larger community actively trying to make it better.

Basically, yes, it hurts, but maybe try using it more? It's certainly better than nothing, which is what we may have if, I dunno, Adobe collapses or something crazy and all our Photoshop licenses suddenly stop working.

Re:Anomalous CPU utilization on Windows build node caused by... by Avamander on Friday July 12, 2019 @04:13PM (#20424063)
You can use such stuff more if you don't want to be productive, and this is coming from a 100% Linux user for nearly half of my life. Unless you write code then the contributions are basically useless.
Re:Anomalous CPU utilization on Windows build node caused by... by yellowapple on Friday July 12, 2019 @03:12PM (#20423503)
> but it seems a lot harder to use

I actually feel the exact opposite - it's easier to use than Photoshop - but that's probably because I used GIMP before I ever had access to Photoshop.

100% agree about Inkscape, though.

Re:Anomalous CPU utilization on Windows build node caused by... by 4bpp on Friday July 12, 2019 @05:58PM (#20424897)
GIMP: My understanding is that at some point the UI design brahmins at GNOME decided that GTK+ must not support MDI (as in the UI paradigm where you have a container window with subwindows floating around inside it), and moreover the same kind of user interface should be implemented at the top level because a good window manager should be able of keeping an application's windows together. Well, no such window manager ever emerged, and as a result using GIMP is a perpetual search for what workspace a particular tool window disappeared to, or having to fight with it deciding that the minimum size of particular windows (tall toolbars, large viewports) is greater than the 1366x768 of my laptop screen. This is frustrating to the point of unusability.

Krita: Constant random crashes, like seemingly every complex Qt application.

Inkscape: I grew up on CorelDraw so maybe I just have the wrong set of expectations, but the UX is full of papercuts and inexplicable choices. For just one example that annoyed me recently, it seemed completely impossible to get snapping to grids and guidelines to behave; some objects would just refuse to snap to certain targets (different set for each object), and generally the snapping seemed to be based on arbitrary "basepoints" (only one per object; can you change those?) rather than bounding boxes.

(Blender, brought up elsewhere: actually quite good (modulo maybe the confusing refcounting/resource management), once you get on top of the learning curve. I hope 2.8, which I haven't tried yet, hasn't changed this.)

Re:Anomalous CPU utilization on Windows build node caused by... by Razengan on Saturday July 13, 2019 @05:41AM (#20427301)
> GNOME decided that GTK+ must not support MDI (as in the UI paradigm where you have a container window with subwindows floating around inside it), and moreover the same kind of user interface should be implemented at the top level because a good window manager should be able of keeping an application's windows together.

This is what macOS does, and does it well. Aqua/Quartz (is it still called that?) doesn't support (or at least doesn't encourage) MDI either, but unlike Windows it's app-centric instead of document-centric, which can annoy some Windows users when ALL of an app's windows come to front when they click on its icon in the dock.

Re:Anomalous CPU utilization on Windows build node caused by... by johnchristopher on Friday July 12, 2019 @01:43PM (#20422647)
Does gimp feature non-destructive multiple filtering on layers yet ? Photoshop CS2 (and you know why I mention that specific version) from more than ten years ago has it.
Re:Anomalous CPU utilization on Windows build node caused by... by chefandy on Wednesday July 17, 2019 @10:52AM (#20460080)
Using those tools for professional graphics work is like being a software developer and using notepad as your text editor, or being a chef and using a residential electric stove in your restaurant. Sure, it's possible to achieve similar (or in some cases equivalent) results, but it's just not worth the hassle.

Also, when you're making artwork on a deadline, fooling with virtual machines and things like that just doesn't make sense. There are just too many moving parts. Having to deal with layers of technology is a serious impediment to letting your creativity flow.

I first installed Linux off of floppies in the mid-90s on a hand-me-down 486— my distaste for that workflow isn't born from lack of experience or technical knowlege— it's born from the knowledge of the very real consequences of having an overly complicated toolchain when doing time-sensitive work.

Re:Anomalous CPU utilization on Windows build node caused by... by basq on Friday July 12, 2019 @02:49PM (#20423293)
Gimp/inkscape are not drop in replacements for ps/illustrator. Unless your use case is very basic.
Re:Anomalous CPU utilization on Windows build node caused by... by fortran77 on Friday July 12, 2019 @02:40PM (#20423212)
Photoshop, Illustrator, and After Effects? Many people do really need them!
Re:Anomalous CPU utilization on Windows build node caused by... by pkulak on Friday July 12, 2019 @01:39PM (#20422600)
I've gotten way too addicted to DxO. But it runs fine in a VM.

That said, I only use it a couple times a month. If I had to run it professionally, I'm not sure I'd be down.

Re:Anomalous CPU utilization on Windows build node caused by... by Jach on Friday July 12, 2019 @03:13PM (#20423516)
It depends on the software (and associated hardware if you're talking about graphics) of course, but between wine (and its extensions like proton that are successfully handling many AAA games old and new), qemu, and virtualbox, the need for actually having to dual boot from Linux or have a dedicated Windows box grows less and less each year.
Re:Anomalous CPU utilization on Windows build node caused by... by thrax on Friday July 12, 2019 @01:24PM (#20422437)
Just wanted to throw out a plug for photopea.com .. discovered it recently and it handles everything that I, as a programmer ever needed from Photoshop.
Re:Anomalous CPU utilization on Windows build node caused by... by mipmap04 on Friday July 12, 2019 @02:17PM (#20423023)
Woah this is great! Spent about 3 minutes with it, but already like it a lot.
Re:Anomalous CPU utilization on Windows build node caused by... by bduerst on Friday July 12, 2019 @01:26PM (#20422455)
How does it compare to pixlr?
Re:Anomalous CPU utilization on Windows build node caused by... by _eht on Friday July 12, 2019 @01:26PM (#20422453)
What is it specifically you are needing to run? I only ask because I’ve been running Linux for the last 15 years exclusively, in and out of the commercial corporate world, and have yet to feel limited software wise.
Re:Anomalous CPU utilization on Windows build node caused by... by alluro2 on Friday July 12, 2019 @07:12PM (#20425351)
One of the reasons I'm so thrilled with Figma and that it completely covers (and more) what I had to use Sketch for...I'm now seriously entertaining the thought of migrating from Hackintosh (on a laptop) to Linux for my web dev / UXD stuff, and potentially just using KVM / Xen for any rare cases when I'd need OSX...For now, I think I'd just sorely miss Postbox (can anyone recommend a Linux alternative?), that's actually all I can think of...
Re:Anomalous CPU utilization on Windows build node caused by... by fit2rule on Friday July 12, 2019 @01:04PM (#20422269)
Had my Linux machine up and running somewhere since the day Linus announced it on minix-list.

Still though, also have my stack of MacBooks.

Apple becoming a Unix vendor lured me to their hardware, which functions as a terminal server in most regards, for my needs. For everything else, there's a fat Linux machine.

Windows: just, no. Only use it if I get paid to use it.

Re:Anomalous CPU utilization on Windows build node caused by... by noonespecial on Friday July 12, 2019 @03:01PM (#20423397)
It's the apples and mickies I keep on a shelf "just in case".

I pull them out a few times a year for that odd doc or onerous requirement.

Otherwise I've been happy with debian for a decade.

Re:Anomalous CPU utilization on Windows build node caused by... by michaelcampbell on Friday July 12, 2019 @01:15PM (#20422357)
Guess who's on the board of the Linux Foundation?
Re:Anomalous CPU utilization on Windows build node caused by... by _eht on Friday July 12, 2019 @01:26PM (#20422460)
At the platinum level, even.
Re:Anomalous CPU utilization on Windows build node caused by... by msla on Friday July 12, 2019 @03:08PM (#20423461)
> Perhaps we should all keep and maintain a Linux machine in the event that Apple and Microsoft both decide to screw us over.

It's already happened.

Re:Anomalous CPU utilization on Windows build node caused by... by girvo on Friday July 12, 2019 @01:35PM (#20422549)
I have a lot of the same dramas... but then my Windows computer and ecosystem has so many equivalents (in terms of frustration and lost time, more than specifics) that frankly I’m exhausted with computing in general at this point.

Question: what enclosure did you get? I’m thinking of getting the Razer Core X myself, for an AMD card for bootcamp and macOS

Re:Anomalous CPU utilization on Windows build node caused by... by ctrl-j on Friday July 12, 2019 @01:57PM (#20422822)
I got the Razer Core X.

There is an issue where I have to plug it in right after windows starts to boot because the mac tries to disable the integrated graphics if it's plugged in when the laptop boots (which causes windows to not boot). But if you don't plug it in while windows is in the early boot stages then windows doesn't seem to want to identify it. Apparently this is solvable with a custom efi module but I haven't explored that yet.

Otherwise it works solid in windows. Pretty much the same performance as when the card was in my desktop.

Re:Anomalous CPU utilization on Windows build node caused by... by zten on Friday July 12, 2019 @02:49PM (#20423297)
I've recently gone through the eGPU enclosure drama after reading an article linked here. I'm using one of the 2019 refreshes of a MacBook Pro, with a Radeon Pro Vega 20. I bought a Radeon RX 5700 XT at launch this week, paired with a Razer Core X, like you've got. (I can go into more detail, but AMD dGPU + eGPU is a ridiculous battle of knowing which obscure config setting to add to drivers to get them to install [Google for EnableFalcon=true]).

rEFInd successfully gets Windows to find the Intel UHD integrated graphics, so that's good. That let me uninstall the Vega 20's drivers and disable it entirely.

Even then, I still don't boot with the enclosure attached - it seems to ignore its presence? Unplugging and plugging it back in triggers Windows to go find all of the hardware, and then I have to wait 30 seconds while things grind to a halt as devices install. I'm eagerly awaiting AMD Navi 10 driver support in OS X, which I suspect will come around since people have found the names in kernel extension strings earlier this year.

Re:Anomalous CPU utilization on Windows build node caused by... by emsy on Friday July 12, 2019 @01:04PM (#20422267)
I agree that the lack of hardware choice (or different "opinions" like a matte screen or smaller phones) is probably Apple's biggest flaw. But they're on a different level. One is an inconvenience, the other is utter disrespect of your privacy.
Re:Anomalous CPU utilization on Windows build node caused by... by Razengan on Friday July 12, 2019 @01:22PM (#20422424)
> like a matte screen

By the way, if you need a matte screen, third-party screen filters can help there.

I got a Kensington “Privacy Guard” that attaches magnetically and can be flipped around between the gloss or matte side. It may be slightly blurry at times but after getting comfortable with the reduction in glare and reflections, I dislike going back to the default Mac screens.

https://www.apple.com/shop/product/HLXJ2ZM/A/kensington-mp15...

Re:Anomalous CPU utilization on Windows build node caused by... by kofejnik on Friday July 12, 2019 @01:53PM (#20422767)
>> lack of hardware choice (or different "opinions" like a matte screen or smaller phones) is probably Apple's biggest flaw

it's a strength, not a flaw

choice fatigue is real, just go dell.com and try to pick a laptop

Re:Anomalous CPU utilization on Windows build node caused by... by ctrl-j on Friday July 12, 2019 @02:17PM (#20423016)
Apple has a lot of inconveniences that pile up. I want to like their ecosystem to the point where I dropped thousands of dollars to be here - but there's SO many day to day issues that I can't stay. My next laptop will most likely be a linux laptop and leaving my production workflows on windows on my desktops.

If they would pay attention to the usability of their machines they'd be amazing. But I can't afford pay thousands of dollars to work slower.

Re:Anomalous CPU utilization on Windows build node caused by... by longcommonname on Friday July 12, 2019 @01:29PM (#20422488)
How long do you think a major OS should have 32 bit support? Everything cant be supported forever.
Re:Anomalous CPU utilization on Windows build node caused by... by AnIdiotOnTheNet on Friday July 12, 2019 @01:31PM (#20422517)
Why not? We live in a world where the latest processor from Intel still boots into 16 bit real mode, and we have emulators and virtual machines.
Re:Anomalous CPU utilization on Windows build node caused by... by ryanianian on Friday July 12, 2019 @01:34PM (#20422538)
There is a real cost to supporting old architectures and associated risk in telling users they can run production workloads on them.
Re:Anomalous CPU utilization on Windows build node caused by... by badsectoracula on Friday July 12, 2019 @01:50PM (#20422736)
There is also a real cost to dropping support for software working perfectly fine.
Re:Anomalous CPU utilization on Windows build node caused by... by asveikau on Friday July 12, 2019 @03:15PM (#20423537)
When a big company explains away how they are not doing something because of engineering resource constraints, put your skeptic's hat on, it's likely an exaggeration.
Re:Anomalous CPU utilization on Windows build node caused by... by Razengan on Friday July 12, 2019 @01:36PM (#20422553)
You can still use emulators on macOS Catalina (the version that drops 32-bit support.)
Re:Anomalous CPU utilization on Windows build node caused by... by mappu on Friday July 12, 2019 @07:33PM (#20425468)
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.
Re:Anomalous CPU utilization on Windows build node caused by... by wtallis on Friday July 12, 2019 @07:50PM (#20425544)
> 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... by usbseeker on Friday July 12, 2019 @01:36PM (#20422558)
Did you start experiencing the random auto double click bug on your logitech yet?
Re:Anomalous CPU utilization on Windows build node caused by... by ctrl-j on Friday July 12, 2019 @01:58PM (#20422837)
Nope, I've never had that problem with any of the Logitech mice I've owned. Which model has that issue?
Re:Anomalous CPU utilization on Windows build node caused by... by IloveHN84 on Friday July 12, 2019 @03:07PM (#20423459)
What about the case of Zoom? Not that privacy focused
Re:Anomalous CPU utilization on Windows build node caused by... by hnarn on Friday July 12, 2019 @01:25PM (#20422441)
> Things like these is why most Mac converts never want to return to Windows.

This sounds like a false dichotomy. There are, of course, other and cheaper ways of getting out of using Windows than buying an Apple computer.

Re:Anomalous CPU utilization on Windows build node caused by... by Razengan on Friday July 12, 2019 @01:37PM (#20422575)
Yes, but in all the recent Touch Bar hatewagon pile-ons, many commenters try to suggest moving to this or that Windows laptop, without understanding that it is Windows we want to avoid in the first place.
Re:Anomalous CPU utilization on Windows build node caused by... by damnyou on Friday July 12, 2019 @01:38PM (#20422589)
The discussion is about a Windows build node — you can't even run MacOS on typical datacenter hardware!

These are just the incentives that capitalism creates. Microsoft's abusive ad practices, Apple's abusive hardware lock in. C'est la vie. The only stack that isn't structurally abusive to users is Linux, but of course it's Linux.

Re:Anomalous CPU utilization on Windows build node caused by... by kazinator on Friday July 12, 2019 @02:46PM (#20423276)
All my exes live in ... Win32 DLL's: CreateThreadEx, CreateFileEx, WaitForSingleObjectEx, ...
Re:Anomalous CPU utilization on Windows build node caused by... by sdinsn on Friday July 12, 2019 @03:56PM (#20423903)
No, it's not. This is a build node, not a consumer PC.
Re:Anomalous CPU utilization on Windows build node caused by... by m463 on Friday July 12, 2019 @03:56PM (#20423902)
Apple does telemetry as well.

I think the endgame you're looking for is probably Linux-based.

Re:Anomalous CPU utilization on Windows build node caused by... by arghwhat on Friday July 12, 2019 @03:03PM (#20423412)
laughs in Linux
Re:Anomalous CPU utilization on Windows build node caused by... by yellowapple on Friday July 12, 2019 @03:14PM (#20423524)
chortles in BSD
Re:Anomalous CPU utilization on Windows build node caused by... by DoofusOfDeath on Friday July 12, 2019 @03:40PM (#20423748)
snickers while writing group-theory proofs on a blackboard