Re:Playground Wisdom: Threads Beat Async/Await
by do_not_redeem on Friday November 22, 2024 @09:58PM
(#42218879)
In case you missed it, the author was mocking the ivory tower that you're so proud of having locked yourself inside.
[ Parent
| on HN ]
Re:Playground Wisdom: Threads Beat Async/Await
by binary132 on Friday November 22, 2024 @10:48PM
(#42219066)
Thank goodness Captain Imperative scampered out of his goto hovel to remind us wizards to feel bad for being better than everyone. ;)
Re:Playground Wisdom: Threads Beat Async/Await
by do_not_redeem on Saturday November 23, 2024 @12:17AM
(#42219326)
Your purely functional insults have no side effect on me, wizard.
Re:Playground Wisdom: Threads Beat Async/Await
by binary132 on Saturday November 23, 2024 @12:59PM
(#42222354)
Argh, right in the monads!
Re:Playground Wisdom: Threads Beat Async/Await
by zeendo on Friday November 22, 2024 @10:20PM
(#42218974)
What is with the unprovoked condescension?
I guess I get the article author was trying to be provocative but what are you doing?
Re:Playground Wisdom: Threads Beat Async/Await
by mrkeen on Saturday November 23, 2024 @07:27AM
(#42220556)
To lay it all out in full:
TFA wrote out a bunch of problems with imperative code asked you to take it on faith that imperative is not inferior to functional. Then he added a bunch of snark, implying that functional programming is just a superiority complex (which is what I quoted).
I quoted the snark to indicate that I was very aware that the author was mocking FP.
serbuvlad asked why you can't just X. I linked to the exact function that does that for you.
do_not_redeem then suggested I was unaware that the author was mocking FP.
Re:Playground Wisdom: Threads Beat Async/Await
by the_mitsuhiko on Saturday November 23, 2024 @09:35AM
(#42221092)
FWIW I (author) didn’t want to mock functional programming. I consider myself an aficionado of functional programming patterns :)