The best thing about bash is it is on almost all 'nix like systems. And that is why I learned vi. Basically for 'personal portability' and being able to help others maintain systems they already know.
Computer languages has been a passion (some I still can't get my head around, like APL or FORTH). Some are of selective use LISP and SNOBOL for examples (but lots of things are LISP based - often below the level or end user cognisance). There are the c's of the world and all the OO deviants thereof, some vendor specific, some not. I agree with David, if there is a difference in the use of the languages that makes a difference, then it should be used. Sometimes there are overriding reasons that keep us from using the 'best' selection ... long term maintainability, contract purposes, company standards, are the ones that easily come to mind (I have run into all of those). I am sure there are others as well. I have a brother that worked on DOD project that 'required' ADA be used. So they used it, and shelled out to run the JAVA application for the real work (mainly because the historical project was JAVA based and swapping languages if a half million lines of taxpayer paid for code had already been written didn't makes sense). I also say some of this from real world commercial experience. Language personally use over the years PL/1, BAL (assembler language), machine language for various architectures, SQL (and other relational and non-relational based languages), EasyOut (natural language parsed database), RPG, FORTRAN, COBOL, APL, LISP, SNOBOL (string processing), EASYTRIEVE (A product from CA now), PERL, C, JCL (job control language of various dialects), and various commercial scripting languages. Also several more special purpose and general purpose languages I am not remembering.
_______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
