summaryrefslogtreecommitdiff
path: root/content
diff options
context:
space:
mode:
authormms <git@sapka.me>2024-12-03 22:39:40 +0100
committermms <git@sapka.me>2024-12-03 22:39:40 +0100
commitb9833d6fe1a8b2aa6337418e3f129e417bcc5807 (patch)
tree9ffdffabf56041861838bdde79205529180f3425 /content
parent23468a51a6666cd7e59e2268db113758f2fa639e (diff)
feat: stable api
Diffstat (limited to 'content')
-rw-r--r--content/blog/2024/stable-api.md63
1 files changed, 63 insertions, 0 deletions
diff --git a/content/blog/2024/stable-api.md b/content/blog/2024/stable-api.md
new file mode 100644
index 0000000..2f35eed
--- /dev/null
+++ b/content/blog/2024/stable-api.md
@@ -0,0 +1,63 @@
++++
+title = "Things I care about: stable APIs"
+author = ["MichaƂ Sapka"]
+date = 2024-12-03T22:23:00+01:00
+categories = ["blog"]
+draft = false
+weight = 2001
+image_dir = "blog/images"
+image_max_width = 600
+Abstract = "Let a good thing be a good thing"
++++
+
+I'm a FreeBSD guy, not a Linux person.
+I use Emacs(1), plain HTML, jpg/gifs.
+I love Irssi, notmuch, xmpp.
+I code in Ruby, not in Python.
+I'm using more and more vim, but not neovim.
+
+What is the pattern here?
+Stable APIs.
+I'm too old to chase the current trend just to chase it.
+I want to lay down and have a nice time.
+I want to tinker with the software because I want to tinker it, not because the API changed.
+I don't even auto-update apps on my phone!
+But it seems that things are changing just to be changed.
+Nothing can be good _enough_, there is always this new crazy idea we simply have to chase.
+
+Case in point: Hugo.
+I used to love Hugo.
+Hugo is amazing! when you first start to use it.
+But then your site grows; I now have over 6000 sub pages.
+So, what does Hugo do?
+Break things.
+I am afraid to update this damn thing, as there is a significant chance there will be some breaking change.
+Sure, it may be a warning here and there, but then it will stop working.
+Don't like where I put my name for RSS?
+It was OK a month ago.
+Hate my use of HTML in markdown?
+We had a deal!
+I was to do it when markdown shows its huge limits.
+
+I used to run neovim(1).
+It was shiny, it was fast, it was multi-threaded.
+But the community doesn't care for old farts like me, and each update of packages was a lottery - what will break <span class="underline">this time</span>?
+Neovim broke vim, so why the hell not, right?
+(btw, hating of neovim community is a subject for a different time).
+
+Yeah, no.
+Thank you.
+Since I'm using tmux(1) more and more, I'll stick to good, old vim(1).
+My Emacs(1) config will most likely work for at least a few years before something breaks.
+I don't expect FreeBSD to adapt SystemD/the-whatitsname-ifconfig-replacement.
+
+And yes, they can rip Xorg from my cold, dead hands.
+
+I'm not against progress, I love my multi threading, I love my fast internet.
+What I hate is progress at all cost.
+Sometimes it's nothing at all cost, as GPT doesn't offer anything new.
+But the cost it always there in the form of something that was there, working, having a great time.
+
+Do you know that there are people solving Advent of Code using awk(1)?
+Yes, this old rusty thing.
+Somehow, after all those years, it is still _good enough_ for the task.