# Why are all discussions on this blog closed?

**URL:** <https://discourse.codinghorror.com/t/why-are-all-discussions-on-this-blog-closed/10147>\
**Category:** Site Feedback\
**Created:** [April 15, 2025, 8:13pm UTC](https://discourse.codinghorror.com/t/why-are-all-discussions-on-this-blog-closed/10147 "2025-04-15T20:13:04Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![EmirOfGroofunkistan](https://discourse-cdn.codinghorror.com/user_avatar/discourse.codinghorror.com/emirofgroofunkistan/32/78665_2.png) [@EmirOfGroofunkistan](https://discourse.codinghorror.com/u/EmirOfGroofunkistan)\
**Post date:** [April 15, 2025, 8:13pm UTC](https://discourse.codinghorror.com/t/why-are-all-discussions-on-this-blog-closed/10147/1 "2025-04-15T20:13:04Z")

</div>

I have loved the software and ideas you’ve come up with and enjoyed your blog over the years. But I think it’s poor form to write a purely political blog in the middle of it all and then immediately disable comments. It’s your blog, so you can do what you want, but I lost a lot of respect with that move. [Let's Talk About The American Dream](https://discourse.codinghorror.com/t/lets-talk-about-the-american-dream/10079)

---

<div class="post-metadata">

**Author:** ![codinghorror](https://discourse-cdn.codinghorror.com/user_avatar/discourse.codinghorror.com/codinghorror/32/36371_2.png) [@codinghorror](https://discourse.codinghorror.com/u/codinghorror)\
**Post date:** [April 16, 2025, 2:52am UTC](https://discourse.codinghorror.com/t/why-are-all-discussions-on-this-blog-closed/10147/2 "2025-04-16T02:52:10Z")

</div>

We are slowly opening comments on older posts cc @JimPas – I tried to explain why I chose to make this decision **for those specific posts**. I want the discussion to be a diaspora across the entire Internet, not siloed here – take the discussion _everywhere_.

---

<div class="post-metadata">

**Author:** ![Nayan\_Zaveri](https://discourse-cdn.codinghorror.com/user_avatar/discourse.codinghorror.com/nayan_zaveri/32/78649_2.png) [@Nayan\_Zaveri](https://discourse.codinghorror.com/u/Nayan_Zaveri)\
**Post date:** [April 19, 2025, 6:23am UTC](https://discourse.codinghorror.com/t/why-are-all-discussions-on-this-blog-closed/10147/3 "2025-04-19T06:23:06Z")

</div>

I agree… it is difficult to discuss when you want to take the discussion everywhere… It is like inviting everyone to party and they can go wherever they like at whatever time they wish…

---

<div class="post-metadata">

**Author:** ![codinghorror](https://discourse-cdn.codinghorror.com/user_avatar/discourse.codinghorror.com/codinghorror/32/36371_2.png) [@codinghorror](https://discourse.codinghorror.com/u/codinghorror)\
**Post date:** [April 19, 2025, 6:46am UTC](https://discourse.codinghorror.com/t/why-are-all-discussions-on-this-blog-closed/10147/4 "2025-04-19T06:46:51Z")

</div>

The goal is to spread the word, not capture it all here, in those specific cases. Let’s keep re-opening old discussions on popular blog posts @JimPas @pfaffman

---

<div class="post-metadata">

**Author:** ![EmirOfGroofunkistan](https://discourse-cdn.codinghorror.com/user_avatar/discourse.codinghorror.com/emirofgroofunkistan/32/78665_2.png) [@EmirOfGroofunkistan](https://discourse.codinghorror.com/u/EmirOfGroofunkistan)\
**Post date:** [April 23, 2025, 2:05pm UTC](https://discourse.codinghorror.com/t/why-are-all-discussions-on-this-blog-closed/10147/5 "2025-04-23T14:05:18Z")

</div>

Maybe it would be better to allow discussion here and encourage links and references to discussions in other communities “all over the internet”?

---

<div class="post-metadata">

**Author:** ![codinghorror](https://discourse-cdn.codinghorror.com/user_avatar/discourse.codinghorror.com/codinghorror/32/36371_2.png) [@codinghorror](https://discourse.codinghorror.com/u/codinghorror)\
**Post date:** [April 24, 2025, 4:21am UTC](https://discourse.codinghorror.com/t/why-are-all-discussions-on-this-blog-closed/10147/6 "2025-04-24T04:21:31Z")

</div>

Let’s keep re-opening older blog entries for discussion cc @JimPas @pfaffman

There will be a discourse community of practice around our GMI initiative soon. Stay tuned.

---

<div class="post-metadata">

**Author:** ![pfaffman](https://discourse-cdn.codinghorror.com/user_avatar/discourse.codinghorror.com/pfaffman/32/74742_2.png) [@pfaffman](https://discourse.codinghorror.com/u/pfaffman)\
**Post date:** [April 24, 2025, 12:20pm UTC](https://discourse.codinghorror.com/t/why-are-all-discussions-on-this-blog-closed/10147/7 "2025-04-24T12:20:44Z")

</div>

> [@codinghorror](#):
>
> Let’s keep re-opening older blog entries for discussion cc @JimPas @pfaffman

Not sure for to act on this. Would you like for me to item them all via rails, or is there some way to know which should be reopened, or not re-opened?

> [@codinghorror](#):
>
> There will be a discourse community of practice around our GMI initiative soon. Stay tuned.

Sounds interesting! Let me know how I can help!

---

<div class="post-metadata">

**Author:** ![JimPas](https://discourse-cdn.codinghorror.com/user_avatar/discourse.codinghorror.com/jimpas/32/76163_2.png) [@JimPas](https://discourse.codinghorror.com/u/JimPas)\
**Post date:** [May 18, 2025, 2:51am UTC](https://discourse.codinghorror.com/t/why-are-all-discussions-on-this-blog-closed/10147/8 "2025-05-18T02:51:32Z")

</div>

When I reopen topics I read the again, or at least the entire first post. But here’s a topic where I clicked on “Show Full Post” and it got stuck LOADING. I checked it out by clicking on the link to the blog and here’s the message I received from Cloudflare. The first link is from the forum. The 2nd is from the blog.  
[The Principle of Least Power](https://discourse.codinghorror.com/t/the-principle-of-least-power/511)  
[https://www.codinghorror.com/blog/2007/07/the-principle-of-least-power.html](https://www.codinghorror.com/blog/2007/07/the-principle-of-least-power.html)

 ![image](https://discourse-cdn.codinghorror.com/uploads/default/original/3X/7/0/705f07d4d2168b873c2b63c2c9c4961119ac4bea.jpeg)  
Here’s the screen shot of it being stuck on LOADING.  
 ![image](https://discourse-cdn.codinghorror.com/uploads/default/original/3X/1/1/119714858f91693566ede4bfdfb1a1f8484844e2.jpeg)

---

<div class="post-metadata">

**Author:** ![codinghorror](https://discourse-cdn.codinghorror.com/user_avatar/discourse.codinghorror.com/codinghorror/32/36371_2.png) [@codinghorror](https://discourse.codinghorror.com/u/codinghorror)\
**Post date:** [May 20, 2025, 9:55pm UTC](https://discourse.codinghorror.com/t/why-are-all-discussions-on-this-blog-closed/10147/9 "2025-05-20T21:55:39Z")

</div>

Some of the redirects from old URLs are not quite in place..

`https://www.codinghorror.com/blog/2007/07/the-principle-of-least-power.html`  
`https://blog.codinghorror.com/the-principle-of-least-power/`

I will work on this! I edited the first post for now..

 ![image](https://discourse-cdn.codinghorror.com/uploads/default/original/3X/4/7/47d2b8080ea2725d7656ddba19dbb378320c0111.png)

---

<div class="post-metadata">

**Author:** ![estrella\_s](https://discourse-cdn.codinghorror.com/letter_avatar_proxy/v2/letter/e/e19b73/32.png) [@estrella\_s](https://discourse.codinghorror.com/u/estrella_s)\
**Post date:** [August 2, 2026, 9:34pm UTC](https://discourse.codinghorror.com/t/why-are-all-discussions-on-this-blog-closed/10147/10 "2026-08-02T21:34:49Z")

</div>

I get that they want organic discussion happening everywhere, but yeah it’s kinda jarring as a reader when you’re not sure upfront whether you can comment on a post or not. Feels more approachable if there’s a consistent rule either way.

---

<div class="post-metadata">

**Author:** ![cjs](https://discourse-cdn.codinghorror.com/user_avatar/discourse.codinghorror.com/cjs/32/79351_2.png) [@cjs](https://discourse.codinghorror.com/u/cjs)\
**Post date:** [August 2, 2026, 9:45pm UTC](https://discourse.codinghorror.com/t/why-are-all-discussions-on-this-blog-closed/10147/11 "2026-08-02T21:45:11Z")

</div>

Welcome, @estrella_s.

My understanding (as a new mod here) is that a lot of the closures were meant to be temporary, and many things just haven’t been re-opened yet. I’m re-opening things as come across them; if there’s someplace you want to post just send a PM to [@moderators](https://discourse.codinghorror.com/groups/moderators) asking for whichever topics you like to be re-opened.

The whole closure thing was admittedly a bit of a hack that we still seem to be recovering from, but unfortunately I’m not seeing any better way of achieving the original aim.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://discourse-cdn.codinghorror.com/user_avatar/discourse.codinghorror.com/codinghorror/32/36371_2.png) [@codinghorror](https://discourse.codinghorror.com/u/codinghorror)\
**Post date:** [August 2, 2026, 10:28pm UTC](https://discourse.codinghorror.com/t/why-are-all-discussions-on-this-blog-closed/10147/12 "2026-08-02T22:28:35Z")

</div>

> [@cjs](#):
>
> was admittedly a bit of a hack that we still seem to be recovering from

Agreed, but given the apocalyptic circumstances around [that _particular_ blog post](https://blog.codinghorror.com/stay-gold-america/), necessary.

Here’s the “behind the music” of how that blog post was written which explains in excruciating detail, if you need it:

> **[Jeff Atwood on Technical Blogging](https://writethatblog.substack.com/p/jeff-atwood-on-technical-blogging)**
>
> Coding Horror/Stack Overflow/Discourse creator Jeff Atwood on why blogging still matters

Also, some really ancient discussions may truly be totally irrelevant at this point, and closing all old discussion does reduce the overall attack surface. Some Discourse instances auto-close all topics {x] days after last response, or {x} days after the topic is posted, which is fine, but I’d prefer not to do that and have not enabled either of those settings.

---

<div class="post-metadata">

**Author:** ![cjs](https://discourse-cdn.codinghorror.com/user_avatar/discourse.codinghorror.com/cjs/32/79351_2.png) [@cjs](https://discourse.codinghorror.com/u/cjs)\
**Post date:** [August 2, 2026, 10:44pm UTC](https://discourse.codinghorror.com/t/why-are-all-discussions-on-this-blog-closed/10147/13 "2026-08-02T22:44:09Z")

</div>

> [@codinghorror](#):
>
> Some Discourse instances auto-close all topics {x] days after last response, or {x} days after the topic is posted, which is fine, but I’d prefer not to do that and have not enabled either of those settings.

I’ve always hated that with a passion because I regularly do searches where the top result takes me to a closed Reddit (or other forum) discussion that’s got incorrect information in it or is missing certain critical information. The only real option is to start a new post referencing the old post, but that of course won’t be found by anybody doing a web search; they’ll just never have any indication that updated information is available.

There are certainly times you’d want to close dicussions, but “it’s too old,” implying “there’s no possibility of new information about this” is almost invariably not a correct one.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://discourse-cdn.codinghorror.com/user_avatar/discourse.codinghorror.com/codinghorror/32/36371_2.png) [@codinghorror](https://discourse.codinghorror.com/u/codinghorror)\
**Post date:** [August 4, 2026, 6:12am UTC](https://discourse.codinghorror.com/t/why-are-all-discussions-on-this-blog-closed/10147/14 "2026-08-04T06:12:34Z")

</div>

Never? Even after 50 years? We haven’t really invented The Long Now on the internet yet.. this is still very much near the beginning of the Big Bang as far as digital network information is concerned..

[![image](https://discourse-cdn.codinghorror.com/uploads/default/original/3X/9/0/902813a2059af459fef50a8e163d731103dbf9c9.jpeg)](https://science.nasa.gov/mission/wmap/wmap-overview/)

I _do_ agree with you in general, but I’m not sure we are thinking far enough ahead.

---

<div class="post-metadata">

**Author:** ![cjs](https://discourse-cdn.codinghorror.com/user_avatar/discourse.codinghorror.com/cjs/32/79351_2.png) [@cjs](https://discourse.codinghorror.com/u/cjs)\
**Post date:** [August 5, 2026, 6:07am UTC](https://discourse.codinghorror.com/t/why-are-all-discussions-on-this-blog-closed/10147/15 "2026-08-05T06:07:14Z")

</div>

Certainly after just 50 years. My working NEC PC-8001 that I still use was introduced in 1979, and I have sitting just to my left a Sharp MZ-80K, the updated model of a computer first made in 1978. I’ve probably got two dozen computers from the early '80s that I still use, program and build accessories for regularly.

The Long Now is an interesting idea, and if we want to do that sort of thing for computing, looking at what we used five decades in the past is probably a good place to start, since that’s when the things we use now really started to gel. (E.g.: the first 128 characters of Unicode; the character sets that would contribute to other parts of it; the general ‘feel’ of our modern CPUs; packaging of consumer computer systems; …)

---

<div class="post-metadata">

**Author:** ![codinghorror](https://discourse-cdn.codinghorror.com/user_avatar/discourse.codinghorror.com/codinghorror/32/36371_2.png) [@codinghorror](https://discourse.codinghorror.com/u/codinghorror)\
**Post date:** [August 5, 2026, 11:44pm UTC](https://discourse.codinghorror.com/t/why-are-all-discussions-on-this-blog-closed/10147/16 "2026-08-05T23:44:17Z")

</div>

Bear with me here, because I’m not going Full Long Now here, _no one should ever go Full Long Now_, but there is some truth to really obsolete technical discussions (say, about a Sound Blaster ISA) not really _needing_ any new replies, and if someone _did_ bring it up today it would be under radically different conditions, and thus should be a new question.

If it was a question about _human behavior_, that has definitely a longer timeline. But even then.. is a 200 year old post about human behavior in a specific area – an area that may not even exist any more – still relevant? It’s complicated. What writing is _absolutely timeless_ such that it should be open to answers and replies _forever?_ I can point to some examples, for sure. But it’s a pretty small fraction of the overall total of writing.

Also, **reducing a massive attack surface of {x million} open questions is no small thing**. You want to absolutely minimize your attack surface, all the time, in every way you can. I don’t mean be obsessed with it, just, this particular one seems like a bit of low hanging fruit to me.

---

<div class="post-metadata">

**Author:** ![cjs](https://discourse-cdn.codinghorror.com/user_avatar/discourse.codinghorror.com/cjs/32/79351_2.png) [@cjs](https://discourse.codinghorror.com/u/cjs)\
**Post date:** [August 5, 2026, 11:59pm UTC](https://discourse.codinghorror.com/t/why-are-all-discussions-on-this-blog-closed/10147/17 "2026-08-05T23:59:41Z")

</div>

> [@codinghorror](#):
>
> …there is some truth to really obsolete technical discussions (say, about a Sound Blaster ISA) not really _needing_ any new replies…

You are coming across (to me, anyway) as quite dismissive of some people’s hobbies, such as writing games for early '90s PCs.

Let’s turn it around: say someone says that there is “some truth” that both your blog and this discussion board do not need new posts and we should disable all new posts to both. How does that make you feel? Do you think that abandoning Coding Horror and starting a new blog and discussion board is a reasonable thing to ask of you?

And no, most things about how you program the original Sound Blaster cards have not changed in the past thirty-five years. We are (especially the demoscene guys) discovering new stuff about it still, but that’s only because more time has been put into it. We’re still getting new demos for the Commodore 64 today that were unimaginable just ten years ago, despite no changes to the hardware in that time (or in the thirty years before that). It’s not clear when, if ever, things like this will be entirely panned out from a creative point of view, but it’s certainly not after just a few decades.

> [@codinghorror](#):
>
> Also, **reducing a massive attack surface of {x million} open questions is no small thing**.

It doesn’t seem to be an issue for Stack Exchange, which has exactly those millions of open questions.

I’m not saying that there’s no value to reducing this “attack surface,” but I think you are _massively_ undervaluing how much allowing amendations to old information does to get correct answers to people. There are plenty of top results on Google that are Just Wrong and have no real prospect of being fixed because no new discussion will ever catch up to the popularity and linkage of the old and closed one.