2 files changed, 16 insertions(+), 15 deletions(-)

M build
M posts/2023-05-10-lebka-propaganda-1.md

@@ 92,7 92,7 @@ generate_navbar
 for f in `find content posts fun -name \*.md`; do
 	PART=$OUT_DIR/`basename -s .md $f`.part.html
 	HTML=$OUT_DIR/`basename -s .md $f`.html
-	 mmtt < $f | lowdown --html-no-skiphtml --html-no-escapehtml > $PART
+	 mmtt < $f | lowdown --parse-math --html-no-skiphtml --html-no-escapehtml > $PART
 	TITLE=`get_title $f` CONTENT_HTML=$PART mmtt < template.html > $HTML
 done
 

@@ 4,16 4,17 @@
 
 The overwhelming complexity of current web standards has narrowed down web
 browsers to just 3 implementations: Chromium, Safari, and Frefox. Even
-Microsoft, valued at 2 *trillion* dollars[1] with 100k developers[2], abandoned
-maintaining its own web browser and switched to Blink.
+Microsoft, valued at 2 *trillion* dollars[^ms_networth] with 100k
+developers[^ms_dev_count], abandoned maintaining its own web browser and
+switched to Blink.
 
 Interestingly, Apple's uncompetitive browser restrictions are the last thing
 keeping web browser diversity alive. Today's web development usually involves
 maintaining compatibility with Chrome, Safari, and Firefox.
 
-- Chrome, because it has the biggest usage share (65 %[3])
-- Safari, because it is mandatory on Apple devices (19 %[3])
-- Firefox, because you might as well while you are at it (2 %[3])
+- Chrome, because it has the biggest usage share
+- Safari, because it is mandatory on Apple devices
+- Firefox, because you might as well while you are at it
 
 Supporting 2 platforms instead of 3 isn't a significant reduction in workload.
 As seen by Firefox still being deemed worth the developer's time and effort to


@@ 23,10 24,10 @@ support.
 
 Imagine if Apple decided to abandon WebKit, joining forces with Chromium just
 like Microsoft. Firefox would be in an even worse position than it is now. With
-Chromium-based browsers dominating 94 %[3] of the web, few would care about the
-remaining 6 %. The reduced need to distinguish between browser-specific behavior
-and standard specified behavior would kill any browser that did not walk or
-quack like Chrome.
+Chromium-based browsers dominating 94 % of the web, few would care
+about the remaining 6 %[^usage_share]. The reduced need to distinguish between
+browser-specific behavior and standard specified behavior would kill any browser
+that did not walk or quack like Chrome.
 
 This would enable Chrome to push non-standard behavior and custom features, such
 as [Web


@@ 39,7 40,7 @@ emerge. Competing with Chrome would mean not only implementing the entire
 HTML/CSS/JS stack but also additional features like a face recognition API.
 
 Of course, Apple isn't keeping WebKit alive to save Firefox; they talk about
-"security" reasons[4]...
+"security" reasons[^misc]...
 
 Ironically, *efforts to stop Apple from enforcing WebKit on iOS might be the
 final nail in the Firefox coffin*.


@@ 69,8 70,8 @@ technical debt, reducing complexity, improving modularity, embracing simplicity,
 making it possible again for meere mortals to create homebrew
 browsers[...](https://git.sr.ht/~prokop/lebka)
 
-[1]: https://www.macrotrends.net/stocks/charts/MSFT/microsoft/net-worth
-[2]: https://devblogs.microsoft.com/engineering-at-microsoft/welcome-to-the-engineering-at-microsoft-blog
-[3]: https://en.wikipedia.org/wiki/Usage_share_of_web_browsers
-[4]: https://www.macrumors.com/2022/02/25/should-apple-ban-rival-browser-engines
+[^ms_networth]: https://www.macrotrends.net/stocks/charts/MSFT/microsoft/net-worth
+[^ms_dev_count]: https://devblogs.microsoft.com/engineering-at-microsoft/welcome-to-the-engineering-at-microsoft-blog
+[^usage_share]: https://en.wikipedia.org/wiki/Usage_share_of_web_browsers
+[^misc]: https://www.macrumors.com/2022/02/25/should-apple-ban-rival-browser-engines