Why the hell am I so into batch files nowdays?
Posted: Tue Apr 09, 2019 10:45 pm
Some of you may had noticed; I've been posting things with batch files, and doing much of nothing else. Well, me using Windows has a lot to do with it (otherwise I would probably be doing shell scripts on Linux), but also with how many unique operations are required to apply (and undo) certain items, it gets real tedious, real fast to do a lot of what I enjoy by hand.
I like options, I like choices, but most of all I like them to be relatively easy. That's where the batch scripts really come in; it's easier for the end user to have a script where they can wax on, wax off in seconds rather than minutes, and the way I prefer to do things; with links, links and more links makes it so there aren't duplicate files taking up your system's free space (a matter of contention with the popularity of lower-capacity SSD boot media not paired with larger media for storage).
For some larger projects, like the Tsunami Visual arcade skins for stock cars the batch script comes in real handy because 215 individual files, five per across twenty-three different directories have to be managed. And if you don't like it? Then what? So being able to apply them (and later, remove them) with a batch script makes using them dead-easy.
...Too easy. Even though my scripts are 100% safe and don't download anything for the end-user, and I drone on about what my stuff does to imply some degree of confidence my work is safe for everyone to use, I still encourage moderators to put into serious regard the safety of scripts by anyone, including myself. The same script I use which coaches the user into pushing buttons and automating things can also be used for evil, and I encourage vigilance for everyone when dealing with any kind of automation routine. Read the code. If it isn't easy to understand and it appears to download things from the Internet using unfamiliar addresses, don't execute it, rather report it.
Aside from that, everything I've been submitting puts the end-user first, so long they understand it and are willing to put a touch of work into... making it work. Which is a good thing because then they can read the code and see how it works. If they don't like it, they don't have to use it. But I provide the option for you because I know how people are. If it's the least bit inconvenient, a lot of you will just ignore it and I try to exert as little inconvenience to the end-user at the best of my ability.
I like options, I like choices, but most of all I like them to be relatively easy. That's where the batch scripts really come in; it's easier for the end user to have a script where they can wax on, wax off in seconds rather than minutes, and the way I prefer to do things; with links, links and more links makes it so there aren't duplicate files taking up your system's free space (a matter of contention with the popularity of lower-capacity SSD boot media not paired with larger media for storage).
For some larger projects, like the Tsunami Visual arcade skins for stock cars the batch script comes in real handy because 215 individual files, five per across twenty-three different directories have to be managed. And if you don't like it? Then what? So being able to apply them (and later, remove them) with a batch script makes using them dead-easy.
...Too easy. Even though my scripts are 100% safe and don't download anything for the end-user, and I drone on about what my stuff does to imply some degree of confidence my work is safe for everyone to use, I still encourage moderators to put into serious regard the safety of scripts by anyone, including myself. The same script I use which coaches the user into pushing buttons and automating things can also be used for evil, and I encourage vigilance for everyone when dealing with any kind of automation routine. Read the code. If it isn't easy to understand and it appears to download things from the Internet using unfamiliar addresses, don't execute it, rather report it.
Aside from that, everything I've been submitting puts the end-user first, so long they understand it and are willing to put a touch of work into... making it work. Which is a good thing because then they can read the code and see how it works. If they don't like it, they don't have to use it. But I provide the option for you because I know how people are. If it's the least bit inconvenient, a lot of you will just ignore it and I try to exert as little inconvenience to the end-user at the best of my ability.