mirre-mt/masters-thesis
Archived
1
0
Fork 0
Code Releases 1 Activity

tex: use a footnote istead of a citation for Go

Browse Source
This commit is contained in:
surtur 2023-08-18 17:59:13 +02:00
parent dfa9fe6a02
commit deabfd53ef
Signed by: wanderer
SSH Key Fingerprint: SHA256:MdCZyJ2sHLltrLBp0xQO0O1qTW9BT/xl5nXkDvhlMCI
2 changed files with 7 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
tex/appendices.tex
View File

@ -73,10 +73,12 @@ This appendix is concerned with explaining why certain technologies were used.
First, a question of \textit{`Why pick Go for building a web application?'} First, a question of \textit{`Why pick Go for building a web application?'}
might arise, so the following few lines will try to address that. might arise, so the following few lines will try to address that.
Go~\cite{golang}, or \emph{Golang} for SEO-friendliness and disambiguating Go Go\footnotemark{}, or \emph{Golang} for SEO-friendliness and disambiguating Go
the ancient game, is a strongly typed, high-level \emph{garbage-collected} the ancient game, is a strongly typed, high-level \emph{garbage-collected}
language where functions are first-class citizens and errors are values. language where functions are first-class citizens and errors are values.
\footnotetext{The Go programming language (\url{https://go.dev})}
The appeal for the author comes from a number of features of the language, such The appeal for the author comes from a number of features of the language, such
as built-in support for concurrency and unit testing, sane \emph{zero} values, as built-in support for concurrency and unit testing, sane \emph{zero} values,
lack of pointer arithmetic, inheritance and implicit type conversions, lack of pointer arithmetic, inheritance and implicit type conversions,
@ -88,9 +90,11 @@ have been foregone. Every \emph{gopher}\footnote{euph.\ a person writing in the
Go programming language} is expected to format their source code with the Go programming language} is expected to format their source code with the
official formatter (\texttt{gofmt}), which automatically ensures that the code official formatter (\texttt{gofmt}), which automatically ensures that the code
adheres to the one formatting standard. Then, there is \emph{The Promise} of adheres to the one formatting standard. Then, there is \emph{The Promise} of
backwards compatibility for Go 1.x, which makes it a good choice for long-term backwards\footnotemark{} compatibility for Go 1.x, which makes it a good choice
without the fear of being rug-pulled. for long-term without the fear of being rug-pulled.
\footnotetext{Now there is also the promise of \emph{forward compatibility}
(\url{https://go.dev/blog/toolchain})}
\n{2}{Why Nix/devenv}\label{appendix:whynix} \n{2}{Why Nix/devenv}\label{appendix:whynix}

8
tex/references.bib
View File

@ -63,14 +63,6 @@
note={{Available from: \url{https://nixos.org/manual/nix/stable/language/index.html}. [viewed 2023-05-17]}}, note={{Available from: \url{https://nixos.org/manual/nix/stable/language/index.html}. [viewed 2023-05-17]}},
} }
@misc{golang,
howpublished = {[online]},
title = {{The Go Programming language}},
author = {{The Go Authors}},
year = 2009,
note={{Available from: \url{https://go.dev/}. [viewed 2023-05-17]}},
}
@misc{dhalllang, @misc{dhalllang,
howpublished = {[online]}, howpublished = {[online]},
title = {{Dhall Configuration Language}}, title = {{Dhall Configuration Language}},