haskell-lectures/VL1/content/VL1_why_haskell5.tex

12 lines
967 B
TeX

Unfortunately, with java we:
\begin{itemizep}
\item now got even more states to keep track of (intellectual complexity?)
\item have clouded the program flow... it's now about object-interaction with their explicit and implicit states and because of the increase of indirection, it might get even harder to do actual abstraction
\item still have \textbf{side effects} everywhere: one object changes the state of another and vice versa, may arbitrarily write to the hard drive, do kernel calls or launch a missile
\end{itemizep}
\slidep
Some parts of the implicit state machine have been made explicit by modelling classes, but it's still there and we have to deal with it, because we are modelling everything around states. Wouldn't it be nice if we could just forget about the global state machine? Maybe there is even a way to remove side effects and have more "predictability"?
\slidep
\vspace{\baselineskip}
\\
We are lucky. There is. It's called \textbf{Haskell}.