This commit is contained in:
zapashcanon 2023-07-19 14:21:14 +02:00
parent 8eb1a06284
commit 4e89c92af1
Signed by: zapashcanon
GPG Key ID: 8981C3C62D1D28F1
4 changed files with 37 additions and 2 deletions

4
.gitignore vendored
View File

@ -7,3 +7,7 @@ _build
*.wast.tex
_minted-wasocaml/
*.listing
*.bcf
*.run.xml
*.bbl
*.blg

View File

@ -1,7 +1,16 @@
wasocaml.pdf: mintedstyle wasocaml.tex roboto
default: wasocaml.pdf
wasocaml.bcf: mintedstyle wasocaml.tex roboto bib.bib
texfot xelatex -shell-escape wasocaml.tex
texfot xelatex -shell-escape wasocaml.tex
wasocaml.pdf: mintedstyle wasocaml.tex roboto wasocaml.bbl
texfot xelatex -shell-escape wasocaml.tex
texfot xelatex -shell-escape wasocaml.tex
wasocaml.bbl: wasocaml.bcf
biber -quiet wasocaml.bcf --output-file wasocaml.bbl
mintedstyle:
(diff ./webassembly.py /usr/lib/python3/dist-packages/pygments/lexers/webassembly.py > /dev/null) || (echo "please install the correct wasm file for syntax highlighting by running cp ./webassembly.py /usr/lib/python3/dist-packages/pygments/lexers/webassembly.py" && exit 1)

7
bib.bib Normal file
View File

@ -0,0 +1,7 @@
@inproceedings{Haa+17,
title={Bringing the web up to speed with WebAssembly},
author={Haas, Andreas and Rossberg, Andreas and Schuff, Derek L and Titzer, Ben L and Holman, Michael and Gohman, Dan and Wagner, Luke and Zakai, Alon and Bastien, JF},
booktitle={Proceedings of the 38th ACM SIGPLAN Conference on Programming Language Design and Implementation},
pages={185--200},
year={2017}
}

View File

@ -12,6 +12,17 @@
\usepackage[most]{tcolorbox} % boxes (for source code or figures)
\usepackage{minted} % source code
\usepackage[
autolang=other,
backend=biber, % choix de l'outil de traitement
backref=true, % liens dans la bibliographie pour remonter dans le texte
backrefstyle=none, % afficher toutes les utilisations de la référence
bibstyle=alphabetic, % style pour les clés des références dans la bibliographie : [initialesAnnée]
citestyle=alphabetic, % style pour les clés des références dans le texte : [initialesAnnée]
%datamodel=software, % swh
sorting=ynt, % bibliographie triée par année, nom, titre
]{biblatex}
\definecolor{bg}{HTML}{282c34}
\definecolor{lightbg}{HTML}{D7D3CB}
\tcbuselibrary{minted}
@ -33,6 +44,8 @@
\affil[1]{OCamlPro SAS, 21 rue de Châtillon, 75014 Paris, France}
\affil[2]{Université Paris-Saclay, CNRS, ENS Paris-Saclay, Inria, Laboratoire Méthodes Formelles, 91190 Gif-sur-Yvette, France}
\bibliography{bib}
\begin{document}
\maketitle
@ -55,7 +68,7 @@ In this presentation, we will explore the compilation of garbage-collected langu
\subsection{Wasm}
JavaScript is widely thought as being the de facto language of the
web. However, it does show its limitations when it comes to
performance, security and safety. In order to remedy this, WebAssembly
performance, security and safety. In order to remedy this, WebAssembly~\cite{Haa+17}
(Wasm) has been developped as a secure modular language of predictable
performance. Its usage is expanding beyond the web: finding
applications in the cloud (Fastly, Cloudflare), in the creation of
@ -648,4 +661,6 @@ that we will be ready when browser start deploying it.
% TODO:
% For the conclusion, I really want to hear about lessons learned, moving forward, etc. Especially since there's no practical use for this work at this time, why should the broader OCaml community be interested in it? Is there something unique that OCaml offers wasm? Are there lessons that we--the OCaml community of developers--can learn from your experience? Were there specific limitations of OCaml that we should be aware of and work on? Are specific strengths of OCaml that distinguish your effort from those working in other languages and ecosystems? For the conclusion, I really want to hear about lessons learned, moving forward, etc. Especially since there's no practical use for this work at this time, why should the broader OCaml community be interested in it? Is there something unique that OCaml offers wasm? Are there lessons that we--the OCaml community of developers--can learn from your experience? Were there specific limitations of OCaml that we should be aware of and work on? Are specific strengths of OCaml that distinguish your effort from those working in other languages and ecosystems?
\printbibliography{}
\end{document}