C’mon — you’re @programming.dev. You’re supposed to know why this is bad.
C’mon — you’re @programming.dev. You’re supposed to know why this is bad.
I’m bringing chili
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.
Never gets old
Alphabetical index — ACAB
Go ahead; .world is getting too big anyway.
IIRC you are required to connect to internet to continue the setup process in newer versions.
OP was never seen again.
Nix installs packages independently of what’s been installed, so you’ll get the exact same result if you skip 0 updates or 500.
What the fuck, US?
Also, it appears said prosecutors are here and downvoting this.
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:
I can’t tell if this is Poe’s law or not.
Flaked NixOS unstable
I’m blind, sorry
No NixOS?
nix run nixpkgs#firefox
Netcat, mostly