summaryrefslogtreecommitdiff
path: root/writeup/writeup.tex
diff options
context:
space:
mode:
authorthing 1 <thing1@seacrossedlovers.xyz>2024-12-05 12:05:58 +0000
committerthing 1 <thing1@seacrossedlovers.xyz>2024-12-05 12:05:58 +0000
commit788c4f3f7f8197400d41c7189076b37a2c1efef8 (patch)
tree5aef75f18631d3dd336a99d163f97c75197ae51c /writeup/writeup.tex
parent8f27dfcccf5943e5bd8df37b923de3a34568eddf (diff)
added some small formating changes
Diffstat (limited to 'writeup/writeup.tex')
-rw-r--r--writeup/writeup.tex60
1 files changed, 42 insertions, 18 deletions
diff --git a/writeup/writeup.tex b/writeup/writeup.tex
index e765f6e..24ddf99 100644
--- a/writeup/writeup.tex
+++ b/writeup/writeup.tex
@@ -1,19 +1,30 @@
\documentclass[a4paper,12pt]{article}
-\usepackage[backend=bibtex]{biblatex} \usepackage{geometry} \usepackage{titling} \usepackage{titlesec}
-\usepackage[english]{babel} \usepackage[hidelinks]{hyperref} \usepackage{listings} \usepackage{xcolor}
-\usepackage{graphicx} \usepackage{forest} \usepackage{tikz-qtree} \usepackage{setspace}
+\usepackage[backend=bibtex]{biblatex}
+\usepackage{geometry}
+\usepackage{titling}
+\usepackage{titlesec}
+\usepackage[english]{babel}
+\usepackage[hidelinks]{hyperref}
+\usepackage{listings}
+\usepackage{xcolor}
+\usepackage{graphicx}
+\usepackage{forest}
+\usepackage{tikz-qtree}
+\usepackage{setspace}
\addbibresource{ref.bib}
\graphicspath{ {./images} }
-\titleformat{\section} {\Huge} {} {0em} {}[\titlerule] \geometry{a4paper,total={170mm,257mm},left=25mm,right=25mm,}
+\titleformat{\section} {\Huge} {} {0em} {}[\titlerule]
+\geometry{a4paper,total={170mm,257mm},left=25mm,right=25mm,}
\author{Lucas Standen} \title{Why are FOSS tools preferred in the development and privacy space?}
-\begin{document} \maketitle
+\begin{document}
+\maketitle
\newpage
@@ -22,7 +33,8 @@ clickable links, clickable references and a clickable table of contents, so plea
The Tex source and Bib Tex bibliography is available for all at \url{https://github.com/standenboy/epq/} under
the MIT/X document license.
-\tableofcontents \newpage
+\tableofcontents
+\newpage
\setlength{\parskip}{1em}
@@ -126,7 +138,8 @@ development, as opposed to one person sending in code every few weeks or days. T
in development over the Covid lock down's. As of 2024 it would be hard not to say Free Software is fully viable
against its Proprietary counterpart.
-\section{How is Free Software developed?} The process of developing Free Software has changed over time, especially
+\section{How is Free Software developed?}
+The process of developing Free Software has changed over time, especially
as the internet came to be, allowing developers from all across the world to add things. In modern terms the
development process is very simple, a developer can look at a piece of code, make changes to a local version of
it, then it can be uploaded to a central online version of the code, to be checked by lead maintainers, before
@@ -145,14 +158,15 @@ system. This pattern of development is liked amongst programmers as it allows ma
which is invaluable if your project has many developers. This method is also commonly used in Non-Free Software,
to manage large development teams\cite{NONFREEvcs}.
-\section{Comparing Free Software to its Proprietary counterparts} As previously mentioned there are many different
+\section{Comparing Free Software to its Proprietary counterparts}
+As previously mentioned there are many different
examples of Free Software, often made to be an alternative to a common piece of Proprietary software, each have
their pro's and con's. To compare, one can look at performance data and usability. To show a wide range of software,
this paper will look at programming IDE's, web browsers, and office software, as most computer users have used at
least one of these, and thus will be familiar with them.
-\subsection{Programming IDE's} \textit{An \textbf{IDE} is an \textbf{I}ntegrated \textbf{D}evelopment
-\textbf{E}nvironment}
+\subsection{Programming IDE's}
+\textit{An \textbf{IDE} is an \textbf{I}ntegrated \textbf{D}evelopment \textbf{E}nvironment}
The main IDE's used by developers are Free Software, but there are a few Non-Free ones that are used according to
the stack over flow developer survey\cite{IDEusage}. To compare text editors, one can look at \textit{Vs Code} as
@@ -175,10 +189,13 @@ that goes on until you reach the market cap.
\begin{figure}[h]
\caption{Comparing speed of browsers, time \textit{(lower is better)}}
- \includegraphics[width=\textwidth]{webbrowserperfomace.png} \center{\cite{BROWSERperformace}} \label{fig:graph}
+ \includegraphics[width=\textwidth]{webbrowserperfomace.png}
+ \center{\cite{BROWSERperformace}}
+ \label{fig:graph}
\end{figure}
-\subsection{Web Browsers} To compare web browsers, one can look at two commonly used browsers, Google Chrome,
+\subsection{Web Browsers}
+To compare web browsers, one can look at two commonly used browsers, Google Chrome,
and Firefox. Both of these are known projects, that are used by near billions every day combined, one can look at
their performance and usability to compare these projects.
@@ -201,7 +218,8 @@ the few exceptions to this rule. Due to this, most browsers will be effected by
effect in the coming years. As this happens it will become increasingly hard to deny that Firefox is easier to
customize and make usable to the users needs.
-\subsection{Office Software} When looking at office software, their are two commonly used tools, Microsoft Office
+\subsection{Office Software}
+When looking at office software, their are two commonly used tools, Microsoft Office
(also known as 365), and Libreoffice. Microsoft Office is Proprietary software, and has been since its creation
in the early days of personal computing, Libreoffice on the other hand, has been FOSS software from the start
(libre actually means free in spanish, so this is no surprise). They both provide advanced features, and for the
@@ -215,13 +233,19 @@ attacks, and long lasting bugs, that could be fixed by switching to Free Softwar
users of these tools fix these issues quickly compared to alternatives. This is usually put up to the fact that
most FOSS developers aren't working to new features and are instead working to making a tool that works for them.
-\subsection{General conclusions} Overall one can see that in many areas of software use, FOSS tools are already
+\subsection{General conclusions}
+Overall one can see that in many areas of software use, FOSS tools are already
at an equal state or better, than the Non-Free counterparts, for general users. One may find that this balance
begins to change in more specific fields, where optimisation and speed may become more important than it is to
the common computer user or tools are only made by large companies and no free alternative exist.
-\section{What makes Free Software so appealing to developers?} \section{What makes Free Software so appealing to
-privacy experts?} \section{Where else is Free Software used and why?} \section{What's next for the Free Software
-space?} \section{Final thoughts}
+\section{What makes Free Software so appealing to developers?}
+\section{What makes Free Software so appealing to privacy experts?}
+\section{Where else is Free Software used and why?}
+\section{What's next for the Free Software space?}
+\section{Final thoughts}
-\newpage \printbibliography } \end{document}
+\newpage
+\printbibliography
+}
+\end{document}