6mo ago

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

cross-posted from: https://lemmy.blahaj.zone/post/20883609

Curated Tumblr @sh.itjust.works

(⬤ᴥ⬤) @lemmy.blahaj.zone

6mo ago

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

Microblog Memes @lemmy.world

(⬤ᴥ⬤) @lemmy.blahaj.zone

6mo ago

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

196 @lemmy.blahaj.zone

(⬤ᴥ⬤) @lemmy.blahaj.zone

6mo ago

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

37 comments

libsnorble-2-dev, a C library that the author only distributes as source code and therefore must be compiled from source using CMake
Of the available options, this is easily the best since I can use my own compilation flags to tune the library for my specific target architecture/CPU which can possibly change as the deployment profile for the business case evolves. Assuming it's OSS, I can also fork and adjust the library itself for said "mission-critical" use case.
Also, the Google product being deprecated since '17 is too real 😅...
- Yup. If source is not available I’m not using it if I have any choice in the matter. Binary distribution is nice, but I’d rather have source.
  Plus I’m sure some kind soul has created a build pipeline that autogenerates binaries from the source. I can always either use that or clone and customize it. It’s a natural separation—as a dev I’d like my responsibility to end at “I merged working code to trunk”.
- And here I would argue that the Rust library is strictly better, specifically because it will come with an automated or precompiled build of the C library. Compiling C is such a pain.
  
  i just knew the fanatical rust fans would just have to push Sprongloxide. Broken records!
- Also, on Gentoo Linux, there will be an ebuild that integrates all of the cmake options into the rest of the packaging system and manage the dependencies
  
  Any similar system for Kubuntu 24.04 LTS noobs/normies like me? I don't know what "ebuild" is, but it sounds cool (of course, I could look it up, but I thought I'd just ask).
  I'm not a dev-ops dude, but for work, I develop parametric CAD solutions and generative DNNs for CAD. Lots of linear algebra and Pytorch on the GNU-Linux side; lots of Grasshopper for Rhino8 on the Win11 side. Hence, I use Docker to separate my experimental build environments from my production ones.
  I've been kinda maintaining my shit "by hand", so to speak, for years now, and I think I'm ready for some automation in that regard.
you folks are still scrimbling? hacker news says you can get much better results if you dronkle instead. in fact, you don't even have to worry about your implementation, just use the kneeb.io api for all of your dronkling (and scrimbling i guess via their legacy api deprecated last month). they just got seed funding and they reinvested that into their infrastructure. this is a no brainer!
- Seriously, it's like nobody in this thread even read the seminal paper, "Scrimbling Considered Harmful".
- You forgot to treat us like we're stupid and close the thread as answered
will it run on a turbo-encabulator?
- if you can find a turbo-enCOBOL sneeble implementation sure
- Lol I named my wifi this. No one gets it but me. 😢
  
  Probably distracted by all the side fumbling.
Yeah, writing your own squeeblerizer sucks, but there's no better option. GNU Scrimble can be used off-the-shelf as a passthrough, so the only real tasks are implementing Squeeb's algorithm and a sprongler; then, your entire pipeline is merely something like:

$ gscrimble --passthrough --args -- ./your_squeeb | ./your_sprongler
Edit: Whoops! Forgot to mention, GNU Scrimble also has Snorble support out-of-the-box, and Scrimble clients have content auto-negotiation, so your_squeeb can just take JSON on stdin. GNU Scrimble is really nice for this sort of thing, just...big.
And if you want to sprongle directly into a database or etc. then you can write your_sprongler to taste. Full disclosure: I have a fairly fast implementation of Squeeb's algorithm in rpypkgs. However, I'd really recommend writing your own; it's like twenty lines of code you can copy from Wikipedia and it'll give you a good basis for extending it with your own desired changes later.
You can read snorblite's code if you need to figure out a specific sprongling technique, but it's way easier to just go look up the original SprongCode from SprongReg. Use a search engine to get around the university's paywall. This gets you the SprongCode UUID and you don't have to read code written by a batshit fascist.
All accurate, except the Microsoft one. Microsoft makes you pay for enterprise development tools, but not for libraries.
- While you aren't wrong I think you're kinda missing the spirit of the joke.
- .NET ecosystem is filled to the brim with paid libraries tho.
  it's like, want to parse JSON? only 399 for enterprise use. i had never seen so many paid libraries until i worked at a .NET shop
  
  For what it's worth, in that specific example at least JSON parsing has been available as part of the base .NET libraries since .NET 3.
I'm trying to use emscripten to compile libsnorble to wasm so I can use it in an electron app but it's not working. Can anyone help me?
"Just use squeeb JS lol"
But squeeb.js can't squeeb snorbles with Windows line endings!
I feel like it's missing the perfect light weight version that appears to do everything you want. Except it's written in java, has not been updated for 4 years, and for some strange reason only works with oracle java.
- And, worst of all, it has a bug that slightly mangles output - except if running on Windows Vista.
  The Docker container has 10 million weekly downloads.
Snorblite for sure, fuck the ATF.
- So, while I agree on that part, the maintainer of snorblite is one step from getting shut down by the feds due to radical actions and an alleged affiliation to a known csa distribution network. As soon as he's brought in for questioning, all data tied to his machines will be deleted and we'll have to rely on forks of the library from previous versions with outdated dependencies.
  
  Not the first time and won't be the last, we'll endure.
Congratulations on squeebling meme of the week - this one really sprangled my sprongle
Snorblite, pecause I actally understand and can debug perl.
Libsnorble as a close second.
I'd probably do libsnorble and then snorblite, mainly just because I prefer C, don't mind source distribution and the rest sound cursed for one reason or another.
just fork snorblite
yay -S scrimble
what have I won?
- no, that's the old version of the GNU one
REAL
Oh no, a library you have to compile. Are you serious?

37 comments