Mercurial Hosting > reactionary

diff src/about.html.luan @ 91:76baf48ea36b

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
add translation
author Franklin Schmidt <fschmidt@gmail.com>
date Fri, 02 May 2025 17:17:52 -0600
parents 8bd99d5f468e
children
line wrap: on
line diff
--- a/src/about.html.luan	Wed Apr 23 20:10:03 2025 -0600
+++ b/src/about.html.luan	Fri May 02 17:17:52 2025 -0600
@@ -1,17 +1,21 @@
 local Luan = require "luan:Luan.luan"
 local error = Luan.error
 local Io = require "luan:Io.luan"
-local Http = require "luan:http/Http.luan"
+local Site_translator = require "luan:gpt/Site_translator.luan"
+local get_lang = Site_translator.get_lang or error()
+local text_writer = Site_translator.text_writer or error()
 local Shared = require "site:/lib/Shared.luan"
 local head = Shared.head or error()
 local header = Shared.header or error()
+local luan_url = Shared.luan_url or error()
 
 
 return function()
-	Io.stdout = Http.response.text_writer()
+	local luan_url = luan_url()
+	Io.stdout = text_writer()
 %>
 <!doctype html>
-<html>
+<html lang="<%=get_lang()%>">
 	<head>
 <%		head() %>
 		<title>About Reactionary Software</title>
@@ -43,7 +47,7 @@
 
 			<p>Today's West is currently at the level of the decaying Greeks, heading toward complete idiocracy.  The programmers in Silicon Valley are like Ptolemy, able to construct and maintain horrible overcomplicated monstrosities, but totally unable to innovate at a fundamental level.  All good programming ideas are rejected because they don't fit into current programming ideologies.  Any programmer like Aristarchus who comes up with a good programming idea will be rejected and ridiculed for violating orthodoxy.  Modern programmers are in love with their own ideas and love complexity.  They hate simplicity and anything that violates their ideologies.</p>
 
-			<p>For a concrete example, consider <a href="https://www.luan.software/goodjava.html#parser">my parser</a>.  It is a basic innovation that massively simplifies parsing.  So what reception did it get?  Of course <a href="https://old.reddit.com/r/Compilers/comments/cv78b3/parsing_for_programmers_who_hate_modern_software/">it was ridiculed</a> by modern programmers.  This is the same story as Aristarchus.  Modern programmers naturally hate everything that is good and only love what is horrible.</p>
+			<p>For a concrete example, consider <a href="<%=luan_url%>/goodjava.html#parser">my parser</a>.  It is a basic innovation that massively simplifies parsing.  So what reception did it get?  Of course <a href="https://old.reddit.com/r/Compilers/comments/cv78b3/parsing_for_programmers_who_hate_modern_software/">it was ridiculed</a> by modern programmers.  This is the same story as Aristarchus.  Modern programmers naturally hate everything that is good and only love what is horrible.</p>
 
 			<p>Given this situation, what should a good reactionary programmer do?  In Matthew 7:6, Jesus said "Do not give what is holy to dogs, and do not throw your pearls before swine, or they will trample them under their feet, and turn and tear you to pieces."  Good software is pearls and modern programmers are swine.  So do not repeat my mistake of showing good software to modern programmers.</p>
 
@@ -57,25 +61,25 @@
 
 			<p>The result is that alt-tech is just as bad as (if not worse than) other modern tech.  A while ago I looked at YouTube alternatives, so I will use this as an example.  BitChute is horrible because its core function, video streaming, is horrible.  Videos often stall or don't play at all.  And BitChute's search is horrible.  BitChute is a technical failure.  Odysee is horrible because they require a password so complex to sign up that I couldn't produce one.  This reflects modern programmers' obsession with security in places where security doesn't matter at all.  Modern programmers, even on the right, hate individual freedom, so they refuse to give users the freedom to choose their own password.  And of course they can't be bothered with making things easier for users by, for example, generating a password for the user.  Since Odysee obviously hates the end user, I won't use Odysee.  Rumble had issues when I looked at this some time ago but seems to have fixed them.  Rumble actually may be okay, which means that they are as good as YouTube.</p>
 
-			<p>An example that I know even better is Reddit alternatives.  Here there really is nothing usable, which why <a href="/freedit.html">a Reddit alternative is needed</a>.  In that post I also go into detail in explaining why software from the Right is no better than other modern software.  And I have looked at all available Reddit alternatives, and as expected they are no good.</p>
+			<p>An example that I know even better is Reddit alternatives.  Here there really is nothing usable, which why <a href="freedit.html">a Reddit alternative is needed</a>.  In that post I also go into detail in explaining why software from the Right is no better than other modern software.  And I have looked at all available Reddit alternatives, and as expected they are no good.</p>
 
 			<p>The problem with alt-tech is the general problem with the Right.  They miss the core issue.  The core issue is not politics.  The core issue is culture.  Modern western culture is evil, so it will always produce bad software, bad politics, and bad everything else.</p>
 
 			<h2>Other Examples</h2>
 
-			<p><b>Git versus Mercurial</b> - A great example of modern programmers preferring bad software as described in <a href="/mercurial.html">the Mercurial post</a>.</p>
+			<p><b>Git versus Mercurial</b> - A great example of modern programmers preferring bad software as described in <a href="mercurial.html">the Mercurial post</a>.</p>
 
-			<p><b>The decline of Java</b> - An example of modern programmers destroying good software as I explained in <a href="/java.html">the Java post</a>.</p>
+			<p><b>The decline of Java</b> - An example of modern programmers destroying good software as I explained in <a href="java.html">the Java post</a>.</p>
 
-			<p><b>Java mail library</b> - The original <a href="https://docs.oracle.com/javaee/7/api/javax/mail/package-summary.html">javax.mail</a> was a huge overcomplicated mess.  This JavaMail package has since <a href="https://javaee.github.io/javamail/">moved to GitHub</a> where it belongs along with other horrible modern software.  Googling for alternatives gives you other libraries that are built on top of JavaMail.  Naturally I rejected all the garbage and wrote my own <a href="https://www.luan.software/goodjava.html#mail">goodjava.mail</a> from scratch.  This whole library is a little over 200 lines of code and is a thin layer on top of SMTP and MIME.  Modern programmers hate thin layers because they always think that they can do better than the underlying layer.  But a thick layer actually adds complexity and makes debugging more difficult for the user of the library.  My thin layer lets the user set the headers directly.  Does this mean that the user has to fully understand MIME headers?  No, not at all.  The user can just send himself an email of the type he wants using his favorite mail client, say gmail, and then when he receives the email, he can look at its source (with gmail "Show original").  Then he can just copy the headers into his code.  If the user is doing something complicated, then my thin layer gives him complete control to generate exactly whatever complex email he wants.  With modern libraries with their disgusting thick layers, it is always a struggle to do anything complex.</p>
+			<p><b>Java mail library</b> - The original <a href="https://docs.oracle.com/javaee/7/api/javax/mail/package-summary.html">javax.mail</a> was a huge overcomplicated mess.  This JavaMail package has since <a href="https://javaee.github.io/javamail/">moved to GitHub</a> where it belongs along with other horrible modern software.  Googling for alternatives gives you other libraries that are built on top of JavaMail.  Naturally I rejected all the garbage and wrote my own <a href="<%=luan_url%>/goodjava.html#mail">goodjava.mail</a> from scratch.  This whole library is a little over 200 lines of code and is a thin layer on top of SMTP and MIME.  Modern programmers hate thin layers because they always think that they can do better than the underlying layer.  But a thick layer actually adds complexity and makes debugging more difficult for the user of the library.  My thin layer lets the user set the headers directly.  Does this mean that the user has to fully understand MIME headers?  No, not at all.  The user can just send himself an email of the type he wants using his favorite mail client, say gmail, and then when he receives the email, he can look at its source (with gmail "Show original").  Then he can just copy the headers into his code.  If the user is doing something complicated, then my thin layer gives him complete control to generate exactly whatever complex email he wants.  With modern libraries with their disgusting thick layers, it is always a struggle to do anything complex.</p>
 
-			<p><b>Other Java libraries</b> - All of the libraries in <a href="https://www.luan.software/goodjava.html">my goodjava library collection</a> were written because all other alternatives that I could find were horrible, so I wrote my own.  Besides <a href="https://www.luan.software/goodjava.html#mail">goodjava.mail</a>, I have <a href="https://www.luan.software/goodjava.html#webserver">goodjava.webserver</a>, <a href="https://www.luan.software/goodjava.html#logger">goodjava.logger</a>, <a href="https://www.luan.software/goodjava.html#json">goodjava.json</a>, <a href="https://www.luan.software/goodjava.html#xml">goodjava.xml</a>, and of course <a href="https://www.luan.software/goodjava.html#parser">goodjava.parser</a> as good examples.  In every one of these cases, I challenge you to find an alternative to my library that is as easy to use.</p>
+			<p><b>Other Java libraries</b> - All of the libraries in <a href="<%=luan_url%>/goodjava.html">my goodjava library collection</a> were written because all other alternatives that I could find were horrible, so I wrote my own.  Besides <a href="<%=luan_url%>/goodjava.html#mail">goodjava.mail</a>, I have <a href="<%=luan_url%>/goodjava.html#webserver">goodjava.webserver</a>, <a href="<%=luan_url%>/goodjava.html#logger">goodjava.logger</a>, <a href="<%=luan_url%>/goodjava.html#json">goodjava.json</a>, <a href="<%=luan_url%>/goodjava.html#xml">goodjava.xml</a>, and of course <a href="<%=luan_url%>/goodjava.html#parser">goodjava.parser</a> as good examples.  In every one of these cases, I challenge you to find an alternative to my library that is as easy to use.</p>
 
-			<p><b>Scripting languages</b> - <a href="https://en.wikipedia.org/wiki/Scripting_language">Scripting languages</a> should be extremely simple.  There is no reason to make them complicated.  Yet all existing usable scripting languages are complicated.  So I wrote my own simple scripting language - <a href="https://www.luan.software/">Luan</a>.</p>
+			<p><b>Scripting languages</b> - <a href="https://en.wikipedia.org/wiki/Scripting_language">Scripting languages</a> should be extremely simple.  There is no reason to make them complicated.  Yet all existing usable scripting languages are complicated.  So I wrote my own simple scripting language - <a href="<%=luan_url%>/">Luan</a>.</p>
 
 			<h2>What you can do</h2>
 
-			<p>Do you want to support reactionary software as an alternative to horrible modern software?  If yes, then join our <a href="/discussion.html">discussions</a> and consider working on <a href="/needed.html">needed reactionary software</a>.</p>
+			<p>Do you want to support reactionary software as an alternative to horrible modern software?  If yes, then join our <a href="discussion.html">discussions</a> and consider working on <a href="needed.html">needed reactionary software</a>.</p>
 
 			<p>You also should consider the fact that if humanity itself becomes worthless, then good software no longer has any value.  To fight the degeneration of humanity, you might also consider my <a href="https://www.arkian.net/">Arkian project</a>.</p>
 		</div>