• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Whats the difference bewteen scripting and programming?

In programming you tell the computer to do something.
In scripting you tell the computer to do something.
In screaming at the monitor while shaking your fist at troll threads you tell the computer to do something.
 
scripting you write code for an existing program for it to execute.
Programming you write code and compile it into an executable, generally.
 
I can't do either, but my understanding is that in programming you're doing everything yourself and in scripting you're plugging in bits of code into a program that other people devised for specific tasks.
 
scripting = mall security guard
programming = police officer
lg-go-away-tshirt.jpg
 
Whats the difference bewteen scripting and programming?

Scripting is interpreted at run time, and is synonymous with a "macro"; it instructs the computer to perform actions based on applications and tools already present on the system, and interacts with resources at the user level.

Programming generally results in compiled code, it instructs the processor to perform operations and interact with resources at the machine level.

The unfortunate side effect of high level languages such as .NET flavors and Java, is that "programmers" who are introduced into programming at this level actually don't know how to program. The industry is in a really sad state right now.
 
there are programming languages that are run by interpreters
http://en.wikipedia.org/wiki/Interpreted_language
Interpreted language is a programming language in which programs are 'indirectly' executed ("interpreted") by an interpreter program. This can be contrasted with a compiled language which is converted into machine code and then 'directly' executed by the host CPU. Theoretically, any language may be compiled or interpreted, so this designation is applied purely because of common implementation practice and not some essential property of a language. Indeed, for some programming languages, there is little performance difference between an interpretive- or compiled-based approach to their implementation.
Many languages have been implemented using both compilers and interpreters, including BASIC, C, Lisp, Pascal, and Python. While Java is translated to a form that is intended to be interpreted, just-in-time compilation is often used to generate machine code. The Microsoft .NET Framework languages always compile to Common Intermediate Language (CIL) which is then just-in-time compiled into native machine code. Many Lisp implementations can freely mix interpreted and compiled code. These implementations also use a compiler that can translate arbitrary source code at runtime to machine code.

so the answer is:

'programmers' call computer code 'programming'
engineers or administrators call computer code 'scripting'

it is basically an elitist thing, 'programmers' think they are better than everybody else
someone that writes a 'script' just want to get the job done and go back to neffing/playing WoW/hacking something, etc etc

also, if the code is part of a project, i.e. a project manager/budget is involved, then the code is 'programming'
if the code is part of ongoing operations/maintenance activity/there is no chance to climb the corporate ladder from the use of the code, then it is scripting
 
there are programming languages that are run by interpreters
http://en.wikipedia.org/wiki/Interpreted_language


so the answer is:

'programmers' call computer code 'programming'
engineers or administrators call computer code 'scripting'

it is basically an elitist thing, 'programmers' think they are better than everybody else
someone that writes a 'script' just want to get the job done and go back to neffing/playing WoW/hacking something, etc etc

also, if the code is part of a project, i.e. a project manager/budget is involved, then the code is 'programming'
if the code is part of ongoing operations/maintenance activity/there is no chance to climb the corporate ladder from the use of the code, then it is scripting

all i got from your post is that you have absolutely no idea wtf you are talking about.
 
The unfortunate side effect of high level languages such as .NET flavors and Java, is that "programmers" who are introduced into programming at this level actually don't know how to program. The industry is in a really sad state right now.

Actually, there's much more demand for these "non-programmer programmers" (not that I condone the term) and little demand for the others. That's not why the industry is in a sad state - the industry needs what it needs. It's in a sad state because the market is meeting this demand with fresh-off-the-boat "developers" from India (with masters degrees from degree mills in India) who were taught to solve a problem by bridging A and B using the shortest possible line, damning scalability and reusability. They're not taught how to write maintainable code or instilled with good coding values (readability, etc). Their mentality is "slam it through as fast as possible... variable 1 will be called a, variable 2 will be b, etc. If it compiles it's done."

It sounds racist/whatever, but I'm just describing what I've seen over the past decade+ as a developer, architect, and manager.
 
Last edited:
The unfortunate side effect of high level languages such as .NET flavors and Java, is that "programmers" who are introduced into programming at this level actually don't know how to program. The industry is in a really sad state right now.
Succinctly: Scripting is for kiddies.
 
lol, i'm buying that.
I have seen a dozen jobs replaced by a handful of code in a script. It's odd seeing that, total success for the IT guy who did it but the reality is people were out of work because of it.

If I coded more I would totally own that shirt. :sneaky:
 
The unfortunate side effect of high level languages such as .NET flavors and Java, is that "programmers" who are introduced into programming at this level actually don't know how to program. The industry is in a really sad state right now.

better go back to punch cards then :colbert:
 
From a relatively code-savvy non-programmer's perspective:

Scripting is (in general) Programming Lite™.

Programmers like to think they're building stuff from scratch, but 99% of them are still working within a framework someone else built (so not REALLY from scratch). If you're depending on a compiler to make your application executable, then I don't see a huge difference except in the size of your project and the complexity of your toolset.

/feedingthetrolls
 
The unfortunate side effect of high level languages such as .NET flavors and Java, is that "programmers" who are introduced into programming at this level actually don't know how to program. The industry is in a really sad state right now.

Right, because everything needs to be written in ASM... 🙄
 
If I've got a simple task to do (eg the text-file-of-URLS example) then I knock it up in shell script. By the time that simple task has feature-creeped up to more than 20 lines I start to wish I'd written it in Perl. So I rewrite. By the time that Perl script has crept up to more than 200 lines I start to wish it was written in Python. So I rewrite. By the time that Python script has crept up to 2000 lines I start to wish I'd farmed the job out to a team of programmers, and I give up caring what language its written in and make them do it as a web service. Then I write a small shell script to call their web service. When that shell script has feature-creeped up to more than 20 lines...
 
Back
Top