Hey all, firstly thank you for everyone’s input. I know this is a hot topic and I appreciate everyone’s willingness to contribute to the conversation.
I don’t think what we’re proposing is a contentious change, so I’d like to make at least this bit perfectly clear in case there was any misunderstanding. We have every intention of supporting past functionality with the replacement we’re proposing. Use of the word “deprecating” may have sent the wrong message, since our plan is to replace this bit of API with something entirely more capable than just polling your services. The new API should be inclusive of all existing use cases while supporting a reactive model that we’d like to recommend going forward.
I’ve opened a GH issue and expect to start work on this change as soon as I reasonably can, which realistically should be some time this month. There’s something of a proposal written in there which I’m happy to refine/concretize if anything is unclear, but I think there’s enough there for others to chime in and provide feedback. I’m very interested in hearing if there are any gaps for existing use cases, so I encourage anyone to look and participate.