On Wed, May 30, 2018 at 9:51 AM, IL Ka <[email protected]> wrote: > There is no reason to use C for "onetime tools" except cases when no other > API exist.
Or when the tool would be running long enough that the performance difference matters. Also, Javascript/Perl/Python/Ruby/shell all tend to be lousy at dealing with anything where control over timing is the overriding issue. Or when your target environment needs you to be miserly with your memory use. Or, for practice. Or, sometimes, just because there are some things where C is more convenient and comprehensible. And maybe for things I haven't thought of. But, other than that, yes. That said, to address the question raised by the original poster: these days, for me, it's been mostly php, perl, shell and sql, with a few makefiles thrown in for good measure. Oh, and a bit of javascript and a bit of svg. A good bit of that is a reflection of my current job, though. [I started learning php last december, for example - and php 7 is almost a reasonable language, unlike previous versions.] If I was working on more practical issues, I would probably focus on C and/or an assembly language (or something close to that - maybe a forth, for example). Thanks, -- Raul
