That's the default. There are, however, many other interesting computational environments you might want to use, which Haskell let's you enable: controlled, strict evaluation (the use of seq and rnf); local mutable state (the `ST` monad); mutable state with transactions and rollbacks (the `STM` monad); arbitrary effects on the world (the `IO` monad); computations with backtracking (the `Logic` monad); deterministic parallelism with shared state (the `Par` monad) and so on.
Just remember: in Haskell, persistent and immutable is the default. You turn on other environments as you need them.
Why is it the default? So-called "purely functional" programming is a rich, safe, environment for most programming problems, and makes lots of nice things possible, such as trivial parallelization, automatic thread safety, proofs on code via simple equational reasoning, and powerful optimizations.
Haskell is the only widely used language that uses lazy evaluation by default. This has historically lead to confusion and difficulties with reasoning about time and space, particularly when a programmer is coming from a strict language.
Why do we care about laziness by default? Like purity, it adds power and expressiveness.
The series require Haskell knowledge but this summary is fairly readable if you have a good grounding on programming language theory and implementation.
Just remember: in Haskell, persistent and immutable is the default. You turn on other environments as you need them.
Why is it the default? So-called "purely functional" programming is a rich, safe, environment for most programming problems, and makes lots of nice things possible, such as trivial parallelization, automatic thread safety, proofs on code via simple equational reasoning, and powerful optimizations.