I find the new newsletter easy to read and informative about what's going on with Stardock. I've been around since the OS/2 days (I went to Windows 2000 to be able to synch my Palm Pilot in 2001).
I would like to hear about your plans for Object Dock under Windows 10. I'm still using it, because it's the gateway to all of may databases (via a large tabbed dock) and I use the expanding dock to open and switch to new folders, e-mail, Firefox, and IE, and I like the AccuWeather, recycle bin, and clock. When Windows won't pass the foreground to Object Dock, I either just wait or, if it's there, switch to my app with the mini-icon on the taskbar.
I recently looked at the Forums to see what was up with Object Dock and saw that declared support for OD under W10 was withdrawn a year ago.
Windows never has been as good as OS/2 at multitasking, which always puzzled me. Microsoft's OS/2 NT became Windows NT, and Windows 2000/XP/7/8.x/10 are all updates of that kernel - but they never did achieve seamless multitasking. I run with 8 cores and Windows 10 can't give me response to the mouse if it's saving to the boot partition. It's like, maybe the kernel can do it but there is some legacy Windows 3.x/95/98/MillineumEdition Program Manager code in the current Windows 10 desktop environment.
I've tried giving the ObjectDoc.exe process priority Above Normal but that doesn't help. I selected that process because its CPU usage increases when I mouse over the object dock. I didn't try elevating the priority of the 64-bit process, ObjectDockTray.exe.
Windows NT and successors, like OS/2, allow extensions to the desktop environment, and Stardock is the leading source of utilities that provide these extensions. Windows 10 is not so good at making some of these hooks work as earlier versions, I get that. But a year is a long time, and Object Dock is a huge thing for Stardock. Between Fences and Object Dock, I have my OS/2 user interface, albeit with no SOM.
So, what is happening with Object Dock for Windows 10?