tag:blogger.com,1999:blog-5135517.post868527001691075556..comments2023-11-05T03:54:44.710-08:00Comments on Making it stick.: Whatever Happened to Patterns?Patrick Loganhttp://www.blogger.com/profile/02088461489050417591noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5135517.post-4811261733468945332008-08-08T16:30:00.000-07:002008-08-08T16:30:00.000-07:00The greatest achievement of the GoF book was to sh...The greatest achievement of the GoF book was to show how useful is the pattern format, giving a way for software development communities a common way to express their best practices. Of course, the practices of the 90' have some shortcomings on 2008, but the whole pattern movement is invaluable.<BR/>Some time ago, I also did a <A HREF="http://gabrielsw.blogspot.com/2007/07/yes-design-patterns-are.html" REL="nofollow"> post in defense of patterns </A>Anonymoushttps://www.blogger.com/profile/17525961934302794120noreply@blogger.comtag:blogger.com,1999:blog-5135517.post-3525275179285082542008-08-08T03:36:00.000-07:002008-08-08T03:36:00.000-07:00Amen!But the poster is also right about OTP. The ...Amen!<BR/><BR/>But the poster is also right about OTP. The interesting aspects of Erlang are not in the language itself, which is rather clunky compared to other functional languages, it's in the OTP framework. <BR/><BR/>OTP applies a lot of patterns for designing fault-tolerant, distributed systems. The patterns themselves are really hard to learn from OTP, and OTP would be much easier to learn if those patterns were documented somewhere.Nat Prycehttps://www.blogger.com/profile/14593335423887511402noreply@blogger.com