-adapter to be written for every device and functionality. Moreover, this does
-not allow you to build in logic into the device. A lot of the small \gls{IoT}
-devices have limited processing power but can still contain decision making.
-Oortgiese et al.\ lifted \gls{iTasks} from a single server model to a
-distributed server architecture~\cite{oortgiese_distributed_2017} that is also
-runnable on smaller devices like \acrshort{ARM}. However, this is limited to
-fairly high performance devices that are equipped with high speed communication
-lines. Devices in \gls{IoT} often only have \gls{LTN} communication with low
-bandwidth and a very limited amount of processing power and are therefore not
-suitable to run an entire \gls{iTasks} core.
+adapter to be written for every device and functionality. However, this forces
+a fixed logic in the device that is set at compile time. A lot of the small
+\gls{IoT} devices have limited processing power but can still contain decision
+making. Oortgiese et al.\ lifted \gls{iTasks} from a single server model to a
+distributed server architecture that is also runnable on smaller devices like
+\acrshort{ARM} devices\cite{oortgiese_distributed_2017}. However, this is
+limited to fairly high performance devices that are equipped with high speed
+communication channels. Devices in \gls{IoT} often only have \gls{LTN}
+communication with low bandwidth and a very limited amount of processing power
+and are therefore not suitable to run an entire \gls{iTasks} core.