196

In my experience, the c library also depends on several additional libraries which is fine except it needs version 5.0+ of a library that you're already using 3.4 of. The APIs for the library have been significantly changed, a function in the library that you heavily use has been deprecated, and upgrading to use it is more work than just implementing the desired feature yourself. The manager who suggested the library thinks you are overstating the amount of work using it will require and thinks technical debt is the money he still owes the Indian subcontractors.

Someone's clearly confused GNU Scrimble, and Scrimble for Windows, a fork of GNU Scrimble which makes no changes to the program itself, but has an overcomplicated installer that provides a stripped-down MSYS2 environment which only includes GNU Scrimble's direct dependencies (which turn out to be about 90% of a full MSYS2 install, excluding only the package manager, update system, and a few key Unix tools you'll only realise aren't present if you start using Scrimble Bash as your daily Bash shell and run a script that uses a POSIX-mandated but rarely used utility, and also awk for some reason, which causes problems squeebing certain file formats until you download an awk binary from the upstream MSYS2 project).

As a true Unix Philosophy application, GNU Scrimble itself wouldn't integrate extra features that should clearly be standalone applications like a Lisp interpreter, Pong implementation, or wide file support. Instead, it calls the existing Lisp interpreter, Pong implementation, and various tools to convert file formats into intermediate text representations that can be parsed through an unholy mix of grep, sed and awk that all GNU-based operating systems must always provide. After all, it's better somehow to call a bash script that runs some awk snippets so your dependencies are only expressed at runtime than it is to link with libjson-glib.so.

Bro forgot Squeeb4J