On Sun, Sep 12, 2010 at 12:10 AM, Liam Knox <[email protected]> wrote:
> I like the idea but its not what I see that happens in practice at least in > the financial sector. You rarely see the same modelling applied by 2 > systems even for very common aspects such as trades, cashflows or accounts. > Partly this is due to lack of attempt to synegize and time to market, but > often its as much that there are fundamental different views and > requirements in different systems. When you expand that to a whole sector > you then see its massively more complex. > > I'm not sure I follow how this argument goes against at least attempts of DSLs. Could you not use the same reasoning against basic OO modeling? I agree that it can be taken too far. Likely I do so all of the time. However, I have found the few times I tried that if I can reduce my main logic code down to a more declarative language for what should happen, it is a lot clearer for anyone trying to fix bugs (myself included) to not lose track of the intended behavior. Not to mention, it is amusing that the most complicated logic most developers I work with ever have to write, is already in a very declarative language (myself included). A "simple" select is probably performing more optimized code paths and data lookups than I care to understand. Imagine if we had to do those imperatively. -- 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.
