From 83c54aa0965c2b52c759355b4aa1a09a93672c65 Mon Sep 17 00:00:00 2001
From: uNetworkingAB <110806833+uNetworkingAB@users.noreply.github.com>
Date: Thu, 27 Oct 2022 08:11:26 +0200
Subject: [PATCH] Update READMORE.md

---
 misc/READMORE.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/misc/READMORE.md b/misc/READMORE.md
index 1bad508..eb49bab 100644
--- a/misc/READMORE.md
+++ b/misc/READMORE.md
@@ -231,7 +231,7 @@ If you want to, you can simply take the previous example, put it inside of a few
 Recent Node.js versions may scale using multiple threads, via the new Worker threads support. Scaling using that feature is identical to scaling using multiple threads in C++.
 
 ### Compression
-In the 1970s, programming was an elite's task. Today programming is done by uneducated "farmers" and as a result, the care for smart algorithms, memory usage, CPU-time usage and the like has dwindled in comparison. Just look at, how many web developers represent time - it is not uncommon for web developers to send an entire textual representation of time as 30-something actual letters inside a JSON document with an actual textual key. This is just awful. We have had standardized, time-zone neutral representation of time in binary, efficient, 4-byte representation since the 1970s. It's called unix timestamp and is an elegant and efficient way of representing time-zone neutral time down to the seconds.
+Programming is no longer an elite's task. The care for smart algorithms, memory usage, CPU-time usage and the like has dwindled in comparison with the early, scientific era of programming. Just look at, how many web developers represent time - it is not uncommon for web developers to send an entire textual representation of time as 30-something actual letters inside a JSON document with an actual textual key. This is just awful. We have had standardized, time-zone neutral representation of time in binary, efficient, 4-byte (or more commonly the 8 byte variant) representation since the 1970s. It's called unix timestamp and is an elegant and efficient way of representing time-zone neutral time down to the seconds.
 
 This is just an example of how we have regressed in our algorithmic thinking. Today it is common to use textual representations such as bloated JSON to represent data, even though most of that bloat is obvious repetitions and inefficient in nature. But we don't care because we have compression. True, even the most bloated source format can be compressed down to a small payload with few repetitions - however - this comes at TREMENDOUS cost.