NireBryce

reality is the battlefield

the first line goes in Cohost embeds

๐Ÿฅ I am not embroiled in any legal battle
๐Ÿฆ other than battles that are legal ๐ŸŽฎ

I speak to the universe and it speaks back, in it's own way.

mastodon

email: contact at breadthcharge dot net

I live on the northeast coast of the US.

'non-functional programmer'. 'far left'.

conceptual midwife.

https://cohost.org/NireBryce/post/4929459-here-s-my-five-minut

If you can see the "show contact info" dropdown below, I follow you. If you want me to, ask and I'll think about it.


lifning
@lifning

in 2030, JavaScript gains a ==== operator that is stricter than ===, needed due to an ambiguity introduced into the core language unilaterally by Google (despite Mozilla's objections) to unblock the launch of a short-lived webapp. The operator has no canonical pronunciation, devs disagree whether it's "quadruple-equal," "double-double-equal," or "actually actually equal."

in 2033, the PHP community, inspired by the discussions around having the choice between three different types of equivalence being good, actually and important to modern best practices, adds a !!= operator that is more lenient than ==, returning true when e.g. two numbers can be rounded to the nearest ten to become equal, or two strings consist of words with the same Latin root. The operator is pronounced "not NOT equal" in a defensive, pedantic tone of voice


NireBryce
@NireBryce

other programmers call ==== "double-double" and mockingly pronounce it like a turkey call


You must log in to comment.

in reply to @lifning's post: