"Useless Ruby sugar": Argument forwarding

Re:"Useless Ruby sugar": Argument forwarding by djur on Friday November 24, 2023 @05:36PM (#38409157)

> the state of the art in JS has so evolved as to make further such work mostly unnecessary, or so I infer from its more-or-less absence over the last decade or so at least. That Ruby still requires such explainers be published in 2023

async/await was introduced in 2017. If you're suggesting that this required fewer "explainers" than a set of gradual changes to Ruby method call syntax, I'm afraid we're not operating under a common understanding of reality.

[ Parent | on HN ]

Re:"Useless Ruby sugar": Argument forwarding by lamontcg on Friday November 24, 2023 @07:12PM (#38409818)

Kind of funny -- if I understand this correctly -- that Javascript was descended from Scheme which has delimited continuations and yet Javascript has async/await and function coloring nonsense, while ruby has continuations and fibers and doesn't need to worry about "function coloring" or "callback hell".

(Which I don't understand very well because I was a ruby programmer for 12 years, so missed all the async/await/callback-hell nonsense entirely that everyone is so obsessive about these days)

[ Parent | on HN ]

Re:"Useless Ruby sugar": Argument forwarding by remexre on Friday November 24, 2023 @09:19PM (#38410562)

I don't believe Scheme as standardized has delimited continuations, only call/cc; it's just that Scheme implementations have often been the laboratories in which experiments on delimited control have been performed.

[ Parent | on HN ]