5 ms·
Very interesting write up. Updating things is non-trivial as often you may depend on something that will eventually decide to deprecate a feature you actually u
by a1o 3y ago
Very interesting write up. Updating things is non-trivial as often you may depend on something that will eventually decide to deprecate a feature you actually used or some library/framework will decide to completely redo their API every five to ten years and then you suddenly have to start an upgrade in your project and try to keep this transparent to your users so things doesn't change for them or you need to figure some path to deal with backwards compatibility.
There are always an assorted amount of chores the more the project ages and has active users, these tasks often end up invisible as they don't get a featured spot in the release notes.
- matmair 3y agoChoosing the right dependencies is a craft that needs to be learned. I find myself looking into the ppl. behind libraries more and more. I will always prefer something striped down from a known person in the space to the solution of a newcomer. Hoping between APIs every few years gets old fast.
- a1o 3y agoIn my mind I was specifically thinking of SDL doing the 2 to 3 transition, not really a newcomer. I also experienced this in the WebView transition from Qt4 to Qt5. I also still remember the python 2 to 3 transition in the beginning. There are definitely more cases of a very established library/framework breaking things.
- matmair 3y agoQt updates (especially when using something like PySide additionally) are always rough. I waited long enough with Python that the tooling for the switch got good. Large breaking changes luckily seem to happen less in the python ecosystem. There is a lot of movement in the dev-tools currently but CPython seems to really focus on gradual improvements - which I appreciate a lot.