Peter Drake, he/him, LFHCfS 🔥 @peterdrake@social.cleverlibre.org

@WiseWoman Yes: https://www.consumerreports.org/

@khird Good advice.

I'm not just concerned about the future life cycle of the item. I'm trying to avoid buying things that will immediately prove worthless for their intended purpose.

@fool You can buy "monitor chow", and should probably have a can next to your monitor monitor.

@lowqualityfacts Huh, that's odd -- the image displayed by Mastodon for the link is from a completely different clip. The link works, though.

@lowqualityfacts I give you the deepest of pulls.

https://getyarn.io/yarn-clip/fa09a06f-4b21-4cb8-a09a-c3e51965e6b8

@freemo Marriage?

@alcinnz I've only taken a cursory glance, but a similar use of special glyphs came up in

https://www.uiua.org/

which was just mentioned by @vanderZwan.

@futurebird Apologies if I'm telling you things you already know, but since you asked...

"The normal way" is infix (2 + 3), as in C, Java, and Python. Polish notation is prefix (+ 2 3), as in Lisp. RPN is postfix (2 3 +), as in PostScript, Forth, and old HP calculators.

I've heard that it's only called "Polish" because English-speaking mathematicians couldn't pronounce "Łukasiewicz", but that may be apocryphal.

Bonus tidbits:

It is argued that both prefix and postfix are better than infix, because you don't need parentheses or operator precedence rules. * + 2 3 4 is unambiguous, but without precedence rules 2 + 3 * 4 could mean (2 + 3) * 4 or 2 + (3 * 4).

Ironically, Lisp is mocked for seeming to consist entirely of parentheses. (This is because the previous statement doesn't hold with variable-arity functions.)