Well, all I know is, I have an FX-8350 (@ stock 4.0 GHz), 24 GB of RAM, an RX 560 (4GB) (latest drivers), and even at the lowest performance settings, with only one QuickLaunch dock, ObjectDock is sluggish to respond when moused over. Now, granted, I do have several Stacks, and a fair few icons on the dock, but RocketDock, which is what I used before I got ObjectDock, never had any of those issues, even with the same icon and docklet load. And it was freeware, not to mention, running off of a mechanical hard disk. The reason I chose to buy ObjectDock in the first place is that it offered several features that RocketDock didn't; among which are icon reflections and a built-in weather docklet (which I've come to find out doesn't even work anymore). But it's not just that that I find as integral to the 'subpar' experience; it's the fact that there is an issue (the ApplicationHostFrame.exe background process being pegged as a running foreground program, and therefore perpetually 'running' on the dock) that has been known to exist since 2015, and still has yet to be rectified. I am running the latest downloadable version of ObjectDock from the StarDock website, and this 3-year-old issue is still present. Back in 2015 the developers considered Windows 10 a 'beta OS', which, at that point, they were justified in their classification, and they chose to leave that issue as it was. It's now three years later, and they still haven't fixed it. They've had plenty of time to do so, so it's not an issue of Windows 10 being too new. StarDock clearly has support in applications for Windows 10, Start10 is concrete proof of that, so why ObjectDock was left by the wayside in that respect remains a mystery to me. ObjectDock works on Windows 10, true enough, but its use on Windows 10 is not officially supported by StarDock. I've seen this actually posted by one of the StarDock team on at least a couple of occasions. And according to the 'StarDock Software and Windows 10' forum post, ObjectDock is listed as 'No' under the 'Compatible?' heading. That was posted in 2016, but there's been no official update that I'm aware of that has addressed any of the issues that had arisen with Windows 10 that have been reported.