Agreed, shared mutable state is generally a PITA. Then again, it can occasionally be very valuable if correctly used and controlled.
Case in point, the disruptor pattern achieves some amazing performance metrics through use of shared mutable state, as do certain lock-free algorithms and software transactional memory. Are these solutions that we want to categorically rule out of a programming language? On 23 November 2011 20:06, Fabrizio Giudici <fabrizio.giud...@tidalwave.it>wrote: > On Wed, 23 Nov 2011 20:51:46 +0100, Simon Ochsenreither < > simon.ochsenreither@**googlemail.com <simon.ochsenreit...@googlemail.com>> > wrote: > > Hi, >> >> are you sure we are talking about the same language? It pretty much reads >> as if you are arguing against dynamically typed languages... >> >> dynamically typed language like scala, php, or whatever >>> >> >> >> Scala is statically typed, and yes, it takes the type stuff a bit more >> seriously than Java, too. >> > > Probably a bit too much. BTW, I didn't understand yet whether this thread > was yet another discussion about Scala, or about Stephen's blog post. > > I haven't read the blog post, as 102+ answers are just unreadable. I did > attend Stephen's presentation (not really because I'm interested in Scala > or Fantom, but because I never attended a talk by Stephen). Overall, it was > very interesting. After a short exchange with Mario Fusco, I understand > that some criticisms about Scala were probably too shallow. In the end, > though, I appreciated one of Stephen's conclusions, that Scala is overkill > on typing and that just a few of current programming problems with Java are > about typing. Thus there's some overengineering in a useless area. OTOH, > while some aspects of Fantom are interesting, I don't feel much > enthusiastic about it (still, I don't think Stephen wanted to give it a > push, but just have a comparison with Scala). Definitely, it's interesting > that with Fantom you can't have shared mutable state, if I understood well, > and this is a real area of troubles, where I'd appreciate some care by the > language. > > > -- > Fabrizio Giudici - Java Architect, Project Manager > Tidalwave s.a.s. - "We make Java work. Everywhere." > fabrizio.giud...@tidalwave.it > http://tidalwave.it - http://fabriziogiudici.it > > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to javaposse@googlegroups.com. > To unsubscribe from this group, send email to javaposse+unsubscribe@** > googlegroups.com <javaposse%2bunsubscr...@googlegroups.com>. > For more options, visit this group at http://groups.google.com/** > group/javaposse?hl=en <http://groups.google.com/group/javaposse?hl=en>. > > -- Kevin Wright mail: kevin.wri...@scalatechnology.com gtalk / msn : kev.lee.wri...@gmail.com quora: http://www.quora.com/Kevin-Wright google+: http://gplus.to/thecoda <kev.lee.wri...@gmail.com> twitter: @thecoda vibe / skype: kev.lee.wright steam: kev_lee_wright "My point today is that, if we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent": the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger" ~ Dijkstra -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javaposse@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
