#like i can semi somewhat respect the FSF

[eggman-is-fat-mkay]

don't forget the rust crate segfaulting your program instead of returning an error if it tries to parse bad data because the underlying C library has a bug in it. someone wrote an issue on the rust crate's github but the dev was just like “the C code is well outside my jurisdiction. WONTFIX” with no link to a corresponding issue on the C side because libsnorble2 has not been developed in public for the better part of 5 years

there's also a separate rust crate caled rusquimble which is a pure Rust implementation of squimblization, but it advertises big about its flexibilty, which in practice means its API is about as user friendly as v1.0 hyper. it contains approximately 7000 structs, all of which are user facing, and a minimal hello world example is 50 lines of boilerplate in which you open all of the relevant files and asynchronous TCP connections yourself and then wrap them in 7 different structs from the rusquimble crate along with some enum variants with horrifyingly long names to tell them what to do, all of which have constructors which can fail, three of which are asynchronous for absolutely no reason, and one of which returns an error type that doesn't implement Display meaning that not even the anyhow crate can save you now.

Also it only supports async-std as the asynchronous runtime even though literally every other crate in existence has standardized on tokio.

don't forget the rusquimble crate having no documentation apart from that single 50 line hello world example and whatever else rustdoc was able to autogenerate, minus of course the handful of modules that the developers put #[doc(hidden)] on (which is about 80% of the API)

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)