Sleep(Math.random()+1)
Select_Traffic_Lights()
Sleep(Math.random()+1)
Select_Traffic_Lights()
Also, researchers asking ChatGPT for long lists of random numbers were able to extract its training data from the output (which OpenAI promptly blocked).
Or maybe that’s what you meant?
I’m both, I say fuck all the time. I fuck on and off the clock.
It’s surprisingly possible (and easy) too… a little bit of tinkering with X11’s compositor API would probably do the trick.
IDK about Wayland tho :/
I’ll point to how many functional languages handle it. You create a type Maybe a
, where a
can be whatever type you wish. The maybe type can either be Just x
or Nothing
, where x
is a value of type a
(usually the result). You can’t access the x
value through Maybe
: if you want to get the value inside the Maybe
, you’ll have to handle both a case where we have a value(Just x
) and don’t(Nothing
). Alternatively, you could just pass this value through, “assuming” you have a value throughout, and return the result in another Maybe
, where you’ll either return the result through a Just
or a Nothing
. These are just some ways we can use Maybe
types to completely replace nulls. The biggest benefit is that it forces you to handle the case where Maybe
is Nothing
: with null, it’s easy to forget. Even in languages like Zig, the Maybe
type is present, just hiding under a different guise.
If this explanation didn’t really make sense, that’s fine, perhaps the Rust Book can explain it better. If you’re willing to get your hands dirty with a little bit of Rust, I find this guide to also be quite nice.
TLDR: The Maybe
monad is a much better alternative to nulls.
Remember kids, always use protected branches.
I use Nix, so I’ll just reinstall my system if anything really bad ever happens. Sometimes I reinstall just because. My important files are on a delegate drive I have to manually mount, so I’m not too worried.
Trailing slash lets you do this though: