On Wed, Oct 22, 2008 at 2:50 AM, efleming969 <[EMAIL PROTECTED]> wrote:
> > Most questions in the group are technical and I apologize if this is > not appropriate, but I I'm curious about how members are justifying > their use of Scala+Lift vs. a traditional Java architecture. I > understand if you are creating applications for your own business or > personal use, but what about employee or consulting work (if any). > > I'm currently a one man consultant and would like to do more work with > Scala and Lift but it seems high risk for my client to have an > application built with newer and practically unknown technologies like > these. > > Any thoughts? High risk? High risk of what? Compared to doing it in Java? I always say that the thing of uttermost importance is to stay competitive in the market, and if you want to stay competitive, you'll have to be daring. Using Scala+Lift over Java/Struts2/JSF/whatnot most likely means less than half time-to-market. And that means lower development-costs, better ROI and more possibilities. But I guess that's nothing compared to feeling really secure. So perhaps they should go for COBOL + COBOL On Cogs. ;) Cheers, Viktor > > > -- Viktor Klang Senior Systems Analyst --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" 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/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
