Commits

Romain Pelisse  committed b93f46a

adds a couple more images, fix one slide layout

  • Participants
  • Parent commits aebe14a

Comments (0)

Files changed (3)

File img/actors.jpg

Added
New image

File img/threading-model.jpg

Added
New image

File src/latex/main.tex

     \item Threads Pools
     \item Executor framework
   \end{itemize}
+
+  \begin{textblock*}{50mm}[0.7,1.8](100mm,100mm)
+    \includegraphics[height=120px]{../img/threading-model.jpg}
+  \end{textblock*}
+
+
 \end{frame}
 
 \begin{frame}[fragile]
-  \frametitle{The Scala (functionnal way) : Actors}
-  \begin{itemize}
-    \item Actors: \textit{Runnable with a BlockingQueue  (mailbox)}
+  \frametitle{The Scala (functionnal) way : Actors}
+  \begin{block}{Actors}
     \begin{itemize}
       \item Mailbox
       \item Non blocking
       \item Managed resources
     \end{itemize}
-  \end{itemize}
 
-  \begin{center}
-    Actors unify thread based and event based models
-  \end{center}
+    \begin{block}{In essence, actor are ...}
+      \textit{runnables with a blocking queue}
+    \end{block}
+
+    \begin{center}
+      Actors unify thread based and event based models
+    \end{center}
+  \end{block}
+
+  \begin{textblock*}{50mm}[0.8,2.2](100mm,100mm)
+    \includegraphics[height=110px]{../img/actors.jpg}
+  \end{textblock*}
+
 \end{frame}
 
 \begin{frame}[fragile]
-  \frametitle{The Scala (functionnal way) : Actors}
+  \frametitle{Scala and actors for concurrent programming ?}
   \begin{itemize}
-    \item So, Scala and Actors for concurrent programming ?
+    \item Benefits for sure ...
     \begin{itemize}
-      \item Benefits for sure ...
-      \begin{itemize}
-        \item Safe space to think sequentially
-        \item Messages as sole way to communicate
-        \item Can fallback on old share data / lock model
-        \item Typing harness providing even more robustness
-        \item Java integration
-      \end{itemize}
-      \item ... but arguably
-      \begin{itemize}
-        \item Actors and messages passing are nothing new
-        \item Functionnal programming on top of OOP might get you sick
-        \item Still a new world, lack of “Effective Actors” book...
-      \end{itemize}
+      \item Safe space to think sequentially
+      \item Messages as sole way to communicate
+      \item Can fallback on old share data / lock model
+      \item Typing harness providing even more robustness
+      \item Java integration
     \end{itemize}
+    \item ... but arguably
+    \begin{itemize}
+      \item Actors and messages passing are nothing new
+      \item Functionnal programming on top of OOP might get you sick
+      \item Still a new world, lack of “Effective Actors” book...
+    \end{itemize}
+  \end{itemize}
+\end{frame}
+
+\chapter{Conclusion}
+\begin{frame}[fragile]
+  \frametitle{Is scala right for your backend ? }
+  \begin{itemize}
+    \item TODO
   \end{itemize}
 \end{frame}
 
 \end{frame}
 
 \chapter{Annexes: Some (more) code samples on consiseness}
-\section{Case class makes it leaner}
-\begin{frame}[fragile]
-  \frametitle{Exemple 1: Case class makes it leaner}
-
-
-  \begin{textblock*}{50mm}[0.3,2.8](100mm,100mm)
-    \includegraphics[height=100px]{../img/obfuscate-it.jpg}
-  \end{textblock*}
-
-    \begin{columns
-      \begin{column}[l]{0.5\textwidth}
-        \begin{center}
-          (Java)
-          \newline
-          \includegraphics[height=200px]{../img/codes/pojo.jpg}
-
-          \end{center}
-        \end{column}
-        \begin{column}[r]{0.5\textwidth}
-          \begin{flushleft}
-            \begin{center}(Scala)\end{center}
-            \newline
-            \includegraphics[height=30px]{../img/codes/case-class.jpg}
-          \end{flushleft}
-        \end{column}
-      \end{columns}
-
-\tiny{Author : \mylink{mailto:david.bernard.31@gmail.com}{David Bernard}
-\newline
-\tiny{\textit{NB: This kind of Java code can be reduced a lot using \mylink{project
-lombok}{http://projectlombok.org/}}}
-
-\end{frame}
-
 
 \section{Pattern matching makes it safer}
 
   \begin{textblock*}{50mm}[0.22,1.8](100mm,100mm)
     \includegraphics[height=160px]{../img/hidden-behind-code.jpg}
   \end{textblock*}
-  \begin{textblock*}{50mm}[1.8,1.6](100mm,100mm)
+  \begin{textblock*}{50mm}[1.8,2.8](100mm,100mm)
     \includegraphics[height=80px]{../img/codes/martin.jpg}
-    \newline
-    \newline
     \tiny{Author : Martin Odersky - Scala author}
-    \newline
-    \newline
-    \newline
+  \end{textblock*}
+
+  \begin{textblock*}{50mm}[1.8,1.2](100mm,100mm)
       \begin{itemize}
         \item Just try to think about the amount of code to get this in Java, would it be clearer ?
         \item See how easy is to understand, even if you don't undestand the syntax !