You guys both have very valid points. Lift is still stabilizing API's for a month or two (AFAIK) till 1.0 which is to be a pre-alpha or maybe alpha release? (this needs TBD)
I can imagine that from adoption part there is still a lot of reluctance especially in Java space because: 1. People need to learn Scala (I'm so glad that more and more people are willing to) 2. People need to learn Lift and I tend to think that this is a quite fast process comparing to other frameworks even if Lift's documentation is kind of lacking in many respects. 3. From versioning perspective not being yet an Alpha/Beta/GA (you name it) may be a question mark as things are not fully stable yet (I'm referring to API's). In reality if people are willing to dig in they will find outstanding things. Still with all these "caveats" I would choose Lift over any other Java web framework anytime. Selling this to companies or even corporates to adopt it over the oversold (Spring, Struts, JSF etc) it very tough. But regardless, more and more commercial applications are written in Lift (AFAIK). My 2 cents ... Br's, Marius On Oct 22, 12:37 pm, "Warren Henning" <[EMAIL PROTECTED]> wrote: > On Tue, Oct 21, 2008 at 5:50 PM, efleming969 <[EMAIL PROTECTED]> wrote: > > but it seems high risk for my client to have an > > application built with newer and practically unknown technologies like > > these. > > I'm kind of a Lift outsider but this isn't all that Lift-specific in > my view, it's a more general concern about using new technology that > hasn't gained much traction yet, which is something I have experience > with. > > I think I understand where you're coming from. It's always scary to > venture into the unknown. Using new technologies, you can feel as if > very quickly after "hello world" you hit a dirt road and you're on > your own to work things out. However: > > 1. If you think about it, in a typical web application, the web > framework will only be a small part. The rest (the application server, > database, DNS server, load balancers, spam filters, ...) are still the > same. I for one think your choice of relational database, for > instance, is of far greater consequence than the web framework(s) you > choose. > > 2. David Pollak is one of the most experienced, intelligent guys in > the industry. He is ideally suited to the task of writing a web > framework. > > As I see it, Lift takes proven infrastructure and integrates it using > ideas derived from years and years of hard-won, real-world experience. > > Also, doesn't a good test suite help things a lot? If Lift doesn't > work the way it ought to, your tests should be able to expose that in > a meaningful way. > > From your perspective, at the present time probably the biggest thing > to be aware of is that the Lift API is not finalized and breaking > changes happen more often than they do with mature projects. > > Warren --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
