[peterbmarks]

One problem of having old WWDC content available is that it is confusing for a developer searching for how to do something to be shown deprecated approaches. It's hard enough finding the right way to do something in Swift with all the old versions of the language around.

[saagarjha]

It’s hard enough finding a way of doing something. Apple doesn’t document anything. Instead they point you at WWDC videos which they take down after 5 years (or even less) that hold critical information needed to develop for their platform. If they want people to do things “the right way”, then they should document it properly instead of just pulling things arbitrarily or putting all their documentation in the form of videos.

[heavyset_go]

This. For the $100/year privilege to write software for their platforms, the documentation is atrocious.

[uhura]

Old WWDC content has a lot of value. They cover a lot of core technologies that Apple has no interest in covering and documenting again (because they deprecated and are removing old documentation instead of improving them...). The channel in question helped me a lot while trying to understand aspects of early-Cocoa.

The argument you've presented is more related to the way Apple handles the evolution of its software than about having old content laying around. Their current approach is far from good unfortunately. During OS X Lion days, Xcode documentation was so rich that even core concepts of the OS were covered.

Having a structured way to keep those informations readily available is very important to help us preserve software history. And Apple is not helping...