Ron Pressler - Pull Push: Please stop polluting our imperative languages with pure concepts-Curry On

Channel:Curry On! · Length:44:42 · Published:2015-08-06 · Views:24766

Watch on YouTube

Summary

Ron Pressler's Curry On 2015 talk arguing that imperative languages should not be polluted with pure functional concepts like monads. He favors simple blocking code over non-blocking styles.

Why HN recommends it

Recommended as the case for blocking code and virtual threads over monads and async/await.

one of my recent favorite videos generally on this topic has been from Curry On conference — HN, 2015

Programming language design · Functional programming · Software architecture & design

Subtitles (excerpt)

uh my name is Ron Pressler uh I'm the founder of parallel universe we make uh an open- Source server side uh stack for the jbm that helps you write uh very efficient applications um so the talk today is kind of messy it's going to be uh part Rand part opinion part some uh rehashing of old ideas um I am going to talk about functional programming and imperative programming I am not going to discuss the relative merits of the two uh but I am going to discuss the applicability of uh certain uh pure functional uh Concepts uh for imperative languages or rather lack the ra um and this entire talk is given from the perspective of an imperative programmer so I'm not going to use uh the right names for things or the names uh hasal gives them um and uh yeah we are we are going to discuss uh monads and I'm going to explain what they are uh and then uh why they're absolutely terrible not four for imperative languages for imperative languages they're excellent for uh pure functional um okay so as a motivation uh these are three classes uh from uh from the jdk this is a standard uh Java runtime liary um many of you must have heard that Java 8 now has lambdas uh it also has in the standard library at least three monads uh and uh this means that there are more

On Hacker News

Here are more arguments against async/await: [VIDEO] Ron Pressler always was an advocate for blocking code and even joined oracle to add virtual threads to the JVM, thus invalidating the performance argument of the async/await/non-blocking crowd. I really wish young developers would be taught about the actor model and communicating sequential processes before falling for the false promises of asy… — fzeindl, 2024-11
Does it shake out to any real advantage? To put it shortly: Writing single-threaded blocking code is far easier for most people and has many other benefits, like more understandable and readable programs: [VIDEO] The main reason why non-blocking IO with it's style of intertwining concurrency and algorithms came along is that starting a thread for every request was too expensive. With virtual thre… — fzeindl, 2024-07
> Or Java? Yes - that was implied in the same sentence where I wrote "(e.g. exceptions or actual compiler enforced error handling like Rust)." :-) > As far as I know, race conditions happen and leak out into production with Scala and Java. They do. But there are more techniques in those languages (such as immutable collections, as their type systems are actually able to model and implement them) … — apta, 2019-06
That's a fair point overall. It's basically the entirety of the debate between functional languages and imperative languages. Nonetheless, it is still pretty good question as far as someone trying to understand the differences and why it might be useful. @hmehta, one of my recent favorite videos generally on this topic has been from Curry On conference [1]. It's not strictly data-flow vs control … — elcritch, 2015-11

Related videos