Hacker News new | past | comments | ask | show | jobs | submit login

Why does the author backport fixes to the 1.5 and 1.6 versions? What's significant about recent changes that makes those worth keeping alive?



They mention one reason in the release notes:

> unintended SSE CPU requirement present in previous releases has been removed.


Removing that requirement makes sense to me (in the current release or the previous releases), but I'm curious why the previous releases are deemed worth maintaining alongside the current release.

What did they do feature-wise in newer versions that makes the old versions desirable to some people, to the point that a user would prefer to upgrade them rather than upgrade to the newest version? It's not about system compatibility: the 2.x line supports Windows all the way back to Windows 7.

I'm content to dig into the docs but I was wondering about people's personal experiences with it. One hint in the release notes is that some, but not all, old plugins work in the new version...


1.5 is the last version that supports Windows XP.

1.6 is the last version before the big rework.


> It's not about system compatibility: the 2.x line supports Windows all the way back to Windows 7.

I wouldn't be surprised if a decent amout of people were still running Windows XP, esp. on old hardware.


I don't know how many, but it's a decent enough choice for a jukebox machine or something.


Yeah almost certainly plugin ecosystem




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: