Do you prefer compiled or scripted languages?

Question

Since this is wide community using all kind of different technologies, it seems like appropriate place to ask this.

Do you like to compile or do you prefer scripting?

I ask this because I tend to program things in small scripting languages with chosen modules I actually need (like Lua, Awk, AutoHotKey ... ) instead of mainstream languages with full blown non-portable IDEs and big one-size-fits-all libraries where every little change require to load and recompile the project.

I like the ability that the only tool I actually need to change/fix/update the project is any editor available on any system I happen to run the script (and of course, the interpreter which is single executable that I can either carry with me or download it instantly from Internet and just save it on disk without any kind of installation procedure).

I also feel good to know that anybody wanting to update the project doesn't require anything else but the editor - no notorious compilation issues, dependency problems etc., and that anybody that doesn't like the button I put there, can open the file and put it wherever he wants or even delete it in a matter of minutes.

I ask this because I noticed that there are some programmers that tend to think that anything that isn't native executable isn't good enough. I even remember one post on the forum where I keep one of my open source applications - another programmer said "Good app, but it isn't .exe"

Answer 1

I am a fan of any tehcnology that allows me to find bugs as early as possible in the development cycle. As such I tend to be more of a fan of projects that compile vs. are interpreted. Static compilation is a tool you can use to force error detection into your code at a very early stage.

Answer 2

I like to compile. This process gives me information about what is wrong in my syntax, type mismatches and so on. Also compiling makes most files unredable which is great for creating software that isn't opensource. Last but not least compiling makes programs run faster.

Answer 3

Scripting is quick for development, etc. But normally it's not as fast as compiled code. So that is the trade-off

Answer 4

Without compile time, when would you have time for Stack Overflow (or wheely chair hockey)?

Answer 5

Compile gives you the benefit of compile-time errors. Scripting doesn't have these, which means that you have to have sufficient tests to get enough run-time errors. Compiling is just easier.

Answer 6

I wouldn't say that what you are saying is universally true. Take PHP for example. It's a scripting langauge. But there' hundreds of different modules for it. Something that may work on your computer may not work on another computer. Also, there's still configuration files (php.ini) and changing the configuration can affect if your program runs the same on different computers.