On Mar 5, 5:59 am, Reinier Zwitserloot <[email protected]> wrote: > Am I missing something or have we been vastly overestimating the impact the > 'multi core future' will have on programming language design?
I agree with you. If you write web apps, the app server (and database, if they're on the same server) both take advantage of multiple cores. So your application already runs multi-threaded, and you "only" care about multi-core if you deal with database concurrency (deadlocks) or if you have some important shared state in memory that you need to lock. For example, I work on a program were we use JBoss Cache, and we use it in a way where we do the locking ourself (it's not thread-safe by default). They have some transactional model in it now, but it wasn't fully baked when we started and required some JTA libraries that we had trouble getting to work on Tomcat. It gets more complicated when your app is distributed and the shared state isn't in the DB - but do Clojure/Scala help you there over some third-party product with Java? -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
