summaryrefslogtreecommitdiff
path: root/content-org
diff options
context:
space:
mode:
authormms <git@sapka.me>2024-11-25 23:46:03 +0100
committermms <git@sapka.me>2024-11-25 23:46:03 +0100
commit916763ed737f8d525f2095586d88abad40e05a94 (patch)
tree0041daccd0c94c7ab32b8a23e0477f1bcbcbe4c7 /content-org
parentdc3238e15bcddeff3c80131c2bccc1b57f6ed6bb (diff)
feat: orig of vi
Diffstat (limited to 'content-org')
-rw-r--r--content-org/blog.org29
1 files changed, 26 insertions, 3 deletions
diff --git a/content-org/blog.org b/content-org/blog.org
index 8a5b53a..00b5cf7 100644
--- a/content-org/blog.org
+++ b/content-org/blog.org
@@ -8,7 +8,7 @@
#+HUGO_SECTION: blog
-* 2024 [100/102] :@blog:
+* 2024 [101/103] :@blog:
:PROPERTIES:
:EXPORT_HUGO_SECTION: blog/2024
:EXPORT_HUGO_CUSTOM_FRONT_MATTER+: :image_dir "blog/images" :image_max_width 600
@@ -123,6 +123,29 @@ It's small annoyance, but it shows the general direction.
Microsoft GitHub is still not near the biggest sin an Open Source can commit when it comes to cooperation (that crown still goes to using Discord), but it's far from being "Open".
**
+** DONE Useless things you may want to know: on the origin of "vi"
+CLOSED: [2024-11-25 Mon 23:44]
+:PROPERTIES:
+:EXPORT_FILE_NAME: origins-of-vi
+:EXPORT_HUGO_CUSTOM_FRONT_MATTER+: :Abstract Where did vi(1) came from?
+:END:
+
+We all know, that =vim(1)= stands for "vi improved", but what the buttocks is "vi"?
+
+Well, in the ancient times, a great editor was born - =ex(1)=.
+While =ed(1)= still is /the/ standard editor, it's lineage is not that simple.
+The =ex(1)= editor expanded on =ed(1)='s line-oriented text editing.
+In short: =ed(1)= was designed before computer displays were common, but =ex(1)= came out later.
+
+Therefore, =ex(1)= added a visual mode, where changes were displayed on the display.
+Like in Star Trek!
+This mode was enabled by calling the =:visual= command, or (in short) =:vi=.
+
+There you go, cyberpalls.
+You're now armed with a bulletproof story for the upcoming X-Mass parties!
+
+=vim(1)= stands for =visual mode of ex, the improved standard text editor, improved=.
+
** DONE RE: Self-Hosting Isn't a Solution; It's A Patch
CLOSED: [2024-11-25 Mon 21:14]
:PROPERTIES:
@@ -164,7 +187,7 @@ Threads, while still being Meta, is available from the Fediverse.
It's not self-hosted, but your self-hosted instance can be accessed from it.
And Zuck sure earns a lot from it.
-In fact, a lot of /centralized/ services stared as /decenrtalized/.
+In fact, a lot of /centralized/ services stared as /decentralized/.
Remember when Slack was accessible from IRC clients?
When Google Talk was just an XMPP?
It worked much better than it does now.
@@ -175,7 +198,7 @@ It's the centralization of the web which is the outlier.
Privacy is a side-product of decentralization, of self-hosting.
While it the essential, it's not the whole picture.
GDRP is a bare minimum, it's tax /we/ pay for the web of today.
-It's not a cure for anything.
+We should have never needed it.
** DONE Updated pages
CLOSED: [2024-11-23 Sat 22:39]