I think you said it yourself here, “hope that in time it will be ready.” That is why I hadn’t started any work on Helix. I figured it was a distinct possibility that Twitch, like any software development shop, may have had challenges in delivering on such a huge undertaking and would fall back to the previous working version. I have dealt with this type of decision a lot in my professional job and I appreciate the fact that Twitch understands that the development community would like a decent amount of time to interact with Helix first once it does solve the use cases that they want to promote and, I imagine, is closer to feature parity with v5. This also is better for them, if they extend out the v5 time, it also means more time for people to start to work with Helix and give them a longer UAT (I consider us the users) time period.
1 Like