Entertaining flag name!

React team seems to really have set a precedent with their "dangerouslySetInnerHTML" idea.

Or did they borrow it somewhere?

I'm just curious about that etymology, of course the idea is not universally helpful: for example, for dd CLI parameters, it would only make a mess.

But when there's a flag/option that really requires you to be vigilant and undesired the input and output and all edge cases, calling it "dangerous" is quite a feat!

▲

wrxd 3 hours ago | parent [-]

I’m pretty sure this comes from Claude code’s --dangerously-skip-permissions

▲

saulpw 3 hours ago | parent [-]

which sounds like it came from React's "dangerouslySetInnerHTML", per the comment you replied to.

	▲	brabel 14 minutes ago \| parent [-]
		I think people used similar prefixes for a long time. For example, Haskell has had `unsafePerformIO` since the 90's... and MSFT's Hungarian notation was also similar, though it used abbreviations for things like "unsafe" (not "dangerous"). Perhaps React was the most famous case of using "dangerously" though.