paritybit.ca

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | README | LICENSE

commit f653e79b9878a66b79df8d184d497ac03f31708e
parent 92231c168b7760495b2da108e845309c9e08cd2c
Author: Jake Bauer <jbauer@paritybit.ca>
Date:   Thu, 27 Aug 2020 12:19:51 -0400

Publish new blog post

Diffstat:
Mpages/blog.md | 1+
Apages/blog/nope-back-to-st.md | 71+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Mpages/home.md | 4++--
Mpublic/feeds/sitewide-feed.xml | 21+++++++++++++++++++++
Mpublic/sitemap.xml | 1+
5 files changed, 96 insertions(+), 2 deletions(-)

diff --git a/pages/blog.md b/pages/blog.md @@ -27,6 +27,7 @@ href="https://pleroma.paritybit.ca/jbauer">Pleroma</a>. ### 2020 <ul> + <li>2020-08-27 <a href="blog/nope-back-to-st">Nope, Back to st</a></li> <li>2020-08-22 <a href="blog/setting-up-weechat-again">Setting Up WeeChat Again with weechat-matrix</a></li> <li>2020-08-21 <a href="blog/my-top-10-most-used-commands">My Top 10 Most Used Commands</a></li> <li>2020-08-14 <a href="blog/the-hacker-quarterly-magazine">The Hacker Quarterly Magazine</a></li> diff --git a/pages/blog/nope-back-to-st.md b/pages/blog/nope-back-to-st.md @@ -0,0 +1,71 @@ +## Nope, Back to st + +[//]: # "After using Alacritty for a month, I think it's time to switch back to st." + +[//]: # "main.min.css" + +[//]: # + +<div class="byline"> +<b>Written By:</b> Jake Bauer | + <b>Posted:</b> 2020-08-27 | + <b>Last Updated:</b> 2020-08-27 +</div> + +I've been using Alacritty for about a month since I [switched to it from +st](https://www.paritybit.ca/blog/switching-to-alacritty) back at the end of +July. It's been a solid terminal, but it has one major drawback and one minor +annoyance which have drawn me once again back to st. + +In the blog post I linked above, I mentioned that Alacritty uses a lot more RAM +compared to st. Granted, Alacritty does have a lot of features compared to st, +but it's not like I made any use of them nor can it really justify RAM usage +that is this high: + +``` + 22.0 MiB + 25.2 MiB = 47.2 MiB st (4) + 59.1 MiB + 84.4 MiB = 143.6 MiB alacritty (4) +``` + +RAM usage was measured with `ps_mem`. Yep, that's four st windows open and four +Alacritty windows open. One of those st windows is the terminal in which I'm +writing this blog post, and I also ran `ps_mem` in an st window. All of the +terminals were freshly opened. + +It's not uncommon for me to have multiple terminal windows open like this. I'll +often have `newsboat`, `aerc`, `weechat`, two or more development terminals, and +a scratchpad terminal all open at once. I also tend to jump between what I'm +working on so I'll frequently have something like four terminal windows open +just for development as I'm working on two or three separate things at once. I +might have 24GB of RAM on my desktop machine, but I'd still rather not have +0.5-1.0GB taken up by just terminal windows (this can easily happen when they +have a lot of lines in their scrollback buffers). + +My minor gripe with Alacritty is that it's configured in YAML. Sure, I'm not +changing my configuration often, but I still dislike it and prefer the method of +configuring st over writing YAML. Besides, the two issues that I noted about +st: crashing when displaying colour emoji and the delete key not working right +in SSH sessions, are easy to work around. + +The emoji problem is simply solved by either installing the `libxft-bgra` +package, a patched version of libxft which [can be +found](https://gitlab.freedesktop.org/xorg/lib/libxft/-/merge_requests/1) as a +`.deb` package or in the Arch User Repositories, or by installing the Symbola +font (`ttf-symbola` for Arch or `fonts-symbola` for Debian) which will be used +as the font for rendering emoji and works just fine without `libxft-bgra`. + +Regarding the delete key, I was already using `set enable-keypad on` in my +`.inputrc` which fixes the problem locally, but in an SSH session all that is +required is to run `tput smkx` and the delete key works on the remote server +normally. Given how rarely I'm using the delete key on a remote server, this is +not a big deal. + +With all that Alacritty has to offer, I just haven't realized any benefit over +using st. st is very nice to both use and configure and I simply don't need the +features Alacritty has. I haven't noticed it being any faster than st, it's +noticeably slower to launch than st, and it uses a lot more RAM than st. + +_This is my ninety-seventh post for the +[#100DaysToOffload](https://social.paritybit.ca/tags/100DaysToOffload) +challenge. You can learn more about this challenge over at +[https://100daystooffload.com](https://100daystooffload.com)._ diff --git a/pages/home.md b/pages/home.md @@ -18,6 +18,8 @@ This site will soon™️ be available over Gopher and Gemini. <a class="rss-icon" href="/feeds/sitewide-feed.xml"> <img src="/img/feed-icon.png" width="15" height="15" alt="Click for RSS Feed"/> </a> </div> +2020-08-27 <a class="feed-item" href="blog/nope-back-to-st">Nope, Back to st</a> + 2020-08-22 <a class="feed-item" href="blog/setting-up-weechat-again">Setting Up WeeChat Again with weechat-matrix</a> 2020-08-21 <a class="feed-item" href="blog/my-top-10-most-used-commands">My Top 10 Most Used Commands</a> @@ -36,8 +38,6 @@ This site will soon™️ be available over Gopher and Gemini. 2020-08-08 <a class="feed-item" href="blog/how-to-not-make-an-ass-of-yourself-internet-discussions">How to Not Make an Ass of Yourself in Online Discussions</a> -2020-08-08 <a class="feed-item" href="blog/gentoo-isnt-for-me">Gentoo Isn't for Me</a> - ### What is a Parity Bit? It is a bit (in the 1's and 0's sense) used in checking for errors in digital diff --git a/public/feeds/sitewide-feed.xml b/public/feeds/sitewide-feed.xml @@ -7,6 +7,27 @@ <description>The feed that covers all notable additions, updates, announcements, and other changes for the entire paritybit.ca website.</description> <item> + <title>Nope, Back to st</title> + <link>https://www.paritybit.ca/blog/nope-back-to-st</link> + <guid>https://www.paritybit.ca/blog/nope-back-to-st</guid> + <pubDate>Thu, 27 Aug 2020 12:18:01 -0400</pubDate> + <description><![CDATA[<h2 id="nope-back-to-st">Nope, Back to st</h2> +<div class="byline"> +<p><b>Written By:</b> Jake Bauer | <b>Posted:</b> 2020-08-27 | <b>Last Updated:</b> 2020-08-27</p> +</div> +<p>I’ve been using Alacritty for about a month since I <a href="https://www.paritybit.ca/blog/switching-to-alacritty">switched to it from st</a> back at the end of July. It’s been a solid terminal, but it has one major drawback and one minor annoyance which have drawn me once again back to st.</p> +<p>In the blog post I linked above, I mentioned that Alacritty uses a lot more RAM compared to st. Granted, Alacritty does have a lot of features compared to st, but it’s not like I made any use of them nor can it really justify RAM usage that is this high:</p> +<pre><code> 22.0 MiB + 25.2 MiB = 47.2 MiB st (4) + 59.1 MiB + 84.4 MiB = 143.6 MiB alacritty (4)</code></pre> +<p>RAM usage was measured with <code>ps_mem</code>. Yep, that’s four st windows open and four Alacritty windows open. One of those st windows is the terminal in which I’m writing this blog post, and I also ran <code>ps_mem</code> in an st window. All of the terminals were freshly opened.</p> +<p>It’s not uncommon for me to have multiple terminal windows open like this. I’ll often have <code>newsboat</code>, <code>aerc</code>, <code>weechat</code>, two or more development terminals, and a scratchpad terminal all open at once. I also tend to jump between what I’m working on so I’ll frequently have something like four terminal windows open just for development as I’m working on two or three separate things at once. I might have 24GB of RAM on my desktop machine, but I’d still rather not have 0.5-1.0GB taken up by just terminal windows (this can easily happen when they have a lot of lines in their scrollback buffers).</p> +<p>My minor gripe with Alacritty is that it’s configured in YAML. Sure, I’m not changing my configuration often, but I still dislike it and prefer the method of configuring st over writing YAML. Besides, the two issues that I noted about st: crashing when displaying colour emoji and the delete key not working right in SSH sessions, are easy to work around.</p> +<p>The emoji problem is simply solved by either installing the <code>libxft-bgra</code> package, a patched version of libxft which <a href="https://gitlab.freedesktop.org/xorg/lib/libxft/-/merge_requests/1">can be found</a> as a <code>.deb</code> package or in the Arch User Repositories, or by installing the Symbola font (<code>ttf-symbola</code> for Arch or <code>fonts-symbola</code> for Debian) which will be used as the font for rendering emoji and works just fine without <code>libxft-bgra</code>.</p> +<p>Regarding the delete key, I was already using <code>set enable-keypad on</code> in my <code>.inputrc</code> which fixes the problem locally, but in an SSH session all that is required is to run <code>tput smkx</code> and the delete key works on the remote server normally. Given how rarely I’m using the delete key on a remote server, this is not a big deal.</p> +<p>With all that Alacritty has to offer, I just haven’t realized any benefit over using st. st is very nice to both use and configure and I simply don’t need the features Alacritty has. I haven’t noticed it being any faster than st, it’s noticeably slower to launch than st, and it uses a lot more RAM than st.</p> +<p><em>This is my ninety-seventh post for the <a href="https://social.paritybit.ca/tags/100DaysToOffload">#100DaysToOffload</a> challenge. You can learn more about this challenge over at <a href="https://100daystooffload.com">https://100daystooffload.com</a>.</em></p>]]></description> + </item> +<item> <title>Setting Up WeeChat Again with weechat-matrix</title> <link>https://www.paritybit.ca/blog/setting-up-weechat-again</link> <guid>https://www.paritybit.ca/blog/setting-up-weechat-again</guid> diff --git a/public/sitemap.xml b/public/sitemap.xml @@ -3,6 +3,7 @@ <url><loc>https://www.paritybit.ca</loc></url> <url><loc>https://www.paritybit.ca/home</loc></url> <url><loc>https://www.paritybit.ca/blog</loc></url> + <url><loc>https://www.paritybit.ca/blog/nope-back-to-st</loc></url> <url><loc>https://www.paritybit.ca/blog/setting-up-weechat-again</loc></url> <url><loc>https://www.paritybit.ca/blog/my-top-10-most-used-commands</loc></url> <url><loc>https://www.paritybit.ca/blog/the-hacker-quarterly-magazine</loc></url>