From 89f83d49ad7d4cd8baa815993d3172ca72e5b30e Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 8 Apr 2023 12:32:25 +0300 Subject: Update content for html --- gemfeed/2021-09-12-keep-it-simple-and-stupid.html | 24 +++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) (limited to 'gemfeed/2021-09-12-keep-it-simple-and-stupid.html') diff --git a/gemfeed/2021-09-12-keep-it-simple-and-stupid.html b/gemfeed/2021-09-12-keep-it-simple-and-stupid.html index c0bd599f..c374c118 100644 --- a/gemfeed/2021-09-12-keep-it-simple-and-stupid.html +++ b/gemfeed/2021-09-12-keep-it-simple-and-stupid.html @@ -10,7 +10,7 @@

Keep it simple and stupid

-Published at 2021-09-12T09:39:20+03:00; Updated at 2023-03-23
+Published at 2021-09-12T09:39:20+03:00; Updated at 2023-03-23

   _______________                        |*\_/*|_______
@@ -39,7 +39,7 @@
 

 Have a look at COBOL, a prevalent programming language of the past. No one is learning COBOL in college or university anymore, but many legacy systems still require COBOL experts. Why is this? It's just too scary to write everything from scratch. There's too much COBOL code out there that can't be replaced from today to tomorrow. 

 

-https://nymag.com/intelligencer/2020/04/what-is-cobol-what-does-it-have-to-do-with-the-coronavirus.html

+https://nymag.com/intelligencer/2020/04/what-is-cobol-what-does-it-have-to-do-with-the-coronavirus.html

 

 On Kubernetes


 

@@ -51,21 +51,21 @@
 

 Coming back to COBOL, k8s is on its way to becoming something similar. One day, k8s might not be the hottest tech stuff everyone wants to use. But there will be still many legacy k8s clusters around but not enough experts available to manage those:

 

-https://www.techrepublic.com/article/why-kubernetes-is-our-modern-day-cobol-says-a-tech-expert/

+https://www.techrepublic.com/article/why-kubernetes-is-our-modern-day-cobol-says-a-tech-expert/

 

 Another article which stroke me is:

 

-Today's Students Don't Understand the Basics of Computer Operations 

+Today's Students Don't Understand the Basics of Computer Operations 

 

 And here is something to smile about:

 

-https://christine.website/blog/theres-a-node-2021-10-02

+https://christine.website/blog/theres-a-node-2021-10-02

 

 The bloated web


 

 Another example is the modern web. Have you ever wondered why the internet becomes slower and slower nowadays? The modern web is so much like lasagna that I decided to use Gemini to be the primary protocol of my website. The HTML version of this website is just a fallback as many visitors don't know what Gemini is and don't have any compatible software installed for surfing the Geminispace:

 

-2021-04-24-welcome-to-the-geminispace.html

+2021-04-24-welcome-to-the-geminispace.html

 

 The Gemtext protocol is KISS. There's no way to do other formattings than headings, links, paragraphs, lists, quotes, and bare text blocks (e.g., ASCII art or code snippets). There's no way to create bloated Gemini sites, and due to its limited capabilities, there's also no way to commercialise it (e.g. there's no good way to track the site visitors as things like cookies don't exist). By design, the Gemini protocol can't be extended, so there is no chance to abuse it even in the future. Gemini sites will stay KISS forever, and there won't be any fancy HTML/JavaScript frameworks like we see on the modern web.

 

@@ -73,7 +73,7 @@
 

 Yet another example I want to bring up is DTail, the distributed log tail program I wrote. There are many great and fancy log-management solutions available to choose from, and they all seem complex to set up and maintain. The ELK stack, for example, requires you to operate an ElasticSearch cluster (or multiple, if you are geo-redundant), Logstash (different configurations and instances, depending on your infrastructure) and a Kibana web-frontend (which also needs to be highly available). I have operated ElasticSearch clusters on multiple occasions, and I must say that it is not an easy task to optimise it for the particular workload you might encounter. I also have seen many ES clusters operated by other people, and I have seen these clusters failing a lot (so it's not just me). The reduced complexity of DTail also makes it more robust against outages. You won't troubleshoot your distributed application very well if the log management infrastructure isn't working either.

 

-2021-04-22-dtail-the-distributed-log-tail-program.html

+2021-04-22-dtail-the-distributed-log-tail-program.html

 

 I don't say that the ELK stack doesn't work, but it requires experts and additional hardware resources to support it. But instead, if you keep your infrastructure simple (e.g. only use DTail), it will maintain pretty much by itself. 

 

@@ -91,7 +91,7 @@
 

 Not to mention, keeping things simple and stupid also reduces the potential malicious attack surface. It's not just about the software and services you use and operate. It's also about the software you write. Here is a nice article about the KISS principle in software development:

 

-https://thevaluable.dev/kiss-principle-explained/

+https://thevaluable.dev/kiss-principle-explained/

 

 When KISS is not KISS anymore


 

@@ -99,16 +99,16 @@
 

 Other relevant readings


 

-Is the madness ever going to end?

-Write plain text files

+Is the madness ever going to end?

+Write plain text files

 

 Enough ranted for now!

 

 E-Mail your comments to hi@paul.cyou :-)

 

-Controversially, a lack of features is a feature. Enjoy your peace an quiet. - Michael W Lucas 

+Controversially, a lack of features is a feature. Enjoy your peace an quiet. - Michael W Lucas 

 

-Back to the main site

+Back to the main site

 
 Generated with Gemtexter |
 served by OpenBSD/httpd(8) |
-- 
cgit v1.2.3