tobast/talk-2019-10-OOPSLA19
1
0
Fork 0
forked from m2-internship/talk-2018-11-uppsala
Code Releases Activity

Squash "why does slow matter" into prev slide

Browse source
This commit is contained in:
Théophile Bastian 2019-10-14 19:07:34 +02:00
parent 79f6500721
commit bf3d847cf6
1 changed files with 13 additions and 37 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

48
slides.tex
View file

@ -239,44 +239,20 @@ Segmentation fault.
\pause{} \pause{}
\vspace{-4cm} \vspace{-5cm}
\begin{center} \begin{tcolorbox}[halign=center, colframe=red, colback=Lavender]
\bf \fontsize{8cm}{1cm} \bf \huge
\colorbox{white}{\alert{Complex}} \\ Complex \,\& \,slow
\colorbox{white}{\alert{\& slow!}} \end{tcolorbox}
\end{center}
\end{frame}
\begin{frame}{Why does slow matter?}
\begin{itemize}
\item{} After all, we're talking about \alert{debugging procedures} ran
by a \alert{human being} (slower than the machine).
\ldots{}or are we?
\end{itemize}
\pause{} \pause{}
\begin{center} \begin{tcolorbox}[halign=center, colframe=red, colback=Lavender]
\textbf{\Large{}No!} \huge
\end{center} \textbf{Pervasive:}\\ relied upon by debuggers, profilers, C++
exceptions \\
\begin{itemize} \medskip{}
\pause{}\item{} Pretty much any \alert{program analysis tool} \textbf{$\leadsto$ not only for debuggers!}
\pause{}\item{} \alert{Profiling} with polling profilers \end{tcolorbox}
\pause{}\item{} \alert{Exception handling} in C++
\end{itemize}
\vspace{2em}
\begin{center}
\textbf{\Large{}Debug data is not only for debugging}
\end{center}
\vspace{1em}
$\leadsto$ we might want \alert{an alternative time/space trade-off}
\end{frame} \end{frame}
\newcommand{\LinusMailOne}{ \newcommand{\LinusMailOne}{