Re: JSMeter10
Posted: July 4th, 2021, 9:04 am
Thanks , I get all that. I think it's my misunderstanding. I dislike installers of any kind and it's extremely rare that I use one. They just put stuff anywhere without users knowing where it's going. I'm talking general app here, not Rainmeter.
So when it came to Rainmeter, I again had the same issue. Not knowing what's installed or where. Let's say I install a couple of skins but it installs plugins without me knowing, they're left there and I don't even know it.
Let's take the issue of apps sharing resources. Many times when I used to install apps via their installer packages, they go all over the system, but the problem arises when you're asked upon uninstallation whether to keep certain dependencies as other apps may use it. You're left with junk if not, or broken apps if there is.
Essentially, it's about organisation preferences. But single skins have no need to use the resource folder and imho, shouldn't. Suites, I can now understand, they are like a self contained set of skins. Let's say a skin uses #@#fonts, why? Why not just use fonts? It serves the same purpose. If all the resource files are just simply placed in the resource folder, that's when it can potentially become an issue.
I know none of you will see my point of view so I'll just leave it at that. Apologies if I came across the wrong way, I don't mean to sound antagonistic, just trying to get a point across that shared resources aren't always a good thing. Probably I'm just a special case!
So when it came to Rainmeter, I again had the same issue. Not knowing what's installed or where. Let's say I install a couple of skins but it installs plugins without me knowing, they're left there and I don't even know it.
Let's take the issue of apps sharing resources. Many times when I used to install apps via their installer packages, they go all over the system, but the problem arises when you're asked upon uninstallation whether to keep certain dependencies as other apps may use it. You're left with junk if not, or broken apps if there is.
Essentially, it's about organisation preferences. But single skins have no need to use the resource folder and imho, shouldn't. Suites, I can now understand, they are like a self contained set of skins. Let's say a skin uses #@#fonts, why? Why not just use fonts? It serves the same purpose. If all the resource files are just simply placed in the resource folder, that's when it can potentially become an issue.
I know none of you will see my point of view so I'll just leave it at that. Apologies if I came across the wrong way, I don't mean to sound antagonistic, just trying to get a point across that shared resources aren't always a good thing. Probably I'm just a special case!