"Killed" is accurate; I don't know of anyplace to find those. And honestly, being as old as it is, you aren't doing yourself any favors with it. VS Code is the go-forward experience and – I was resistant at first – it's totally worth the short learning curve. I'm massively more productive in it.
Don: I've been using PowerShell ISE, but I've now heard you and Jeff Hicks mention switching over to VS Code. What is it about using that tool that's that much better than just using PowerShell ISE? As you mentioned you're way more productive in it. Why?
Where do I start? Vastly better IntelliSense. VASTLY better debugging integration. Better automated code formatting (and reformatting). Cross-platform (I use a Mac). Also edits Markdown documents (which I write Help in, yay PlatyPS). The ISE is a hover board; VS Code is a Tesla. VS Code also has a better scoping mechanism than the ISE, which always created debugging problems for me.
You obviously need the PowerShell plugin and whatever other coding plugins you like (Markdown), but you can add all that super easy once VS Code is installed.
VSCode is the way to go. It rocks once you get powershell configured for it. They are also not developing Powershell ISE any longer. It's still supported but will not be part of powershell moving forward. Powershell for Windows 5.1 was the last release of powershell for windows. Powershell 6 (Core) does not include a built in IDE and is cross platform.