

YAMPA, hmm maybe i should make that
YAMPA, hmm maybe i should make that
Just gotta invoke skynetctl
ret
urn from subroutine, int3 would be something relating to interrupts off the top of my head.
Might want a sled and a ROPe to have a smooth descent
Huh, I was about to correct you on the use of embarrassment in that the intent was to mean a large amount, but it seems a Wiki edit reverted it to your meaning a year ago, thanks for making me check!
'tis how LLM chatbots work. LLMs by design are autocomplete on steroids, so they can predict what the next word should be in a sequence. If you give it something like:
Here is a conversation between the user and a chatbot. <insert description of chatbot>
<insert chat history here>
User: <insert user message here>
Chatbot:
Then it’ll fill in a sentence to best fit that prompt, much like a creative writing exercise
Containers, the concept that Docker implements, lets app developers give a self-contained environment for distribution. For devs that means consistency in deployments across environments, which in turn means sysadmins can deploy each of these apps as fully isolated units.
With that, you get really clean installs/updates/uninstalls, and your deployments get done with a well-defined, declarative definition file which can also handle multi service dependencies (a la Docker Compose/K8s)
Ahhh the comment misspelled it, yep that’s the one. Thanks!
I find it funny it didn’t point out Active Directory
Oh that just made it click in my head why they would do it as sign, exponent, mantissa and not sign, mantissa, exponent. I mean yes I’ve been taught it’s for sorting purposes, but this really helped it fit better. Thanks!
Rust has an RFC that wants to consider yeet as a keyword for throwing an exception, I think they’re currently keeping it as a placeholder just in case
Not particularly, most of my use has been on a desktop or laptop 😅
DWService is a favourite of mine. One self-contained program to run on the target, and a web-based interface to interact with it
All good, thanks for the explanation! :D
Ah, so is it right to say it’s an abstraction of how functions are sequenced? I could kinda see that idea in action for I/O and Async (I assume it evaluates functions when their corresponding async input is ready?)
The way I understood monads is they’re a way to abstract the “executor” of a function. I/O monads run step-by-step based on stdin, List runs a function on every element, and the function is unaware of this, Option runs the function if the value exists (again the function’s not aware of this)
That being said, I’m coming at this from a Rust view, and I’ve only scanned through one guide to monads so I may be wrong
I would actually bring a parallel to the device driver-firmware blob split that’s common with hardware support in Linux. While the code needed to run inference with a model is straightforward and several open source versions exist already, the model itself is a bunch of tensors whose behaviour we don’t have any visibility into. Bias is less a problem of the inference code and more an issue with the data it was trained on