I also extensively use org-mode to publish static sites and, well, organize essentially everything in work and my private life.
Learning org-mode is quite a valuable activity, in my opinion and experience.
I happen to tweak Emacs and write Clojure for a living, but thankfully I left the 'meta' trap behind years ago. My blog in on Medium.
https://medium.com/s/story/the-rise-of-anti-notifications-6c... 1.1MB 51 requests
Parent article 26kb 4 requests.
Both actually load quickly on a fast connection particularly with adblock. Sadly not everyone has a fast connection.
I do concede that org mode and lisp in general are brought up perhaps a bit too often here at HN seeing as they're not all that new though.
Those two points are, I believe, not in very widespread usage among blog writers. I believe that 2) is responsible for 1). Unflexible configurations are too widespread in my opinion and it goes very much against what a programmer / hacker could aspire for.
In the end, the time I've spent on this was very short. Compared to the previous systems I've tried, it now makes for a much smoother publishing experience for me. The ultimate point is that I can tailor it to my exact needs instead of being endlessly frustrated with a non-hackable publishing system.
My remark wasn't particularly aimed at you, simply it followed OP's (and also my) observation that "Org mode meta-blogging" is a category by itself :)
Maybe the author has that time to invest on tooling and doesn't care about how he would save a couple of hour by pushing a button on medium. Just because you did it unconsciously doesn't make it a trap.
LOL. As a dyed-in-the-wool Emacs user for 20 years, I have to admit that this is true. On the other hand, it makes me happy that the flagship software project of Free software is still alive and kicking. Moreover, people have been making these comments about Emacs ever since the early 1980's.
These days, my .emacs is very minimal and on any new machine my standard setup can be manually recreated in five minutes, mostly using Customize.
There is no need for any complicated thing that has to be automatically downloaded and updated in-place from a source control management repository. This is especially important when, for example, you are working in a heavily fortified corporate network, where access to the outside Internet needs to go through strange proxies if it is allowed at all. And in these cases it's usually a stressful environment to begin with, so when your boss -- who doesn't know anything about programming and just wants to see results quickly, dammit -- asks you what you've been doing all day, you don't want to have to explain that you spent all your time figuring out how to get Emacs to work over the corporate proxy.
I also often find myself going through all the steps in one of these articles then when I'm all ready to reap the results of success I move on to something else.
Which seems to happen quite often when people customize their software, especially up-front, instead of over time. I suppose you could describe it as waterfall-style customization
Once you've learned a bit more, it becomes second nature to a) make the tweaks you need and b) filter out those you don't.
I, for one, enjoy the ability to adapt my editing/workflow as my needs evolve.
1) Being able to clone the author's blog repo and read it offline (just a bonus that it's already in org mode so no post-processing necessary). Is there a "lemme download everything by this author and read offline?" button on Medium?
2) The blog being in a public Git repository is nice for transparency.
The expectation that all your code is on a public repository (I blame GitHub for this) is one of the most horrifying developments in software engineering.