3 ms·

That's a good example. But as you hint at: managing the content for that is probably pretty annoying for how simple it is.

• danso 11y ago
  What I meant was that it may have started out as cumbersome (i.e. someone's Word document)...but hopefully by now they've moved it to a spreadsheet-like format. Given that Macrumors is a well-established site, I wouldn't be surprised if it wasn't baked into their CMS as some kind of module...though it really could be done as a set of spreadsheets (or YAML) and then as a static site. How long would it take to research every iPod-era-and-onwards Mac product line -- including dates of refreshes/announcements? I bet no more than a day...especially if you just start from the Wikipedia page, which needs some cleaning up of taxonomy, but is pretty good (and relatively machine-parseable): https://en.wikipedia.org/wiki/Timeline_of_Apple_Inc._products https://en.wikipedia.org/wiki/Timeline_of_Apple_Inc._product... There is definitely some editorial decision making that needs to be done about how to best classify things. But the Apple product line is pretty small, so the number of decisions -- e.g. should "iPod classic" and "iPod touch" be separate "families"/product-lines -- is relatively small. After you have a list/spreadsheet of product-lines and dates...then it's not hard to write a script that calculates the number of days between each subsequent release...which gets you much of the main utility of the Macrumors' guide: days since last release, and average days per cycle. (it'd actually be kind of cool to see this done with the major programming languages...)