The use of `class` for things that should be simple free functions

Re:The use of `class` for things that should be simple free ... by jcelerier on Thursday May 28, 2020 @07:58AM (#23336237)

> Users will suffer when the vendor is not replying as quickly as they would hope for (which is not a pleasant experience at all, specially if you run server software) or when they simply discontinue the software (cf thousands of games).

My experience as a Linux user is that I suffer even more from some minor update in /usr/lib/libwhatever.so suddenly breaking some feature in software that I use to do my job / have fun, which wouldn't happen at all if that software was self-contained.

[ Parent | on HN ]

Re:The use of `class` for things that should be simple free ... by jfkebwjsbx on Thursday May 28, 2020 @05:17PM (#23342776)

Being self-contained does not imply statically linked, though.

The benefit of dynamically linking is that you (as a user) or upstream (most likely) can fix those issues you point out, including future ones.

Being self-contained simply means updates aren’t forced into it, which is a good thing and I agree with it.

I didn’t downvote you, by the way, since the point you make is valid.

[ Parent | on HN ]