this post was submitted on 15 Nov 2025
18 points (100.0% liked)

badposting

740 readers
118 users here now

badposting is a comm where you post badly


This is not a !the_dunk_tank@hexbear.net alternative. This is not a !memes@hexbear.net alternative. This is a place for you to post your bad posts.

Ever had a really shitty bit idea? Joke you want to take way past the point of where it was funny? Want to feel like a stand-up comedy guy who's been bombing a set for the past 30 minutes straight and at this point is just saying shit to see if people react to it? Really bad pun? A homemade cringe concoction? A cognitohazard that you have birthed into this world and have an urge to spread like chain mail?


Rules:

  1. Do not post good posts.
    • Unauthorized goodposting is to be punished in the manner of commenting the phrase "GOOD post" followed by an emoji that has not yet been used in the thread
    • Use an emoticon/kaomoji/rule-three-abiding ASCII art if the rations run out
  2. This is not a comm where you direct people to other people's bad posts. This is a comm where you post badly.
  3. This rule intentionally left blank.
  4. If you're struck for rule 3, skill issue, not allowed to complain about it.

Code of Conduct applies just as much here as it does everywhere else. Technically, CoC violations are bad posts. On the other hand: L + ratio + get ~~better~~ worse material bozo

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] 30_to_50_Feral_PAWGs@hexbear.net 7 points 1 month ago (1 children)

OK, so like...

  • 0 == "0" is true because the script interpreter recognizes that the integer form can be cast to a string value, and then it compares both values as if they were strings.
  • 0 == "\t" is true because a string consisting of only whitespace characters is trimmed down to an empty string, which is considered "falsey." Numeric zero is also "falsey," so both values are cast to booleans for comparison purposes.
  • 0 == [] is the same story -- an empty array is also falsey, so both the numeric zero and the empty array are cast as booleans when they are compared.
  • None of these comparisons work between the string-form zero character, the tab character (or blank, non-empty string), or the empty array because fuck you, that's why.

If you want to get into heresy, here are some excerpts from The Satanic Verses:

  • Boolean(0) == Boolean("") returns true, but Boolean(0) == Boolean("\t") returns false.
  • Boolean(0) == Boolean("0") returns false.
  • Boolean(0) == Boolean([]) returns false.

The Boolean builtin constructor seems to go off of string length instead of mimicking the == operator's automatic cast behavior.

[โ€“] miz@hexbear.net 4 points 1 month ago

because fuck you, that's why

this should be the name of a good podcast