old stuff

Author: pshirshov

01-logstage/target/logstage.pdf 01-logstage/logstage.pdf

@@ -15,7 +15,7 @@
     %\usepackage[mathletters]{ucs}
     %\usepackage[utf8x]{inputenc}
     \usepackage[utf8]{inputenc}
-    \usepackage{pifont}    
+    \usepackage{pifont}
     \usepackage{newunicodechar}
     \newunicodechar{✪}{\ding{74}}
 
@@ -47,7 +47,7 @@
 
     \usepackage {tikz}
     \usetikzlibrary {positioning}
-    \graphicspath {{target/media/}}
+    %\graphicspath {{target/media/}}
     %----------------------------------------------------------------------------------------
     %	TITLE PAGE
     %----------------------------------------------------------------------------------------
@@ -72,7 +72,7 @@
 
   // ...
 
-  val data = 
+  val data =
       new HashMap[String, String]()
   data.put("from", "userA")
   data.put("to", "userB")
@@ -81,7 +81,7 @@
 \end{VerbatimOut}
 
 \begin{VerbatimOut}{ex-scala-logging.tmp}
-class Example 
+class Example
   extends LazyLogging { // Let's break SOLID!
   //...
 
@@ -99,7 +99,7 @@
 \begin{VerbatimOut}{ex-scala-tree-out.tmp}
 Expr(Apply(Select(
   Apply(
-    Select(Select(Ident("scala"), scala.StringContext), 
+    Select(Select(Ident("scala"), scala.StringContext),
       TermName("apply"))
       , List(Literal(Constant("Received a message from "))
           , Literal(Constant(""))
@@ -164,23 +164,23 @@ \section{The problem: what's wrong with all the loggers}
 
 \begin{frame}
 \frametitle{\code{scala-logging} API example}
-\scalacode{target/ex-scala-logging.tmp}
+\scalacode{ex-scala-logging.tmp}
 \end{frame}
 
 \begin{frame}
 \frametitle{\code{fluentd} logging API example}
-\scalacode{target/ex-fluentd.tmp}
+\scalacode{ex-fluentd.tmp}
 \end{frame}
 
 \section{The solution: code as structure}
 \begin{frame}
 \frametitle{The code\dots}
-\scalacode{target/ex-scala-tree-source.tmp}
+\scalacode{ex-scala-tree-source.tmp}
 \end{frame}
 
 \begin{frame}
 \frametitle{\dots~is structured}
-\scalacode{target/ex-scala-tree-out.tmp}
+\scalacode{ex-scala-tree-out.tmp}
 \end{frame}
 
 \begin{frame}
@@ -200,7 +200,7 @@ \section{The implementation: logstage}
 
 \begin{frame}
 \begin{figure}
-\Huge 
+\Huge
 \color{RubineRed} L✪GSTAGE
 \noindent
 {\color{RubineRed} \rule{\linewidth}{1mm} }
@@ -228,7 +228,7 @@ \section{The implementation: logstage}
 
 \begin{frame}
 \frametitle{An example}
-\scalacode{target/ex-scala-logstage.tmp}
+\scalacode{ex-scala-logstage.tmp}
 Followed by a cute screenshot of course:
 \begin{figure}
     \includegraphics[width=\textwidth]{media/logstage-console.png}
@@ -238,7 +238,7 @@ \section{The implementation: logstage}
 \begin{frame}
 \frametitle{Something nice for our robots}
 \begin{figure}
-    \inputminted[fontsize=\scriptsize]{json}{target/ex-json-out.tmp}
+    \inputminted[fontsize=\scriptsize]{json}{ex-json-out.tmp}
 \end{figure}
 \end{frame}
 

01-logstage/logstage.tex

@@ -15,7 +15,7 @@
     %\usepackage[mathletters]{ucs}
     %\usepackage[utf8x]{inputenc}
     \usepackage[utf8]{inputenc}
-    \usepackage{pifont}    
+    \usepackage{pifont}
     \usepackage{newunicodechar}
     \newunicodechar{✪}{\ding{74}}
 
@@ -47,7 +47,7 @@
 
     \usepackage {tikz}
     \usetikzlibrary {positioning}
-    \graphicspath {{target/media/}}
+    %\graphicspath {{media/}}
     %----------------------------------------------------------------------------------------
     %	TITLE PAGE
     %----------------------------------------------------------------------------------------
@@ -65,8 +65,8 @@
 \begin{document}
 
 \begin{VerbatimOut}{ex-scala-roles.tmp}
-@RoleId("testservice") 
-class TestService[F[_] : Monad](http: HttpSrv[F]) 
+@RoleId("testservice")
+class TestService[F[_] : Monad](http: HttpSrv[F])
   extends IzService {
     override def start(): Unit = http.start()
     override def stop(): Unit = http.stop()
@@ -145,9 +145,9 @@ \section{The problem: both Monolith and Microservice approaches are broken}
 \begin{itemize}
 \item \textit{Software components} are still in place -- in form of Services.
       All the potential pitfails of component design apply to microservices,
-\item Many checks which may be done by your compiler in case of monolithic design have  
-     to be performed by integration test suites (in case you have them, it's hard to write),   
-\item Many tasks are delegated to operations: in case of a monolith your dependency graph is being 
+\item Many checks which may be done by your compiler in case of monolithic design have
+     to be performed by integration test suites (in case you have them, it's hard to write),
+\item Many tasks are delegated to operations: in case of a monolith your dependency graph is being
       processed by your DI framework\footnotemark[1], in case of microservices it is\dots in worst case processed by people,
       in best case requires an orchestration tool. But we don't have any single great tool yet,
 \item An orchestration tool does \textit{exactly the same job} your DI framework may do. And lot more things.
@@ -166,7 +166,7 @@ \section{The solution: roles}
 \item Let's choose which \textit{roles} we wish to assign to a before we start it,
 \item Roles come from Classpath, may be discovered dynamically or statically,
 \item It resembles Containers and OSGi,
-\item Containers have some disadvantages. 
+\item Containers have some disadvantages.
       They provide you a lot so we get used to think that they are sluggish on startup.
       Isolated classloaders are inconvenient. Dynamic DI is a nightmare,
 \item Let's get rid of Dynamic DI. And let's keep isolation optional.
@@ -185,7 +185,7 @@ \section{The solution: roles}
 Roles allow you to do \textbf{everything} you can do with microservices plus have additional benefits\footnotemark[1]:
 \begin{itemize}
 \item Higher Density makes Development Flows better: instant startup of any combination of roles,
-\item Higher Density makes Operations easier: any combination of roles for any container. 
+\item Higher Density makes Operations easier: any combination of roles for any container.
     You don't need to start 5 containers to have 5 services with low load profile,
 \item Smaller distribution size: Just one image, less traffic,
 \item More static checks $\Rightarrow$ higher reliability,
@@ -201,9 +201,9 @@ \section{The solution: roles}
 \item Startup time. Do you remember Tomcat? Design matters\footnotemark[1],
 \item Weaker isolation $\Rightarrow$ more dangerous failures,
 \item Dependency convergence. You may need isolated classloaders\footnotemark[2],
-\item Heterogenous systems: C\#, Scala and Go won't mix in a single process\footnotemark[3], 
-\item Distributed communication between Roles: most likely you don't want it. Otherwise 
-      you need a mechanism similar to: distrubuted DI framework 
+\item Heterogenous systems: C\#, Scala and Go won't mix in a single process\footnotemark[3],
+\item Distributed communication between Roles: most likely you don't want it. Otherwise
+      you need a mechanism similar to: distrubuted DI framework
       built around \textit{Service Discovery} and \textit{Cluster State} concepts. See: \code{dOSGi},
 \item You need to build a nice Continuous Delivery pipeline.
 \end{itemize}
@@ -216,12 +216,12 @@ \section{The implementation: distage}
 
 \begin{frame}
 \begin{figure}
-\Huge 
+\Huge
 \color{RubineRed} DISTAGE
 \noindent
 {\color{RubineRed} \rule{\linewidth}{1mm} }
 \Large Next-gen Dependency Injection Framework for Scala
-\normalsize Generative, Modular, R✪les and Garbage Collection included 
+\normalsize Generative, Modular, R✪les and Garbage Collection included
 \end{figure}
 \end{frame}
 
@@ -230,7 +230,7 @@ \section{The implementation: distage}
 \begin{itemize}
 \item Next generation of DI.
 \item Generative, built on PPER principle. Allows you to plan context provisioning, edit the plan, then execute it,
-\item Fully aware of Scala typesystem, allows you to fuse FP and OOP lot better than before, 
+\item Fully aware of Scala typesystem, allows you to fuse FP and OOP lot better than before,
 \item Bundled Garbage Collector,
 \item \textit{Bundled Roles mechanism} built as an extension. Cheap for developer because of Garbage Collection,
 \item Bundled \code{typesafe-config} support built as an extension,
@@ -240,7 +240,7 @@ \section{The implementation: distage}
 
 \begin{frame}
 \frametitle{How may\footnotemark[1] it look like: Dynamic\footnotemark[2] loader example ?}
-\scalacode{target/ex-scala-roles.tmp}
+\scalacode{ex-scala-roles.tmp}
 \footnotetext[1]{Roles API is not published yet. More details to follow.}
 \footnotetext[2]{Static one is also available.}
 \end{frame}
@@ -275,7 +275,7 @@ \section{The implementation: distage}
 \item Idealingua: transport and codec agnostic gRPC alternative with rich modeling language,
 \item LogStage: zero-cost logging framework,
 \item \textit{Fusional Programming and Design} guidelines. We love both FP and OOP,
-\item \textit{Continous Delivery} guidelines for Role-based process, 
+\item \textit{Continous Delivery} guidelines for Role-based process,
 \item \textit{Percept-Plan-Execute} Generative Programming approach, abstract machine and computational model.
 Addresses Project Planning (see Operations Research). Examples: orchestration, build systems.
 \end{itemize}

02-roles/target/roles.pdf 02-roles/roles.pdf

@@ -9,7 +9,8 @@
 
     \usepackage{graphicx} % Allows including images
     \usepackage{booktabs} % Allows the use of \toprule, \midrule and \bottomrule in tables
-    \usepackage[outputdir=target]{minted}
+    %\usepackage[outputdir=target]{minted}
+    \usepackage{minted}
     \usepackage{xcolor}
     \usepackage[utf8]{inputenc}
     \usepackage{pifont}
@@ -85,7 +86,7 @@
 
     \usepackage {tikz}
     \usetikzlibrary {positioning}
-    \graphicspath {{target/media/}}
+    %\graphicspath {{target/media/}}
 
     \title[\distage]{\distage: Modern Staged Dependency Injection for Scala}
 
@@ -150,7 +151,7 @@ \section{The problem: Dependency Injection and Functional Programming}
 \frametitle{The motivation behind DI pattern and DI frameworks}
 \begin{enumerate}
 \item Systems we work with may be represented as graphs. Nodes are components (usually instances), edges are references,
-\item Graph transformation complexity grows with node count 
+\item Graph transformation complexity grows with node count
      (need to add one constructor parameter, have to modify $k$ classes), many operations have non-linear complexity,
 \item Graph composition has combinatoric complexity (need to run tests choosing between mock/production repositories and external APIs, have to write four configurations).
 \end{enumerate}

02-roles/roles.tex

@@ -11,7 +11,8 @@
 
     \usepackage{graphicx} % Allows including images
     \usepackage{booktabs} % Allows the use of \toprule, \midrule and \bottomrule in tables
-    \usepackage[outputdir=target]{minted}
+    %\usepackage[outputdir=target]{minted}
+    \usepackage{minted}
     \usepackage{xcolor}
     \usepackage[utf8]{inputenc}
     \usepackage{pifont}
@@ -87,7 +88,7 @@
 
     \usepackage{tikz}
     \usetikzlibrary{positioning}
-    \graphicspath{{target/media/}}
+    %\graphicspath{{target/media/}}
 
     \title[\distage]{\distage: Modern Staged Dependency Injection for Scala}
 

03-pper-basics/target/pper-base.pdf 03-pper-basics/pper-base.pdf

@@ -8,8 +8,8 @@ LATEX_ARGS=--interaction=nonstopmode -shell-escape -file-line-error  -file-line-
 SRCS = $(wildcard *.tex)
 PDFS = $(patsubst %.tex,%.pdf,$(SRCS))
 
-JUNK =  *.toc *.aux *.pdf *.ps *.eps *.log *.lof *.bbl *.blg *.dvi *.log *.out *.tmp
-JUNK_PARAMS = $(foreach mask,$(JUNK),-name "$(mask)" -or )
+#JUNK =  *.toc *.aux *.pdf *.ps *.eps *.log *.lof *.bbl *.blg *.dvi *.log *.out *.tmp
+#JUNK_PARAMS = $(foreach mask,$(JUNK),-name "$(mask)" -or )
 
 .PHONY: all clean pdf
 
@@ -22,14 +22,14 @@ pdf: $(PDFS)
 	@echo "== Compiling $*..."
 	@echo ""
 	mkdir -p $(PDF_DIR)
-	cp -R media/ $(PDF_DIR)/media
-	cp $*.tex $(PDF_DIR)/
+	ln -s $(shell pwd)/media/ $(PDF_DIR)/media || true
+	ln -s $(shell pwd)/$*.tex $(PDF_DIR)/ || true
 	cd $(PDF_DIR) && $(LATEX) $(LATEX_ARGS) $*
 	cd $(PDF_DIR) && $(LATEX) $(LATEX_ARGS) $*
 	# https://askubuntu.com/questions/113544/how-can-i-reduce-the-file-size-of-a-scanned-pdf-file
 	gs -sDEVICE=pdfwrite -dCompatibilityLevel=1.4 -dPDFSETTINGS=/prepress -dNOPAUSE -dQUIET -dBATCH -sOutputFile=$*.pdf $(PDF_DIR)/$*.pdf
-	#find $(PDF_DIR) -name '*.pdf' -exec echo gs -sDEVICE=pdfwrite -dCompatibilityLevel=1.4 -dPDFSETTINGS=/prepress -dNOPAUSE -dQUIET -dBATCH -sOutputFile=$(basename {}) {} \;
-	#find $(PDF_DIR) -name '*.pdf.tmp' -exec sh -c 'mv -- "$$0" ../"$${0%.tmp}"' {} \;
+
 
 clean:
-	find . \( $(JUNK_PARAMS) -false \) -delete
+	rm -rf $(PDF_DIR)
+	rm -f *.pdf