On Mar 6, 5:28 pm, David Pollak feeder.of.the.be...@gmail.com wrote:
Back in 2005-2006 Ruby and Rails were not easy to
get started with.
My first Rails checkins in our VCS are from 2004. I had no trouble at
all getting things running back then and don't remember hearing a lot
of complaints
Business wise, rails / php etc are not even on the same scale as lift. Rails /
PHP etc are cheap, easy ways to deploy *sites*. Lift is for building serious
*web applications*. there is a distinct difference... and yes, for these
reasons no doubt the higher cost of deployment will scare some
On 6 mar., 06:43, cageface milese...@gmail.com wrote:
Like many other web developers, I abandoned some heavyweight Java web
frameworks about 6 years ago for Rails and have been working pretty
much exclusively in Rails ever since. However, I've always had a
secret lust for functional
It intentionally avoids putting code in the template. This keeps the template
clean... Putting code inside the template is one of the worse design
decisions ever. Putting template fragments inside Scala code makes tremendous
sense as it allows a truly flexible way of achieving
A few notes from my behalf. I understand Tim's perspective and I fully
agree with, but this is a perspective of a guy coming from Lift side
which is likely to differ from the perspective of a new comer.
1. I definitely do not agree with something like here is why you
should use A and not B thus
Thank you for writing your comments. As most have said in the thread,
honest feedback is valuable if not essential and often hard to come
by, so please don't be put off by the odd negative response.
I'm fairly newbie here too and share some of your concerns about
Lift. For what it's worth I
I'm overall very impressed by the community response so far to this
post. My first reaction to this was, please don't dismiss it (like
the first response seemed to).
Marius was quick to agree that the web site needs some work. I have
to agree here. I am surprised by a few things:
1. So much
On Mar 6, 11:35 am, David Pollak feeder.of.the.be...@gmail.com
wrote:
Please allow me to rebut your thoughtful post.
I'm really glad to see David taking a more reasoned response to this
criticism compared to the early responders . . .
Okay... sorry... but this is a gratuitous swipe. Ugly ==
On Mar 6, 12:05 pm, cody koeninger c...@koeninger.org wrote:
How long had that getting started document been broken before it got
fixed (assuming it's fixed now)?.
It's still broken.
To the OP, taking the time to explore lift further is worth it if
you're doing i18n / comet or just want to
Okay... sorry... but this is a gratuitous swipe. Ugly == Not Easy to Use.
Nope. Sorry. I don't buy this.
Maven commands that wont copy and paste correctly == Not Easy To Use.
Im not sure it is difficult to copy and paste:
mvn archetype:generate -DarchetypeCatalog=http://scala-tools.org/
On Mar 6, 12:20 pm, Timothy Perrett timo...@getintheloop.eu wrote:
Im not sure it is difficult to copy and paste:
mvn archetype:generate -DarchetypeCatalog=http://scala-tools.org/
Its one line... easy. Im not saying maven does not suck, but this is
one the wiki home page people...
When I try
If you're using TextMate you can navigate through your snippets/models quite
easily - I've implemented a nifty little feature:
http://www.youtube.com/watch?v=MXMh_uoeeTs
Now I know this is only for TextMate but I'm sure it wouldn't be too big a
hassle to implemented in whatever editor/IDE you
On Mar 6, 2:20 pm, Timothy Perrett timo...@getintheloop.eu wrote:
Okay... sorry... but this is a gratuitous swipe. Ugly == Not Easy to Use.
Nope. Sorry. I don't buy this.
Maven commands that wont copy and paste correctly == Not Easy To Use.
Im not sure it is difficult to copy and
This thread is another nice example of the kindly atmosphere within
the Lift community!
It's already late so I don't want to join the discussion in detail ;)
The only thing I'd like to add to the documentation talk is that I'd
really appreciate to have an up-to-date aggregated scaladoc of all
On Sat, Mar 6, 2010 at 12:13 PM, cageface milese...@gmail.com wrote:
On Mar 6, 9:35 am, David Pollak feeder.of.the.be...@gmail.com wrote:
Back when I was doing Rails, the state of Rails' documentation was not
materially different from the current state of Lift's documentation with
the
On Mar 6, 7:28 pm, David Pollak feeder.of.the.be...@gmail.com wrote:
Another failing of Rails is the community. The Rails community is a
significant detractor to adoption outside of the young hip kids.
The rails community is a significant detractor to adoption even among
young hip kids. . . I
I think I understand David's point about letting Lift sell itself for now,
rather than pushing for more widespread adoption, until the right time comes
At the same time I would like to mention that it seems to me (not based on
any experience) than Jonathan Mawson has very good marketing sense /
Also, someone was lamenting GitHub's flat wiki. Assembla has a more advanced
wiki system but David said it's not worthwhile to move unless someone will
take on the role of managing the wiki.
On Sat, Mar 6, 2010 at 10:44 PM, Naftoli Gugenheim naftoli...@gmail.comwrote:
I think I understand
I think with its power and number of developers, Lift can have a
better home page. At least better than this because it only has one
developer:
http://nitrogenproject.com/
--
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email
Yes we know ... we are working to change the Lift website but it's
going slower than I expected to.
On 6 mar., 08:34, ngocdaothanh ngocdaoth...@gmail.com wrote:
I think with its power and number of developers, Lift can have a
better home page. At least better than this because it only has one
20 matches
Mail list logo
