Add section "Languages"

This commit is contained in:
inference 2024-02-09 23:58:48 +00:00
parent 10bef988ef
commit 4ba964ad80
Signed by: inference
SSH Key Fingerprint: SHA256:FtEVfx1CmTKMy40VwZvF4k+3TC+QhCWy+EmPRg50Nnc

View File

@ -1,7 +1,7 @@
<!DOCTYPE html>
<!-- Inferencium - Website - About -->
<!-- Version: 8.1.0-alpha.13 -->
<!-- Version: 8.1.0-alpha.14 -->
<!-- Copyright 2022 Jake Winters -->
<!-- SPDX-License-Identifier: BSD-3-Clause -->
@ -33,6 +33,19 @@
<ul>
<li><a href="#about_me">About Me</a></li>
<li><a href="#date_time">Date and Time</a></li>
<li><a href="#languages">Languages</a></li>
<ul>
<li><a href="#languages-markup">Markup</a></li>
<ul>
<li><a href="#languages-markup-xhtml">XHTML</a></li>
<li><a href="#languages-markup-asciidoc">AsciiDoc</a></li>
</ul>
<li><a href="#languages-programming">Programming</a></li>
<ul>
<li><a href="#languages-programming-rust">Rust</a></li>
<li><a href="#languages-programming-go">Go</a></li>
</ul>
</ul>
<li><a href="#licensing">Licensing</a></li>
<ul>
<li><a href="#licensing-code">Code</a></li>
@ -115,6 +128,74 @@
<code>YYYYMMDDThhmmss-hhmm</code> (with negative
offset).</p>
</section>
<section id="languages">
<h2><a href="#languages">Languages</a></h2>
<section id="languages-markup">
<h3><a href="#languages-markup">Markup</a></h3>
<p>The following markup languages are used in my code, with
rationale provided for the usage of each language.</p>
<section id="languages-markup-xhtml">
<h4><a href="#languages-markup-xhtml">XHTML</a></h4>
<p>XHTML is preferred for most content
due to its HTML-based design and syntax,
with advantages over HTML, including
strict parsing checks which assist with
achieving code-correctness, and being
XML-compliant to allow widespread usage
even outside of the intended HTML-based
use case.</p>
<p>HTML has multiple flaws, including
allowing broken code to be loaded in the
user's web browser, not informing the
developer of broken code or mismatching
tags, and using non-standard, highly
permissive syntax which is
non-portable. XHTML mitigates or
completely fixes these issues via
its XML namespace.</p>
</section>
<section id="languages-markup-asciidoc">
<h4><a href="#languages-markup-asciidoc">AsciiDoc</a></h4>
<p>AsciiDoc is used when portability is
a concern, as it allows easy conversion
to other file formats, including HTML
and PDF. AsciiDoc can also be read
as-is, due to it having clean markup and
high readability when viewed as
plaintext.</p>
</section>
</section>
<section id="languages-programming">
<h3><a href="#languages-programming">Programming</a></h3>
<p>The following programming languages are used in my code, with
rationale provided for the usage of each language.</p>
<section id="languages-programming-rust">
<h4><a href="#languages-programming-rust">Rust</a></h4>
<p>Rust is a partially object-oriented
programming language with a focus on
security and performance. It has strict
compile-time checks to verify the
memory-safety and thread-safety of code,
is memory-efficient, has no garbage
collection, is highly portable, has
great support for integration with other
languages, and is well-suited for both
high-level and low-level code.</p>
<p>Rust is the modern replacement for
C++.</p>
</section>
<section id="languages-programming-go">
<h4><a href="#languages-programming-go">Go</a></h4>
<p>Go is a functional programming
language with a focus on performance. It
is easy to use, has garbage collection,
allows clean codebases, and is suitable
for high-level code.</p>
<p>Go is the modern replacement for
C.</p>
</section>
</section>
</section>
<section id="licensing">
<h2><a href="#licensing">Licensing</a></h2>
<p>I care about upstreaming and sharing code, strongly