4 ms·
I gave it a skim and from that what I could conclude was that it focuses a lot on concurrent operations. Which I don't think comes to everyone's use.
by mesaframe 7y ago
I gave it a skim and from that what I could conclude was that it focuses a lot on concurrent operations. Which I don't think comes to everyone's use.
- naasking 7y agoIntegrating concurrency with mutability is a tough problem, and concurrency is becoming increasingly important.
- mesaframe 7y agoIt has always been important but again not for everyone. I would like a similar treatise but for synchronous single threaded operations.
- spinningslate 7y ago> it focuses a lot on concurrent operations It does but not to the exclusion of other computation models. I'd agree with GP - I found it a wonderful book. It builds different models of computation successively by incrementally adding features. It's a bit like SICP[0] in that it starts with declarative/functional fundamentals and brings in mutable state really late. The coverage of dataflow was the first one that gave me an "aha!" moment. It's easily 10 years since I bought it and I still dip into it every few months or so. Every time I do, I get something new: insights, deeper understanding, etc. Really wonderful book. [0] https://sicpebook.wordpress.com/ https://sicpebook.wordpress.com/
- riffraff 7y agoYes, I think concurrency is about 1/3 of the book, but it's approached the same way as the other paradigms; you have a basic language, add a single feature and see what happens: what new things can you do? How does the expressivity change? What problems arise? Is this equivalent to another paradigm? I found the insights interesting, but I would agree they are not of immediate utility to many people's day job.