There is no way in hell I'm trying it on my production system. I had to start in safe mode and do some heavy repair to get back.
If you had to do heavy repair than the problem wasn't surely caused by my Aero Glass. This software does not do any system modification except creating scheduled task to inject DLL on startup. This DLL injection can be easily skipped by holding CTRL key or scheduled task can be removed in safe mode.
The reason we do not ship a similar feature is we will not ship something we know will break each time certain files in the OS get updates and then have to wait on fixing it until Microsoft release debugging symbols. I.e. we will not ship anything which assumes hardcoded memory addresses.
In fact, it is not problem at all, because the utility does not modify any system file and it is able to find where to inject the specific code (memory addresses are not hardcoded). This locations almost don't change at all. Currently, it changed only between W8 --> W8.1 --> W8.1 Update1, thus the WindowBlinds suffer from the same problem, because they need update very often between several Windows versions.
And at the end, from my observation, WindowBlinds also injects its DLL by using undocumented API function which can be changed in any OS update and WindowFX hooks DWM's Direct3D device, the same technique as used in my Aero Glass [e digicons][/e]
I have not reverse engineered Aero Glass, but have a good idea of how it would function and I seem to recall seeing discussion of at least the beta using fixed offsets into dlls in order to patch internal functions. If that isn't the case I apologise.
For our purposes we cannot realistically ship anything which is guaranteed to break with the next service pack (you suggest it changes every single major update so far), that's the key difference between paid for and free software. If we take someones money we need to be reasonably sure that if it were to break for any reason that we could fix it even if the OS PDB symbols are not available at the time. Based on the comment that there are two versions, one for 8 and one for 8.1, it suggests each version of the OS is having to have a custom version, but perhaps this is inaccurate.
I ought to stress I have nothing against the product and you should be happy we are currently uncomfortable with shipping something like that. I have to confess other than loading it up to see if I could make Start8 detect it and so enable blurred backgrounds on the Start8 menu, I have not used it and unfortunately in that case there was no easy way to detect it. If this has changed please do let me know so I can make Start8 aware.
Other than the issue with the 64 bit version of Windows a few months ago where a previously unnoticed bug got exposed in WindowBlinds, you should not require an update of WindowBlinds in order to work on a new update of an OS. You do need new versions for each major version (so Win7->Win8), but that's expected and reasonable to customers. On occasion there are some minor visual issues that come in due to new OS enhancements which need skinning, but there should not stop the OS working correctly with the older version and we aim to update the product quickly and again well before any debug symbols would be released.
We think carefully about every technique we use to determine if we feel it may cause us support problems down the line. If it is considered too risky we simply do not use it. That's not to say we are perfect, but the things you mention are proven to be reliable and sometimes we may be aware of things that are not public knowledge.