当我想使用Ember.js时，我应该选择哪个版本？

I am currently considering using ember.js as my mvc solution.

我目前正在考虑使用ember.js作为我的mvc解决方案。

I have learnt Version 1.10. It is merely a js mvc framework. But now Version 1.11 has released with huge modification. It is now more like a web container.

我已经学习了1.10版。它只是一个js mvc框架。但现在版本1.11已经发布了大量修改。它现在更像是一个Web容器。

With Version 1.10, one can use it with Express(node.js) or JavaEE container. These back-end solutions are mature and familiar to me.

对于1.10版,可以将它与Express(node.js)或JavaEE容器一起使用。这些后端解决方案对我来说已经成熟且熟悉。

However, with Version 1.11, I think it is more like a standalone application. No additional back-end is needed.(Actually, It looks like one has to implement the backend logic inside the ember app.)

但是,对于1.11版本,我认为它更像是一个独立的应用程序。不需要额外的后端。(实际上,看起来必须在ember app中实现后端逻辑。)

I currently haven't used Emberjs in any production yet. I am aware of that things can be more complicated when switch from study project to productional project.

我目前还没有在任何产品中使用Emberjs。我知道从学习项目转向生产项目时,事情可能会更复杂。

So I wish people with emberjs production experience can give some advises. I have following enquiries.

所以我希望有emberjs生产经验的人能给出一些建议。我有以下询问。

Is Version 1.10 + Express(or Java EE) a good combination for production? Is 1.10 a reliable version? Is it adequate? What is the most difficult part while adopting to this methodology?

版本1.10 + Express(或Java EE)是生产的良好组合吗? 1.10是可靠的版本吗?它足够了吗?采用这种方法时最困难的部分是什么?

Is Version 1.11 a reliable platform, in perspective of a web container? Compared with the methodology above(1.10+Express or Java EE)， what are the strengths and drawbacks of Version 1.11?

从Web容器的角度来看,1.11版是一个可靠的平台吗?与上述方法(1.10 + Express或Java EE)相比,1.11版的优点和缺点是什么?

Other tips or considerations of using Emberjs are appreciated as well!

使用Emberjs的其他提示或注意事项也很受欢迎!

1 个解决方案

#1

Ember.js has always been for writing standalone applications that communicate with a server via HTTP and JSON. This is not a change between 1.10 and 1.11.

Ember.js一直用于编写通过HTTP和JSON与服务器通信的独立应用程序。这不是1.10和1.11之间的变化。

In 1.11 we updated the guides to reflect the community's adoption of a standard build tool (ember-cli). This build tool is not a replacement for your particular backend technology. You will still develop Ember.js as a stand-alone application and still need to develop a HTTP API service in the backend language and framework of your choice.

在1.11中,我们更新了指南,以反映社区采用标准构建工具(ember-cli)。此构建工具不能替代您的特定后端技术。您仍然可以将Ember.js开发为独立应用程序,并且仍然需要在您选择的后端语言和框架中开发HTTP API服务。

Because Ember.js adheres to Semver, you do not need to adopt ember-cli as a build tool until Ember.js 2.0. All versions of Ember.js in the 1.x series will continue to operate in the style you originally learned. No new features require ember-cli.

因为Ember.js遵循Semver,所以在Ember.js 2.0之前你不需要使用ember-cli作为构建工具。 1.x系列中所有版本的Ember.js将继续以您最初学习的风格运行。没有新功能需要ember-cli。

1 个解决方案

#1

更多相关文章

随机推荐