Skip to content
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

Windows 7 caveat missing from last release as it's not supported (due to nw.js) #976

Closed
4 tasks done
Porkepix opened this issue Aug 6, 2023 · 7 comments
Closed
4 tasks done

Comments

@Porkepix
Copy link

Porkepix commented Aug 6, 2023

Checklist

Streamlink Twitch GUI version

Not relevant

Streamlink version

v2.3.0

Operating system, environment and configuration details

Windows 7

Description

Latest release (2.3.0) doesn't start anymore on Windows 7. After some search it appears that nw.js was compatible with Windows up to release 0.72.0 and therefore latest Streamlink Twitch GUI uses one that's more recent and thereore note supporting W7 anymore.

Maybe it wasn't seen on the version choice, or maybe it was intentional; either way I think it deserve a caveats in the release.

That means that W7 users are stuck on release 2.2 and for that reason, it would seems relevant to do a caveat in the future release of Streamlink that would require Streamlink Twitch GUI above version 2.2 to work.

Debug log

No response

@bastimeyer
Copy link
Member

I was aware of this, but I forgot to include this in the changelog.

Chromium has ended its support for Windows 7, 8 and 8.1 in its 110 release, which was in February this year:

Streamlink Twitch GUI v2.2.0 was based on Chromium 105. v2.3.0 is now based on Chromium 115.

Windows 7 has been unsupported for over 8.5 years now, with its extended paid security support having ended 3.5 years ago. Microsoft's support for Windows 8.1 has run out this year, shortly before Chromium did, which is why Chromium waited until then:

That means that W7 users are stuck on release 2.2

I honestly don't care. If this is an issue for anyone using an outdated, unsupported and insecure operating system, then they can fork and build the application themselves.

Going to update the changelog and release notes now.

@bastimeyer
Copy link
Member

2a44dc4

@Porkepix
Copy link
Author

Porkepix commented Aug 6, 2023

Just to make it clear, it wasn't a critics or anything for the drop of support, I found out the drop of support for nw.js as shown above, but did so the hard way (just a side computer running W7 I don't use for anything important, and never cared enough to update, but it so happens I sometimes put streams there).

But it's completely legit for me to drop that support.
It's just that I think it deserved to be notified as a caveat in the release.

My guess is that anyway the support will probably drop soon for streamlink too, which already needed some specific release of python to run on W7 and therefore its own releases (though I just checked and 3.8 still have a little bit more than one year of support. Wouldn't have bet it was still supported when there was already 3 others major releases since).

@bastimeyer
Copy link
Member

I will stop publishing py38 based Streamlink releases once supports ends by the Python devs, which will be next year:
https://peps.python.org/pep-0569/#lifespan

I already commented on that on the Streamlink issue tracker. It's just copying a few extra checksums for me when managing and building new releases, so it hasn't bothered me much.

@bastimeyer
Copy link
Member

No idea about the bundled FFmpeg though. If something breaks there, then I will drop py38 Streamlink releases sooner

@eldepor
Copy link

eldepor commented Aug 19, 2023

Callin w7 "old" and removing support for it is the most stupid shit ive ever seen. I wont upgrade. Period.

@bastimeyer
Copy link
Member

bastimeyer commented Aug 19, 2023

Windows 7 has been unsupported for over 8.5 years now, with its extended paid security support having ended 3.5 years ago. Microsoft's support for Windows 8.1 has run out this year, shortly before Chromium did, which is why Chromium waited until then:

That means that W7 users are stuck on release 2.2

I honestly don't care. If this is an issue for anyone using an outdated, unsupported and insecure operating system, then they can fork and build the application themselves.


Callin w7 "old" and removing support for it is the most stupid shit ive ever seen. I wont upgrade. Period.

Good luck with that.

Locking the thread.

@streamlink streamlink locked as resolved and limited conversation to collaborators Aug 19, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants