17 ft ladder, s/hidden
/style="overflow: hidden; height: 0"
/
17 ft ladder, s/hidden
/style="overflow: hidden; height: 0"
/
15 ft ladder:
<div hidden>
<?= rand() ?>
<?= rand() ?>
<?= rand() ?>
<?= rand() ?>
<?= rand() ?>
<?= rand() ?>
<?= rand() ?>
<?= rand() ?>
<?= rand() ?>
<?= rand() ?>
<?= rand() ?>
<?= rand() ?>
<?= rand() ?>
<?= rand() ?>
<?= rand() ?>
</div>
13 ft ladder: <span hidden> guid </span>
NixOS and your family is always welcome to come over and your family is always welcome to come over for the weekend and friends are in my life and your dad will have a few minutes to be there by noon or something else but I’m not the one who is going for the weekend
189cbca
refactor
425b7de
increased bullshitry levels
33bc72d
works on my machine
f5fe8ed
who the fuck cares
112e7ff
probably did more shit
c02191c
updater cool factor
101% complete
Ctrl+Alt+Tab on Windows / Ctrl+(iirc)F9 on KDE is pretty cool too
I’d believe Shift+Left and Shift+Right, but I doubt most programs support multicursor.
♪ It’s the ciiircle of shiiiiiiiit ♪
Prism has a counter for total time you’ve had Minecraft running.
Simple; take a picture of yourself to hold a circular reference.
Netcat, mostly
Genocide or more genocide? Difficult choice…
Nix has flakes; nix run
can contain pretty much all of the needed dependencies. If that’s not enough, you can set up an entire container as a module.
Yep, parentheses force {}
to be interpreted as an expression rather than a block — same reason why IIFEs have !function
instead of just function
.
The inspector REPL evaluates as a statement-with-value (like eval
), so the {}
at the beginning is considered an empty block, not an object. This leaves +[]
, which is 0. I don’t know what would make Node differ, however.
Edit: Tested it myself. It seems Node prefers evaluating this as an expression when it can, but explicitly using eval
gives the inspector behavior:
Flaked NixOS unstable
Mint where?