To add it is the "without replacement" part that was overlooked. Not having a replacement makes this one unique and maybe a bit out of touch and unrealistic. Why only now; It has become necessity to deal with the deprecations once they actually arrive and normally one drops in the "replacement". Especially if one is running multiple projects for clients that need value driven updates. Looking at frameworks with plenty developers, those have many depreciation notices as well.