Hacker News Reader

Comment by lvass | Hacker News Reader

I dislike it because it's kinda hard to understand (can't really say I did) specially without any context, and programming language release notes are something people should read even a hundred years afterwards.

View on HN

I totally disagree with your opinion. I liked it because I found it easy to read (both in skim and in depth, as well as backwards), didn't require additional context (title was included), and programming release notes capture the historical context of the release (where refugees are subject to extreme NIMBYism in our day and age).

Why should programming language release notes be something people should be able to read in a hundred years?

Secondly, why does adding this section affect that even if you think that?

I'm curious about the circumstance leading to reading Python 3.12 release notes in 2123.

Isn't it obvious? Someone's "temporary hack" stopped working, and even though it's not been important enough to refactor for the past 100 years it's important enough to drop everything right now to fix when it breaks.

PL research and reverse engineering or just fixing compatibility. Say you want a program from 3.6 era but the 107 year old interpreter doesn't quite suit you and the newest one broke something, and you bisect interpreter versions to find 3.11 to 3.12 broke it.

Multiplanetary species that has merged with AI thanks to neuralink-esque tech discovers a bug in the brains of 5% of the population. Turns out the bug is due to Python 3.12 which was used to write the natural language understanding (NLU) engine of the brain chips.

We have Fortran code from several decades ago defining scientific domain knowledge. The next Einstein formula may require 3.12 to run.

I'm curious what aspect of the poem you don't think will be relevant in a century from now?

Reply on news.ycombinator.com