TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Memory Models: A Case for Rethinking Parallel Languages and Hardware (2010)

54 pointsby wheresvic1about 6 years ago

3 comments

ameliusabout 6 years ago
Since this is about parallel languages, why don't they say anything about Erlang and related languages?
评论 #19295101 未加载
Tojotabout 6 years ago
The article says a lot about <i>concurrent</i> programming, but little about <i>parallel</i> programming.<p>The naming is misleading.
评论 #19294620 未加载
评论 #19294444 未加载
评论 #19294231 未加载
bullenabout 6 years ago
I think there are two ways forward; larger L1 caches or split memory between cores, both have their problems.<p>To solve what this article argues about though, you can use my internet platform: <a href="https:&#x2F;&#x2F;github.com&#x2F;tinspin&#x2F;rupy" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;tinspin&#x2F;rupy</a><p>Java has excellent concurrency and non-blocking implementations.<p>Since it also has the only class-loader that is worth using, it&#x27;s the only programming language you can use for server-side joint parallel future proof systems today.