Unfortunately, quite a bit of the web is at the mercy of not only Adobe, but also Sun (aka now as Oracle since they purchased it) for java and so on and so forth. We will always be subject to whatever their updates do to our web experiences be it animated site setups or scripts running Menus.
There are, however, many times that circumstances would render an update to a program (for anyone not just CC) to be too much hassle for it's worth and I would imagine that the Firestarter program falls into that category. Keep in mind that Firestarter has been around many many years and although it's had updates it's most definitely still old school in a lot of things and I would imagine updating it would require a total rebuild at this point. Maybe the rebuild is more of a project than they are wanting to take on right now?
Either way though, think about it in timely fashion and you'll realize that it doesn't matter if they retire it or not really. A fix would take a long time trying to work around Adobe's blunder, and then to have them fix their blunder would break CC's fix and so on lol. The main thing is that they couldn't do it fast enough to fix all the site animations that are broken right now. A rebuild could take months or even a year or more, fixing could also take months depending on what's broken.
This means that "retired" or not is irrelevant at this point, what matters is that it's broken and people just need to find an alternative or use the suggestions for the older version (stated incessantly in the other post that this should have been posted in instead of starting a new one lol).
A fix isn't the issue really, it just can't be done fast enough to accommodate anyone anyways, so retiring the program is the logical thing to do really. Even if they fixed it it would take a long time, and people's sites would still be broke, and it still wouldn't be CC's fault even though they would be trying to fix someone elses blunder.