As a native Russian speaker, may I advise German. Russian has all the grammatical complexity of German + non-Roman phonetics + Cyrillic alphabet + word order that's not prescribed, but has stylistic meaning.
Ppl, this is a low-fi piece journalistic trolling - the "subject matter" was growing a beard when I was a Moscow high school senior 20 years ago :).
Leaving aside the Russian tendency to take ill-informed pot shots at Americans (a national past time), cultural anthropology is an actual discipline with actual data to peruse - _lots_ of it - if you're interested. Curiosities of cultural interaction go far wider than the "happy fool/gloomy fool" non-dilemma here. ;)
- your value proposition is in the "it's XXX but you can get there for YYY". Put that front and center and give it a better visual treatment than the insufficiently anti-aliased black sans ;)
- the $10 sleeve makes you think hard where it's at right now. Move everything related to $10 only in one spot. The entire copy under "EXPERIENCED TRAVELERS HELP YOU SAVE TIME AND MONEY" could be compressed to a couple bullet points.
- "How do we do it" doesn't need to be on the front page - it distract from the goal of getting me to try
What's not mentioned (it's hard to sell) is, 50%+ of the reason Lift is so fabulous is, you're writing Scala. It's a mighty upgrade in quality of life, from either Ruby, Java or Python.
By corollary, what's being omitted is, the learning curve is steep. Scala isn't super-easy, and Lift dives fairly deep into the more complex stuff - implicits, currying, etc.
Nor is Lift itself all too well documented just yet. Yes, there's two books and a super-helpful community, but the experience is still in a different universe from the lavishly over-documented Spring MVC where you never really have to ask a question.
I was in a startup that built a MySQL/Spring/Wicket app, and I'm building a Mongo/Play one right now. So, point by point:
1) Java isn't amenable to pre-installed hosting like PHP is. You usually deal with machine images that you have to prepare yourself. Jetty 7 + Nginx is the going coin, it's quick and easy
2) Java is outright the best performing language of the ones currently used for web development with any degree of frequency (PHP, Python and Ruby being the other ones I'd mention). There's 10+ years of optimization and garbage collection research in those VM's, and language is statically typed, which increases verbosity yes, but also performance
3) If you extend the view beyond start-ups, Java isn't just getting used - the world runs on it. If it's a web app of any meaningful size, there's a 90%+ it's written or getting written in Java. The only other language that has this wide an acceptance level is PHP, which is a different animal entirely. Not to disrespect RoR or Django, but their overall share of the web development market is negligible
Keeping in mind the bias that comes from 12+ years of dealing in Java, here's a quick pro-con for what it's worth:
pro =>
- Java is fast. Very fast
- Tool support is unrivaled. It's hard to appreciate what an IDE can do to speed up your work until you've gotten your first couple dozen IntelliJ keystrokes in the muscle memory. RoR is not faster to write than Java (a frequent claim)
- Library support is unrivaled as well. Whatever it is, there's already a library for it, usually quite well-documented, and most questions that come up are googlable on the spot (something I sorely miss when I have to work Rails on occasion)
- with the entry of Play, speed and ease of web development is approaching dynamic languages: write, hit reload, be done
- knowledge and people to hire are available widely
- the JVM is also home to Scala and Clojure. Starting in Java and moving to Scala is a pattern these days
con =>
- it's wordy and, compared to, say, Ruby or Scala, downright ugly. Not a big deal as far as start-up success is concerned, mostly a hacker bragging right. Nothing wrong with bragging as long as it doesn't get in the way of getting stuff done
- generics and collection syntax is unwieldy. IDE support takes care of some of that, but not all
- there's arcane stuff one needs to get used to - a learning curve of sorts. Again, mitigated by the widely available documentation and Google support
The Lift framework core has some rather lithe Scala in it. Do mind that it's an actively developed, actively deployed framework - functionality sometimes takes priority ... ;)