3 ms·

Slightly tangential, but I wish this blog would date its posts. Reading "If you're starting a brand-new application today, there are plenty of valid reasons to

Slightly tangential, but I wish this blog would date its posts. Reading "If you're starting a brand-new application today, there are plenty of valid reasons to write it in 2 instead of 3. There will be for a long time." on the same day it was written is not the same as 6 months or a few years down the lines. I don't actually know when this was written except for the copyright: 2014-2015, so it can't be more than a bit short of 2 years ago.

teraflop 11y ago
The Wayback Machine reveals that it was posted sometime after September 2015: http://web.archive.org/web/20150921221742/http://migrateup.com/python/ http://web.archive.org/web/20150921221742/http://migrateup.c...
seliopou 11y ago
I remember seeing a retweet in my stream a couple months ago where somebody made the suggestion of not dating blog posts so as to make them seem less ephemeral. I think the logic went that if the writing isn't tied to a single moment in time, then it'll become timeless. It's one of the more irrational and idiotic suggestions I've ever come across. One of, if not _the_ most important piece of metadata for anything that has or will ever exist is its creation date. In particular for writing, putting it in a historical context usually makes the piece more powerful and increases your understanding of the subject. If it's bad writing then it's not going to have a chance anyway. Sorry to say but that may be true of the post in question. I was under the impression that due to poor Python 3 adoption, Python 2.7 would continue to be supported. I second OP, please date your blog posts.
dogecoinbase 11y ago
"If you're starting a brand-new application today, there are plenty of valid reasons to write it in 2 instead of 3. There will be for a long time." This has been true for the last seven years, and I certainly don't see it changing anytime soon.

teraflop 11y ago

The Wayback Machine reveals that it was posted sometime after September 2015: http://web.archive.org/web/20150921221742/http://migrateup.com/python/ http://web.archive.org/web/20150921221742/http://migrateup.c...

seliopou 11y ago

I remember seeing a retweet in my stream a couple months ago where somebody made the suggestion of not dating blog posts so as to make them seem less ephemeral. I think the logic went that if the writing isn't tied to a single moment in time, then it'll become timeless. It's one of the more irrational and idiotic suggestions I've ever come across. One of, if not _the_ most important piece of metadata for anything that has or will ever exist is its creation date. In particular for writing, putting it in a historical context usually makes the piece more powerful and increases your understanding of the subject. If it's bad writing then it's not going to have a chance anyway. Sorry to say but that may be true of the post in question. I was under the impression that due to poor Python 3 adoption, Python 2.7 would continue to be supported. I second OP, please date your blog posts.

dogecoinbase 11y ago

"If you're starting a brand-new application today, there are plenty of valid reasons to write it in 2 instead of 3. There will be for a long time." This has been true for the last seven years, and I certainly don't see it changing anytime soon.