您在Scala / Lift中开发的经验是什么？ [英] What are your experiences developing in Scala/Lift?
问题描述
我听到很多关于 Scala 和最近提升 Web框架，特别是来自 Foursquare的家伙因此，我可能会在我的下一个项目中使用这项技术。
I heard a lot of good things about Scala and the Lift Web framework recently, especially from Foursquare's guys hence, I might use this technology in my next projects.
- 您是否有任何Scala / Lift Developers？
- 您在此平台上开发的经验是什么？与Ruby On Rails或Python / Django相比，它有哪些优势？
- 您认为未来几年它是一种可行的技术和值得关注的东西吗？
值得吗？分享您在Scala / Lift平台上的体验。
Is it worth it? Share your experiences on the Scala/Lift Platform.
推荐答案
-
我现在正在Scala做我的大部分事情。 （我应该提一下，我认为Scala是自前一轮发明以来最好的东西。： - D）
I'm currently doing most of my things in Scala right now. (I should mention that I think that Scala is the best thing since the invention of the wheel some time ago. :-D )
在我的拙见中，它是唯一的语言真正允许人们选择最佳的任务方法，而不会在（更多）面向对象和（更多）功能方法之间产生不必要的分歧。
In my humble opinion it is the only language which truly allows people to choose the best approach to a task without some unnecessary divide between (more) object-oriented and (more) functional approaches.
查看语言之前声称有这样的事情，我基本上可以看到两个相互竞争的语言设计阵营：
Looking at the languages which claimed something like this before, I can basically see two competing language design camps:
-
来自面向对象方的那些看到函数式编程最近获得了一些牵引力并且认为好吧，我们并不真正理解那个功能性的东西，但是让我们为我们的语言添加一些花哨的语法糖，所以我们可以声称它也是功能性的！ （例子：Java，Python）
然后是功能方面的人，他们认为嗯，我们的功能方法很远优于其他任何东西，面向对象的废话很烦人，但让我们在我们的语言中添加一些额外的关键词，这将使我们的语言肯定会逃离学术界！ （示例：F＃，OCaml）
Then the ones from the functional side, who thought "Well, our functional approach is far superior to anything else and that object-oriented nonsense is annoying, but let's put some additional keywords into our language, that will make our language escape academia for sure!" (examples: F#, OCaml)
Scala的设计师统一了来自双方的许多方法并且创造了一些精心设计的语言 - 在我看来，这是与其他语言的最大区别，它决定采用弗兰肯斯坦方法来编程语言设计。
Scala's designers unified many approaches coming from both sides and created some well-designed language, which is - in my humble opinion - the biggest difference to other languages, which decided to take the "Frankenstein" approach to programming language design.
只使用Lift做了一些较小的东西，只有Rails和Django的表面经验，我不得不承认，大部分时间我都想知道为什么Lift中的某些东西与我的预期有所不同，这是由于事实上，我的期望是有缺陷的，而且Lift的方法更优越。
Having done only smaller things with Lift yet and only superficial experience with Rails and Django, I have to admit that most of the time when I wondered why something in Lift worked differently from what I expected, this was due to the fact that my expectations were flawed and Lift's approach superior.
提升当然不是简单介绍Scala，但了解Lift的工作原理几乎与学习Scala之前一样有意义。 。
Lift is certainly no "easy introduction to Scala" but learning how Lift works was almost as rewarding as learning Scala before it.
能够拥有一个没有任何逻辑的干净视图的能力对其他声称相同的框架有很大的改进，但却没有。 Scala的XML文字支持使得验证响应的良好性成为可能：编译器将在编译时证明您只向客户端发出格式良好的XML。
The ability to have a "clean" view without any logic in it is a great improvement to other frameworks which claimed the same, but fell short of it. Scala's XML literal support makes it possible to verify the well-formedness of your response: The compiler will prove at compile time that you only emit well-formed XML to a client.
Lift是一种可行的技术，如果您想构建外观，感觉和行为类似于真实桌面应用程序的Web应用程序，而不是自己编写疯狂的代码，那么这是唯一真正的方法。
Lift is viable technology and at the moment the only real approach if you want to build web applications which look, feel and behave like "real" desktop applications without writing insane amounts of code yourself.
这篇关于您在Scala / Lift中开发的经验是什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
