to lift or not to lift
Nov. 13th, 2010 12:53 amIn short, I came to a conclusion that while lift is the best technology for a web app, it is not worth it for a web page. E.g. I just want a service that takes a query, returns a response. Functionality inside. Why would I need lift with forms, session tracking, etc? I'll just use servlets, and will write them in Scala, and that would be it.
Update. Oh, okay, can go to sleep. Unlike lift... just got tomcat, got all the stuff from Burak Emir, configured ant.properties, fixed one line in Burak's code dating 2007 (ancient history, by Scala scale) - and lo and behold, have a .war file, deployed it, and it runs.
Small joys.
(Among other events, my check was bounced by my bank. First time in my life. Had to write an email to the artist to whom I wrote the check... in short, hope he'll join our barbecue tomorrow...)
Update. Oh, okay, can go to sleep. Unlike lift... just got tomcat, got all the stuff from Burak Emir, configured ant.properties, fixed one line in Burak's code dating 2007 (ancient history, by Scala scale) - and lo and behold, have a .war file, deployed it, and it runs.
Small joys.
(Among other events, my check was bounced by my bank. First time in my life. Had to write an email to the artist to whom I wrote the check... in short, hope he'll join our barbecue tomorrow...)