EDIT
编辑
Okay, rookie here so please bear with me. What I'm trying to ask is the following:
好的，菜鸟在这里请耐心等待。我想问的是以下内容：
- Is it plausible for a Python-syntax fan to use one of these options while other team members "plain vanilla" version? Is it a matter of personal preference, or would it require converting other people to using these technologies as well?
- 对于Python语法粉丝来说，使用其中一个选项而其他团队成员“普通的香草”版本是否合理？这是个人偏好的问题，还是需要转换其他人使用这些技术呢？
- Is it possible to easily convert between, say, Jython and Java or Pyjamas and Javascript?
- 是否可以轻松地在Jython和Java或Pajamas和Javascript之间进行转换？
- Also, in general, what advantages/disadvantages have people experienced from using these in the "real world"?
- 另外，一般来说，人们在“现实世界”中使用这些有哪些优点/缺点？
I think that states a little more clearly what I'm looking for. Input from anyone who uses these technologies in the industry would be very helpful.
我认为我更清楚地说明了我在寻找什么。任何在行业中使用这些技术的人的意见都会非常有帮助。
Thanks in advance for your insights.
提前感谢您的见解。
2 个解决方案
#1
5
You are talking about two different things.
你在谈论两件不同的事情。
First, Jython and IronPython are Python implementations that you can embed in a Java or C# application to provide scripting capability. This reduces the amount of code that you have to write overall. Or you can look at them as a way to glue together and leverage an existing collection of class libraries. However you look at it, these are good things and lots of people use them.
首先，Jython和IronPython是Python实现，您可以将其嵌入Java或C＃应用程序中以提供脚本功能。这减少了您必须整体编写的代码量。或者，您可以将它们视为粘合在一起并利用现有类库集合的方法。无论你如何看待它们，这些都是好事，很多人都会使用它们。
But Pyjamas is something else entirely. It complicates your web stack and makes it harder to pass projects on to other programmers. The main use case is if you have a shop of Python programmers and they need to provide a rich Internet application client side but cannot afford the time to learn Javascript. Not as broadly useful.
但是睡衣完全是另一回事。它使您的Web堆栈变得复杂，并且使得将项目传递给其他程序员变得更加困难。主要用例是如果你有一个Python程序员的商店，他们需要提供一个富Internet应用程序客户端，但没有时间学习Javascript。不是那么广泛有用。
Also, my personal experience is that most Python programmers already know Javascript reasonably well from building web apps. It really is not much of a learning curve to just dive into Javascript. I've written JSCRIPT scripts on Windows as a batch file replacement and bits of Javascript with Jquery in numerous web pages. When I wanted to learn server-side Javascript for node.js, it really only took a couple of weeks to round out my knowledge of Javascript. In my opinion, Pyjamas should be avoided. Sooner, rather than later, Javascript engines will be supporting version 1.8 of the language which greatly narrows the gap between the languages other than the curly braces issue.
另外，我个人的经验是，大多数Python程序员已经从构建Web应用程序中相当了解Javascript。潜入Javascript真的不是一个学习曲线。我在Windows上编写了JSCRIPT脚本作为批处理文件替换，并在许多网页中使用Jquery编写Javascript。当我想学习node.js的服务器端Javascript时，我只花了几个星期的时间来完善我的Javascript知识。在我看来，应该避免睡衣。更快，而不是更晚，Javascript引擎将支持该语言的1.8版本，这大大缩小了花括号问题之外的语言之间的差距。
#2
0
But how does it scale?
但它如何扩展？
As well as anything else. Scalability is about architecture, not language.
以及其他任何事情。可伸缩性是关于体系结构，而不是语言。
Anyone use these frameworks in industry?
有人在工业中使用这些框架吗？
Yes.
是。
#1
5
You are talking about two different things.
你在谈论两件不同的事情。
First, Jython and IronPython are Python implementations that you can embed in a Java or C# application to provide scripting capability. This reduces the amount of code that you have to write overall. Or you can look at them as a way to glue together and leverage an existing collection of class libraries. However you look at it, these are good things and lots of people use them.
首先，Jython和IronPython是Python实现，您可以将其嵌入Java或C＃应用程序中以提供脚本功能。这减少了您必须整体编写的代码量。或者，您可以将它们视为粘合在一起并利用现有类库集合的方法。无论你如何看待它们，这些都是好事，很多人都会使用它们。
But Pyjamas is something else entirely. It complicates your web stack and makes it harder to pass projects on to other programmers. The main use case is if you have a shop of Python programmers and they need to provide a rich Internet application client side but cannot afford the time to learn Javascript. Not as broadly useful.
但是睡衣完全是另一回事。它使您的Web堆栈变得复杂，并且使得将项目传递给其他程序员变得更加困难。主要用例是如果你有一个Python程序员的商店，他们需要提供一个富Internet应用程序客户端，但没有时间学习Javascript。不是那么广泛有用。
Also, my personal experience is that most Python programmers already know Javascript reasonably well from building web apps. It really is not much of a learning curve to just dive into Javascript. I've written JSCRIPT scripts on Windows as a batch file replacement and bits of Javascript with Jquery in numerous web pages. When I wanted to learn server-side Javascript for node.js, it really only took a couple of weeks to round out my knowledge of Javascript. In my opinion, Pyjamas should be avoided. Sooner, rather than later, Javascript engines will be supporting version 1.8 of the language which greatly narrows the gap between the languages other than the curly braces issue.
另外，我个人的经验是，大多数Python程序员已经从构建Web应用程序中相当了解Javascript。潜入Javascript真的不是一个学习曲线。我在Windows上编写了JSCRIPT脚本作为批处理文件替换，并在许多网页中使用Jquery编写Javascript。当我想学习node.js的服务器端Javascript时，我只花了几个星期的时间来完善我的Javascript知识。在我看来，应该避免睡衣。更快，而不是更晚，Javascript引擎将支持该语言的1.8版本，这大大缩小了花括号问题之外的语言之间的差距。
#2
0
But how does it scale?
但它如何扩展？
As well as anything else. Scalability is about architecture, not language.
以及其他任何事情。可伸缩性是关于体系结构，而不是语言。
Anyone use these frameworks in industry?
有人在工业中使用这些框架吗？
Yes.
是。