Sarnold March 2005 Purpose of this page : tell how different programming styles are possible with Tcl, and how it saves headaches, rather than just tell someone : Tcling is fun, because you won't be believed until you show what makes it possible.
And IMHO, programming is too serious to be fun, even if the programmer often searches the Holy Grail of the languages. The discussion is open.
Tcl makes it possible, with a common style, and even with some Radical language modifications. It is well known to reduce side-effects. Maybe would it reduce the size of your scripts.
TODO : explain where functional programming is obviously needed or wished
The choice is here : many OO extensions are available. It helps you to structure your code , and doesn't need wasteful learning. There are good tutorials, and it is, in most cases, not boring to write some classes.
When you have lots of business logic, OOP will be a strong choice.
TODO : add links to OOP on the wiki
After all, you can get the job done with the basic style, with the help of Introspection. For small scripts, you won't need a complete knowledge of the commands (memoizing manual pages).
TODO : explain why scripts written in a regular style are easy to understand, and finally to maintain
There are many ways to do things dynamically, creating procs at runtime, treating variables as strings, and so on. You may realize that a functionality is done in 10 lines, where in imperative programming it would take ten times more.
'More than one way to do that !
This is common in many languages, but much more in Tcl.