New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Future development #367

Open
vinszent opened this Issue Jun 3, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@vinszent
Owner

vinszent commented Jun 3, 2018

A lot of you may have noticed that the development pace has slowed down a bit since the last release. The main reason for this is Twitch constantly burning devs with changes to their already unstable APIs and causing GT to break constantly.

Then at the beginning of the year they announced that they are planning on axing their existing API and replacing it with another one. This new API only has a fraction of the functionality that the old one has and in it's current state would render GNOME Twitch and similar applications unable to function.

The response from Twitch has also been non-existent (see here) and many devs are worried, including myself, about what the future for 3rd party applications will be. I'm somewhat suspicious that this is indeed a move to stop applications such as GT and forcing users to access Twitch via their crappy website...

So I will be putting GT on somewhat of hiatus until Twitch releases more information on what their plan is as I don't want to sink a lot of time into something that might be dead in a few months anyway because of them.

I will be looking at the Twitch dev forums and outlets everyday for updates and as soon as they announce something positive, I'll get right back into development. Until then v0.4.2 should work in its current state, at least until 31 December 2018 when Twitch has announced to finally remove the API for good.

@ptkato

This comment has been minimized.

Show comment
Hide comment
@ptkato

ptkato Jul 7, 2018

If Twitch indeed do axe their API, what will be done about GT code? Reshaped into something else, maybe?

ptkato commented Jul 7, 2018

If Twitch indeed do axe their API, what will be done about GT code? Reshaped into something else, maybe?

@vinszent

This comment has been minimized.

Show comment
Hide comment
@vinszent

vinszent Sep 19, 2018

Owner

It seems like Twitch has decided to delay the end-of-life of their current API https://discuss.dev.twitch.tv/t/twitch-api-update-delaying-v5-end-of-life/16277. While this doesn't solve all of the issues I listed above, it does alleviate some concern I had with continuing development.

I've been wanting to rewrite GT in a more maintainable language for a while (see #199). So I will take the opportunity to slowly migrate from the current C code base to Rust which is quite mature at this point, has good community and corporate support and already as usable libraries for GLib (GTK+, GStreamer, etc) libraries. Plus it integrates well with C, so I can rewrite parts one at a time.

So look forward to more stuff coming soon!

Owner

vinszent commented Sep 19, 2018

It seems like Twitch has decided to delay the end-of-life of their current API https://discuss.dev.twitch.tv/t/twitch-api-update-delaying-v5-end-of-life/16277. While this doesn't solve all of the issues I listed above, it does alleviate some concern I had with continuing development.

I've been wanting to rewrite GT in a more maintainable language for a while (see #199). So I will take the opportunity to slowly migrate from the current C code base to Rust which is quite mature at this point, has good community and corporate support and already as usable libraries for GLib (GTK+, GStreamer, etc) libraries. Plus it integrates well with C, so I can rewrite parts one at a time.

So look forward to more stuff coming soon!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment