koitsu wrote:
Back in the day (90s), we used "whatever came with the system". Installing more crap on the system was highly discouraged. For example, doing table generation on the Apple IIGS, we'd just use Applesoft BASIC to generate all the
.db statements and put them in a file. On x86 systems, we'd use QBASIC or Turbo Pascal (if we had it installed) for the same task.
On present-day Windows systems, you could use
JScript or
VBScript (both come wth the base OS, so no installation needed, both usable via
cscript.exe) which should be enough (IMO) to do simple/complex math and generate all the stuff you need. It's remarkable how these two things often get neglected/forgotten.
On UNIX/Linux systems, a simple programming language of your choice would likely be necessary. Many Linux distros include Perl or Python by default, and you could even do it in bash (albeit painfully, depending on how complex the math is) if needed.
While I agree with you ideally, I think it's ultimately better to use something you know well (even if it needs an install) rather than using some obscure language just because it is here with the system.
For instance if someone is extremely familiar with Python, I understand why they'd want to loose 1 minute to download and install python instead of using one hour to figure out how to generate .db statements in a file using JScript or VBScript.
Personally I use C all the time at work so that is the major language I'd use for everything. I know it is a terrible language, especially for this particular application, and there is many more adapted languages out there, but in the end I'd save time doing it in C just because I am so used to using it. Even if I wanted to use the C++ extensions I'd loose time because I'd have to look up for how you use std::cout, because I don't remember, so I end up using C anyways.
When I was a student I used to using java, now I'd never want to code in this language ever again, because it is absolutely awful and even worse than C in all aspects, cumulating C's problems with other problems made up especially for it. The only great thing about java is that it detects the buffer overflows problem instead of crashing or making segfaults. Other scripting languages such as Perl looks awesome, but I only used those a couple of times to try something, and it'd take forever to remember how to use Perl to do some basic operation. I had no idea JScript and VScript even existed. I though Java Script was only for web pages, I am surprised you could do a non-web application with it. Although if you use Java Script so often at work, I pefectly understand why you'd want to use this for an application where JavaScript was not supposed to be adapted, just to win time.
Sorry to have gotten completely off-topic.