Sunday, October 08, 2006

[Event] JAOO Conference Day 3

Hot Old Ideas - Experiences Of An Old Country Programmer (“Pragmatic” Dave Thomas)

Nice track introduction and an overview which concepts of programming models and languages he has encountered in his life. The reason to know about the history of computer science is, that a lot of ideas were there before but are sometimes forgotten. So sometimes you have to look back to know what could be right today ...

The History of Scheme (Guy L. Steele Jr.)

Introduction to Lisp and its concept of lists and where it was flawed. He then continues to present how Scheme (which original name was Schemer, but the files on his machine only had 6 characters ...) was born and how he discovered that Lamda Functions are functional equivalent to the actor based messaging concept.

Functional Programming And Monads (Erik Meijer)

Haskell is back and with Eric it made a lot of sense once more. For him, because he has a small brain, Haskell was the ultimate language because it represents the ultimate DRY language. He also explained why an experienced Haskell developer never ever writes recursive functions (as I did in the university course long time ago), you can always write folding functions and Lamda functions which work directly on the lists. His advice was, because we have already stolen the work from the mathematicians of the last 2000 years, the best thing to do is to train new ones because otherwise we will run out of ideas ...

Are We There Yet? (Rod Johnson)

Rod told the story how Spring come to life because the JEE concept was totally flawed 2003. Spring was the answer of the community and it fixed completely what IBM, Sun, BEA and others nether got right (because the smart people where never build real applications). The next big thing for Enterprise Java is to focus on the domain model, which should once again really be object oriented and not a dump structure which is only used for state management and as transfer structure between the DAO and the service layer. He has also a wonderful example why the interceptors in EJB3 are totally crap and showed that with Spring 2.0 and AspectJ it is a lot more elegant to inject aspects in the domain model.

Five Considerations for Software Architecture (Kevlin Henney)

Kevlin told something about five considerations for good and elegant architecture, which, as every fundamental truth, was discovered with the help of beer. He explains all five with a lot of anecdotes, but basically the idea is that if the architecture is flawed you never get a project right, independent from tools, languages or platforms you use.

How Will We Be Programming In 2016? (Dave Thomas, Guy L. Steele Jr., Erik Meijer, Kevlin Henney, Ole Lehrmann Madsen, Steve Vinoski)

Because the panel was stopped after the beer was gone, it lasts only for an hour. But all of them agreed in the following points: Concurrency and Distributions of programs will largely increase and had to be supported by tools and language features, programs and the problems they solve will get more complex and we need more tools for analyzing, deploy, test and monitoring them, DSLs will evolve but not everyone is a good language designer so most of them will be rubbish, development is language agnostic, so it doesn't matter in which language you solve the business driven problem.

powered by performancing firefox

No comments: