On Tue, Oct 21, 2008 at 5:50 PM, 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
On Thu, Oct 23, 2008 at 2:43 PM, David Pollak
[EMAIL PROTECTED] wrote:
The folks at Twitter love Scala and say so publicly.
Off-topic: are you at liberty to discuss the extent of Scala usage at
Twitter? What, if anything, can you tell us?
Did they replace Rails with Scala/Lift?! :D
Warren
On Thu, Oct 23, 2008 at 2:47 PM, Warren Henning [EMAIL PROTECTED]wrote:
On Thu, Oct 23, 2008 at 2:43 PM, David Pollak
[EMAIL PROTECTED] wrote:
The folks at Twitter love Scala and say so publicly.
Off-topic: are you at liberty to discuss the extent of Scala usage at
Twitter? What, if
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
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
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
Wow, thanks for the feedback.
I should have been more clear as to what I meant by High Risk. I'm
not concerned so much with Lift's technical merit, but rather the risk
of personnel. If I get hit by the proverbial bus then my client/
employer will have a difficult time completing/maintaining
On Wed, Oct 22, 2008 at 4:30 PM, efleming969 [EMAIL PROTECTED] wrote:
Wow, thanks for the feedback.
I should have been more clear as to what I meant by High Risk. I'm
not concerned so much with Lift's technical merit, but rather the risk
of personnel. If I get hit by the proverbial bus
+1 Viktor. In troubled economic times such as these, its in the
business interest to run as efficiently as possible - in short, more
productive programmers... what you said is bang on.
Cheers, Tim
--~--~-~--~~~---~--~~
You received this message because you are
I'd also like to say you should pick a technology that meets your goals.
Lift/Grails/Django/Rails/Seam/JSF/Spring/Struts (etc..) have their own
quirks and if you try to deviate too far from the paradigm, you'll run
into them quickly.
For me, (so far) Lift is really amazing at doing quick ajaxy
+1
Let's not forget that Scala is growing more and more may Java people
are looking for alternative maybe because they are bored of anonymous
classes, dubious oversold design patterns, stereotypes and coding
cliches. Of course a language purely by its existence do not solve
these problems BUT
11 matches
Mail list logo
