• Ephera@lemmy.mlEnglish
    5·
    14 hours ago

    I kind of love the idea of the ternary operator. C is all about being a procedural language, except this is of course a lie, because it does have mathematical expressions.

    But then they realized that it’s not just mathematical expressions where being purely procedural is kind of shit, so they wanted to introduce if-else expressions.

    But oh no, we can’t have it look like the if-else control flow element. This is where madness functional programming lies. Let’s make it look like a mathematical expression instead, by choosing the ugliest syntax known to man.

    But what really makes it a meme is that other languages decided they needed to look like C, so they copied this terrible design and even though JavaScript has almost nothing to do with C anymore, webdevs in particular get to suffer from the unreadable syntax all the more.

  • Schmoo@slrpnk.netEnglish
    3·
    13 hours ago

    You can have my ternary operator when you pry it from my cold, dead hands.

    • SeductiveTortoise@piefed.socialEnglish
      5·
      6 hours ago

      return true === (a === b) ? true : false

      Now that I think of it, the return of false should be a casted integer. Just to add horror.

  • MistressRemilia@lemmy.sdf.orgEnglish
    3·
    18 hours ago
    # I mean, Crystal does have a ternary operator, too...
bar = case something
      in "aaa" then true
      in "bbb" then false
      end

foo = if bar
        69
      else
        42
      end

    ;; Or CASE or IF or COND or whatever
(let* ((bar (ecase (something)
              (:aaa t)
              (:bbb nil)))
       (foo (if bar 69 42)))
  )
    • Sv443@sh.itjust.worksEnglish
      1·
      3 hours ago

      I’ve been called slurs before for using immediately invoked anonymous function expressions with switch cases in JS

      const [val1, val2] = (() => {
  switch(whatever) {
    case "foo": return [1, 2];
    case "bar": return [3, 4];
    default: return [0, 0];
  }
}))();
    • ricecake@sh.itjust.worksEnglish
      5·
      18 hours ago

      Yeah, the problem isn’t “conditional expressions”, it’s “terse syntax”, and operator rules that you need to just memorize because they’re special and different. Also being limited such that you need to nest the extremely deeply if you, for whatever, you need to have a complex inline condition.

      I like the case expression , although I mostly know it from erlang.