On Fri, Jan 31, 2014 at 4:58 AM, Rakesh <[email protected]> wrote:
> The idea of telling the client where to go next is very powerful to me > (its basically a state machine right?) but its complicated to > implement and new territory for the devs (me included). > I think this is the crux to me. It is more complicated to implement with no clear benefit long term for many projects. What do you vision as the long term win from doing this? I think you have to focus on that, and try to bring it closer to the present. And realize that your argument may equate to telling people it is better not to take out a mortgage on a house if you can afford it. This is almost certainly true, but the up front costs are not something you can always ignore. Or is it a lot cheaper to do this "the right way" than I have been led to believe lately? -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/javaposse. For more options, visit https://groups.google.com/groups/opt_out.
