I many times read that if you keep updating your website you may consider an interpreted language to be better for this case. I want to understand why interpreted server side language is better if I keep updating my site (such as adding new features or change some functionality).?
The people who say that are probably referring to the fact that you don't have to rebuild, repackage, and redeploy an application consisting of an interpreted language each time you make a change. For instance, if you need to make a small change to an application written in an interpreted language, you can simply change the source code and replace the changed files on the production server with the updated versions without the need to complete the build steps I mentioned above.
This may be convenient at times, but it's not enough of a reason to choose an interpreted language over a compiled one. It's a pretty insignificant detail in the grand scheme of things, especially with the efficiency provided by build automation tools.
Before choosing one or the other, make sure you understand the differences between the two.
This doesn't make sense. There is no such thing as an interpreted language. Nor is there such a thing as a compiled language. A programming language is an abstract concept. A programming language is a set of mathematical rules and definitions. Programming languages aren't compiled or interpreted, they just are.
Compilation and interpretation aren't properties of a programming language, they are properties of, well, a compiler or an interpreter (duh). Every language can be implemented by a compiler and an interpreter, and most languages have both compiled and interpreted implementations. In fact, the majority of modern language implementations utilize both an interpreter and a compiler in the same execution engine for maximum performance.
If English were a typed language, the term interpreted language couldn't even exist, it would be a type error.