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)
  • AnyOldName3
    4•5 hours ago

    The documentation was totally clear that calling squeeb would do that, and the official sample code only called squeebWithACondom for that exact reason except for one sample specifically illustrating the remote impregnation feature. It’s not Squeeb4J’s fault that third parties made tutorials with security holes, and it was irresponsible of the tech press to blame them. It wasn’t Dennis Ritchie’s fault when people demoed exploits in software that passed user-provided format strings to printf in C, everyone accepted it was the application’s fault for using printf irresponsibly.