Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
To be frank, I think that's mostly just language snobbery at work. Much like the derision that BASIC tended to get from some quarters in the past. If you're having fun, then good on you, just ignore the nay-sayers.
Whether something gets called a script or program seems mostly down to common convention and little more than that:
sed, awk, expect, shell, perl, python: script
BASIC, Pascal, C, C++, Java, etc: program.
If you try and come up with some sort of hard criteria for a distinction you'll just find yourself with lots of exceptions to the rule, so best not to even try. Just have fun coding and don't worry about it.
I couldn't agree more, aslong as it does what you need it too (in the most elegant way possible) than that's all that matters.. Having fun is a side benefit.
Distribution: Debian testing/sid; OpenSuSE; Fedora; Mint
Posts: 5,524
Rep:
I must make note that for system administration tasks the shell works pretty well, because the programs needed already exist on the system. But if you're writing an application program, like the thousands of packages in any distro, you're going to use a compiled language, preferably oo.
No one can write serious programs that run efficiently using a script.
Some programming languages are non-procedural, such as Prolog. (If you're itching to solve Rubik's Cube, or a logic puzzle, or a Sudoku puzzle, and you don't know how to write a procedure to do that ... Prolog – especially gprolog – is your friend.)
Yeah... I had to take Scheme (a variation of Lisp) in college, I absolutely HATED it, the only computer class I really had trouble in. Assembly language was a piece of cake.
Whether something gets called a script or program seems mostly down to common convention and little more than that:
sed, awk, expect, shell, perl, python: script
BASIC, Pascal, C, C++, Java, etc: program.
I would put Perl and Python into the actual programming language category. To my mind, scripting languages rely mainly on launching other programs to do their work, while programming languages do most of their work with built-in functions or importable libraries.
I tend to use bash scripts only for starting up or shutting down either the system or other, large programs such as a database like ORACLE that takes many steps. Not to do real work.
Programming languages do the hard work themselves.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.