This is a blog post dedicated to the configuration language of my favourite editor: Emacs.
It is true that Emacs owes its flexibility and very configurable nature to this wonderful and awful language. It is both its greatest strength and weakness. It is simply the brick wall that is responsible for the learning curve.
This is an interesting discussion with many people that have in one way or another echoed the point of view that cryptocurrencies in general are a blight on society. While a wiser man than I cautioned against accepting the premise of the bully, in this case doing so is instrumental in dismantling the arguments.
This is the unofficial name that was given to the controversy that involved a blatant violation of the GitHub terms of service, and instigated a personal attack on the founder of Free Software Foundation, Richard Matthew Stallamann.
I am not here to either defend or explain my choice to not participate in the "sign or be unhirable in Open Source" open letter, and my decision to side with the countervailing party. I will merely mention that it was a decision to choose the lesser of two evils, and that this is what has transpired as a result.
This is not meant to be a detailed comparison, just a back-of-the-envelope guide explaining why you should or shouldn't use a particular program in particular circumstances.
sudoThis program is sadly, considered the default on most GNU+Linux
distributions. It is a rather complex beast, despite the fact that it
is, for lack of a better term, the original systemd, an ugly piece
of code that almost everyone hates, but still runs for some reason.
Not to say that systemd is bad, these days it's perhaps what it was
meant to be all along, but sudo is something that you likely need to
know about, but also something that you should avoid if possible on
your own machines.
This is a very controversial topic and perhaps one that will land me a lot of enemies. I nonetheless believe that it is imperative to understand the point: the existence of game remasters is a symptom of a larger problem, that will soon become all-encompassing. It is my firm belief that we as a species have blundered our way to this problem unknowingly, and that we can still fix it... albeit with a lot of effort, specifically pertaining to unlearning some of the bad habits that we have accumulated.
Info
I must preface this by pointing to something that should be blindingly obvious, but shall be taken out of context regardless. This is not a personal attack on Drew De Vault. While one might construe our relationship as antagonistic I have respect for a lot of what he is doing. We are of differing and in some ways incompatible political views, and have different approaches to programming.
However, the very object of the following text is to mock antagonism with such flimsy footing. The subject of the mockery is language elitism, conveyed through the lens of a frustrated rant by Drew De Vault, and demonstrated as a deconstruction of the "destruction". I will posit that all attempts to espouse such an opinion for any reason is fundamentally misguided.
This is quite an interesting experience.
I will not say that I am wholly disappointed, but that it is sad. I've been a vi user for the better part of my teens, and I've only picked up Emacs around ten years ago, when I was 19. So this challenge was less of a dive into foreign waters, and more of a return to my own roots. And it is interesting to see your grandparents do some renovations, to see signs of prosperity in some areas, but to also notice that they are struggling. Not financially, but in that they've lost track of what made them who they are.
SSH has some of the dumbest ideas in UX.
Rather than use the fact that the person responsible for the creation of this program is capable of such stupidity so as to discredit ssh, we politely forgive them for flaunting "I am a security expert" as if that makes their stupidity more forgivable.
I've had complaints about Markdown for years. I don't like it. Is it better than e.g. writing your code in ReST, I'd argue marginally, and only if you assume that ReST was meant to be used in the same circumstances as Markdown, which it does not.
In my opinion, if your life revolves around Markdown, this article will make your life a bit easier, not by a lot, but still. I'd make the case that we're better off leaving Markdown behind, and instead to move beyond "lightweight" text-based markup.
This is a blog post dedicated to my, and many other people's favourite text editor. In-keeping with the theme of this section, I shall mainly focus on the misunderstood nature of the editor, and my personal connection to it. Most of it is going to be in the negative light, so it slightly edges out being posted in the Software section.
This is a continuation of the rant about static site generation systems. While I liked vitepress a lot more than I like Jekyll I still have some issues with how it works.
In principle it is one of the better static site generators in my opinion, probably better than anything that I've dealt with so far...
This is perhaps a fitting beginning to the first blog post on my home page.
I FUCKING HATE JEKYLL.
I'm quite surprised, and frankly appalled at the fact that there are few if any useful tools for generating static sites.
I started off with Jekyll, because it seemed like the right tool for the job, after all it is supported by GitHub.