\section{Discussion}
\todo{class based shallow doesn't have multiple backend support}
-\todo{slow client software because of intepretation}
+\todo{slow client software because of interpretation}
\todo{What happens if a device dies? Task resending, add to handshake}
option and exchanged during the handshake so that the server knows the
multithreading capabilities of the client.
+\todo{Parametric lenses on devices share?}
+
\subsection{Resources}
Resource analysis during compilation can be useful to determine if an
\gls{mTask}-\gls{Task} is suitable for a specific device. If the device does
This idea could be extended to the analysis of stack size and possibly
communication bandwidth. With this functionality ever more reliable fail-over
-systems can be designed. When the system knows more precise bounds it can
+systems can be designed. When the system knows preciser bounds it can
allocate more \glspl{Task} on a device whilst staying within safe memory
bounds. The resource allocation can be done at runtime within the backend
itself or a general backend can be devices that can calculate the resources