cross-posted from: https://lemmy.blahaj.zone/post/31679150

proportional reaction

all 19 comments

sorted by: hot top controversial new old
[–] 18 points 1 year ago (3 children)

Meanwhile Rust, where every control flow has a return value

  • source
  • hideshow 3 child comments
  • [–] 14 points 1 year ago (1 child)

    its not my fault return apple == red ? true : false is so cute. :3

  • source
  • hideshow 1 child comment
  • [–] 10 points 1 year ago* (1 child)

    That

    return a === b ? true : false

    Is bothering me way too much. Just

    return a === b

  • source
  • hideshow 1 child comment
  • [–] 9 points 1 year ago
    [–] 9 points 1 year ago

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

  • source
  • [–] 7 points 1 year 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.

  • source
  • [–] 5 points 1 year ago

    TypeScript library devs are shivering in cold sweat right now

  • source
  • [–] 5 points 1 year ago

    Ternary operators are the one thing I really miss from Go.

  • source
  • [–] 5 points 1 year ago* (last edited 1 year ago)

    ternary operator rules though

  • source
  • [–] 5 points 1 year ago (4 children)
    # 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)))
      )
    
  • source
  • hideshow 4 child comments
  • [–] 8 points 1 year 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.

  • source
  • parent
  • [–] 6 points 1 year ago* (2 children)

    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];
      }
    }))();
    
  • source
  • parent
  • hideshow 2 child comments