411
every worthwhile link on how to implement your own squeeblerizer is dead and approximately 40% archived
(files.catbox.moe)
show transcript
compiler-specific posts:
every software is like. your mission-critical app requires you to use the scrimble protocol to squeeb some snorble files for sprongle expressions. do you use:
- libsnorble-2-dev, a C library that the author only distributes as source code and therefore must be compiled from source using CMake
- Squeeb.js, which sort of has most of the features you want, but requires about a gigabyte of Node dependencies and has only been in development for eight months and has 4.7k open issues on Github
- Squeeh.js, a typosquatting trojan that uses your GPU to mine crypto if you install it by mistake
- Sprongloxide, a Rust crate beloved by its fanatical userbase, which has been in version 0.9.* for about four years, and is actually just a thin wrapper for libsnorble-2-dev
- GNU Scrimble, a GPLv3-licensed command-line tool maintained by the Free Software Foundation, which has over a hundred different flags, and also comes with an integrated Lisp interpreter for scripting, and also a TUI-based Pong implementation as an "easter egg", and also supports CSV, XML, JSON, PDF, XLSX, and even HTML files, but does not actually come with support for squeebing snorble files for ideological reasons. it does have a boomeresque drawing of a grinning meerkat as its logo, though
- Microsoft Scrimble Framework Core, a .NET library that has all the features you need and more, but costs $399 anually and comes with a proprietary licensing agreement that grants Microsoft the right to tattoo advertisements on the inside of your eyelids
- snorblite, a full-featured Perl module which is entirely developed and maintained by a single guy who is completely insane and constantly makes blog posts about how much he hates the ATF and the "woke mind-virus", but everyone uses it because it has all the features you need and is distributed under the MIT license
- Google Squeebular (deprecated since 2017)
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.
I interpreted it as needing to be part of the build chain
Then I'm learning GNU Scrimble for job security and never documenting it fully lol.