every worthwhile link on how to implement your own squeeblerizer is dead and approximately 40% archived

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

Obviously you use a half implemented java wrapper for libsnorble-2-dev that was a students practice project 4 years ago that they left public on github

No, no, it's fine -- I saw a Python2 sample squeeblimator that was never fully fleshed out. I just need to rewrite it... dodge the deprecations... use a few list comprehensions...

The next dev 5 years in the future: wtf is this?

I'm at the phase where I'm reading constant blog posts about how libsqueeb2 sucks with metrics supporting them but the guy writing the blog post is also writing libsqueeb3 but it hasn't seem an update for months. you really want to migrate to libsqueeb3 for various reasons but youre unsure about the state of the project, but for now you use libsqueeb2 while stalking this mysterious open source blogger

Ahah fuck it I’m taking the worst decision: I’m grabbing that hermetic spec, I’m cannibalizing every other implementation under the sun and I’m writing my own. Because you only live once

Oh God, I've come across this post trying to package Snorble for Windows as an Intune package, does anyone happen to know the switches to get it install silently?

Every time I squeeb a snorble it results in a lot of internal cursing when the sqawk doesn't compile and I get 50+ error messages.

sprongloxide might be the first rust crate i’ve heard of that’s reached version 0.9. my experience has usually been that the projects die and get forked due to infighting or loss of interest before reaching v0.6.

We need something like SI units in programming.

If I can easily call Squeeb.js from the command line, then I'm using it. I'm assuming this is something I need to do once and never again. That's my view of the hypothetical, at least. Definitely not using a c or rust library. GNU Scrimble is tempting. I honestly might try it first. I can just see myself getting lost and frustrated by the weird syntax of flags and lisp.

I'll probably have to sit there and remember how to install something to use through the command line from npm. I'll likely have an existential debate about whether it try yarn or not. I'll see where the project is now and if npm still sucks. Then I'll remember npx vaguely and try that. I'll get all of this set up and leave it in my rc files only to forget what it all is the next time I need to squeeb a snorble or use any Node cli stuff.