Hey Stefan, sorry, yes I do indeed mean Unique Selling Point. Cheers, Tim
On Aug 8, 4:16 pm, Stefan Scott <[email protected]> wrote: > I usually can figure out new acronyms ... but "USP" had me stumped. > > Even after googling, nothing applicable came up. > > I was unsure if it refers to a technology ... or maybe it's just > shorthand for a common English phrase. > > Finally I thought "unique sales point" might be a common English > phrase ... and then I found "unique selling proposition" online. > > So "USP" = "unique selling proposition"? > > On Aug 8, 10:49 am, Timothy Perrett <[email protected]> wrote: > > > > > ivo, > > > The Bespin story (likewise forhttp://cappuccino.org/) is one of > > integration with Lifts comet support etc... both those technologies > > are all based on Javascript runtime (as is GWT) so you need to think > > in more abstract terms; when we talk about integration with a client > > side technology, we [the team] usually refer to integrating Lift's > > main USPs with said technology. For example, making sure the comet > > support works OOTB etc. > > > Bespin (and to that end, Thunderhead) are amazing toolkits for client > > side dev, and any integration done with Lift will purely be to ensure > > that our USPs work in a very seamless way - its not to say that if > > there isnt "integration" with a technology you want you cant use lift, > > its just that some we'll supply and some we wont. > > > Does that help? > > > Cheers, Tim > > > On Aug 8, 2:00 pm, ivo <[email protected]> wrote: > > > > So without surprise I realize that my doubts about JQuery come of my > > > lack of experience with it, but in contrast my experience with GWT is > > > that one really "forgets" about the generated javascript code. It is > > > small, performant and it just works! If one adds SmartGWT to the > > > picture, one gets tons of useful widgets, and with GAE one gets a > > > persistent backend and an object model that can be shared between > > > server and client. All this is what I was calling the full-stack. > > > > Nevertheless there are disadvantages, one of them being the incredible > > > amount of code one has to write specially for the client (because in > > > the server one can use Python or Scala as alternatives to Java.) > > > Another important disadvantage is vendor lock-in. > > > > But again, my curiosity was triggered by the Bespin + Lift project. > > > What is that all about really? How can we compare it to JQuery + Lift, > > > or GWT, or other? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
