Kevin

I feel like that’d defeat the purpose of having redundancy in case the main instance itself goes down 🤔

For the record, you have sent me back on a nostalgia trip for 2016 memes and music edits

Thank you

As an Indian myself this makes me happy :D

He did eventually take one later on, which I can imagine must’ve been a bit of a painful decision ;-;

Bach Lava Balaklava

Android has an Enterprise feature that allows devices to have an isolated “Work” profile from their Personal profile, complete with separate accounts and apps (though your device IDs are still likely shared due to it being the same device)

There’s this project called Island that allowed anyone to set it up on their own devices

From a maintainability standpoint, absolutely. Computers have gotten fast enough to let programmers optimize for developer time instead

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

Goddammit.

Ah I figured I had that one wrong, thanks!

Because systemd (the project) extends more than just systemd (the init system). It also includes things like:

• systemd-journald (system logging)
• systemd-timesyncd (Network Time Sync)
• NetworkManager systemd-networkd (network interface/connection management)
• systemd-homed (Home directory management)
• systemd-resolved (DNS Resolver)

and so many more

Now, in my personal opinion, I do find it good in that these being under one umbrella project led to fairly good integration between these aspects of “system management” as a whole. But I do also concede that this may feel like too many responsibilities handled by one project

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