3 ms·
> I keep hearing this over and over. Hearing what? That pmap is a drop-in for map giving instant speed gains? That's odd. I've never heard that. Like anythi
by fogus 13y ago
> I keep hearing this over and over.
Hearing what? That pmap is a drop-in for map giving instant speed gains? That's odd. I've never heard that. Like anything pmap has its tradeoffs.
> poster child for lisp's success
You're conflating "functional programming" with Lisp.
> I think the whole multiple core thing is over blown
That's something that I would probably agree with. However, people tend to focus on that regarding Clojure because it provides more than one model for describing concurrent state changes. People get excited about that I suppose.
- dominotw 13y ago> That pmap is a drop-in for map giving instant speed gains? That's odd. I've never heard that. That was just an example of how programming without state makes it easy to scale it over multiple cores. > Like anything pmap has its tradeoffs. No one said anything about pmap being a drop in replacement for map. If pmap didnt have tradeoffs there wouldnt be a 'map' and just pmap.Common Sense. I am not sure why you are even mentioning that. As I said that was just an example of ease of writing multithreaded programs in clojure. Which was one of the main points in the blog post. Did you get a chance to read the blog linked to this post?