backbone.js 生产准备好了吗？
我最近被一家初创公司聘为前端开发人员。由于我们的产品是将由金融组织使用的用户管理员，因此我们希望该应用程序尽可能像应用程序一样运行。我的任务是寻找客户端框架。
经过研究，我选择了backbone.js。当我今天提出这个选择时，有人问了我一些问题，我没有完整的答案，但我认为你们可能有。
backbone.js 生产准备好了吗？
它坚如磐石吗？有任何证据吗？ 我只会为此应用程序使用模型、视图和集合。我的问题是，我对骨干网在处理模型时不会随机失败有多大信心。有没有我可以查看的官方测试？您对主干有什么经验？是否有任何类型的支持网络来处理骨干网相关问题？
如果我能够回答这些问题，以及向我的老板提出任何见解，我将不胜感激！我真的很想使用主干，因为我认为它非常适合，但因为它太新了，我需要卖掉它。
提前致谢！
I was recently hired at a startup as the front end developer. As our product is a user admin that will be used by financial organizations, we want the app to run as much like an application as possible. I have been tasked with finding the clientside framework.
After researching, I have chosen backbone.js. When I presented this choice today, I was asked some questions that I do not have the full answers for but thought you guys might.
Is backbone.js production ready?
Is it rock solid and is there any proof?
I will only be using models, views, and collections for this app. My question is, how confident can I be that backbone will not just randomly fail when dealing with models. Are there any official tests I might be able to look at? What are your experiences with backbone?Is there any sort of support network in place for dealing with backbone related issues?
Answers to either of these questions as well as any insights you have that I could present to my boss would be most appreciated! I Really want to use backbone as I think its a perfect fit, but because its so new, I need to sell it.
Thanks in advance!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
Backbone.js 生产准备好了吗？
看看Backbone 的示例部分。一些较知名的用户包括：
是否有适当的支持网络？
当然，不能保证它会受到作者的无限期支持，但它很快就获得了很大的关注，所以我看不到它很快就会去任何地方。作者建议在 GitHub 上报告问题。
总有Stack Overflow 本身提供支持！
Is Backbone.js production ready?
Take a look at Backbone's example section. Some of its better known users include:
Is there a support network in place?
There is, of course, no guarantee that it will be supported by its authors indefinitely, but it has gained a lot of traction very quickly so I don't see it going anywhere soon. The authors recommend reporting issues on GitHub.
There is always Stack Overflow itself for support!
几个月前，我也在寻找一个前端应用程序框架。以下是我们的要求列表以及 Backbone.js 如何响应每个要求：
1。浏览器支持 (IE8+)
这里有一个警告：backbone.history 模块使用 hashchange 事件，该事件不会不能在 IE7 及以下版本中工作。有很多方法可以解决这个问题，所以这不是一个阻碍，而是一种烦恼。
2.能够将我们自己的外观和感觉应用到 UI 元素
由于主干仅强制应用程序的 MVC 结构（与 cappucino 或 sproutcore 等框架不同），这对我们来说是完美的选择。
3.能够连接任何其他外部 JavaScript 库
我们已经在使用 jQuery，并且主干支持它，所以这很好。然而，backbone 似乎正在尝试采用与库无关的方法（例如，如果您愿意，您可以使用 zepto.js 而不是 jQuery）。
4.社区支持
在主干上有很多介绍性材料（比如人们在博客上发布教程）。不幸的是，当您的应用程序变得复杂时，我们发现有相当多的“架构”部分需要我们自己解决，但没有明显的方法来做到这一点。 DOCS 很好，但还不是很好。
我猜想固执己见的框架（如 Rails）的陷阱之一是有时你会陷入“我这样做对吗”的感觉。
5.现实世界的例子
看到其他人实际上用骨干做了一些“真实”的事情总是令人信服的：
http://documentcloud.github.com/backbone/#examples
我们最终使用了 Backbone，总体来说这是一次很好的体验，我肯定会在下一个项目中再次研究它。
I too was looking for a front-end app framework a few months ago. Here's the list of requirements that we had and how Backbone.js responded to each of those:
1. Browser support (IE8+)
There is one caveat here: The backbone.history module makes use of hashchange event, which doesn't work in IE7 and below. There are ways to hack around this problem, so it's not a show stopper, but kind of an annoyance.
2. The ability to apply our own look and feel to UI elements
As backbone only enforces the MVC structure of your app (unlike frameworks like cappucino or sproutcore) this was a perfect fit for us.
3. Being able to hook up any other external JavaScript libraries
We were using jQuery already, and backbone supports it, so that was fine. However, it seems like backbone is trying to take a library agnostic approach (for instance you can use zepto.js instead of jQuery if you like).
4. Community Support
There is a lot of introductory material on backbone (like people posting tutorials on blogs). Unfortunately, when your APP get's complicated it turned out there were quite a few "architectural" parts we had to figure out by ourselves, there was no obvious way to do it. The DOCS are good, but not great.
I guess on of the pitfalls of opinionated frameworks (like rails), is that sometimes you get caught up in a "am I doing this right" feeling.
5. Real world examples
It's always convincing to see that someone else has actually done something "REAL" with backbone:
http://documentcloud.github.com/backbone/#examples
We ended up using Backbone, and it was overall a nice experience, and I will definetively be looking into it again for our next project.
谁能说某些产品比产品用户更适合生产？
我正在使用backbone.js处理一个相对较大的项目（实时聊天操作员应用程序，13k+行，目前处于早期测试阶段）。我有超过三个月的骨干经验，我认为这非常好。由于骨气，我没有遇到任何不愉快的意外。我无法想象在没有干净且结构良好的代码的情况下开发这种规模的应用程序。有了骨气，你就可以轻松实现这一点。
使用主干时还有一个很好的好处 - underscore.js。你会经常使用它。
StackOverflow backbone.js 标签 就在你身边！
你的公司作为一家初创公司，不能害怕新事物。您应该适应它们并传播您的经验。请记住，您的产品也将是新的。
Who is to say that something is production ready better than the product users?
I'm working with backbone.js on a relatively large project (livechat operator application, 13k+ lines, currently at early beta). I have more than three months of experience with backbone and in my opinion it's excellent. I haven't had any unpleasant surprises because of backbone. I can't imagine developing an app of this size without clean and well-structured code. With backbone you can achieve that easily.
There's also an excellent bonus when using backbone - underscore.js. You will use that a lot.
StackOverflow backbone.js tag is there for you!
Your company, being a startup, cannot be afraid of new things. You should adapt them and spread your experiences. Remember, that your product is also going to be new.
这个答案有点晚了，但我觉得有必要回答这个问题“我有多大信心在处理模型时骨干不会随机失败”。
没有代码会随机失败；代码由于特定原因而失败，该原因始终可以追溯到某个地方。代码常常会随机失败，因为它是如此复杂和迟钝，以至于你无法理解它。就backbone.js而言，源代码很小（完整记录了1,500行）并且记录得很好。
如果您需要追踪问题所在，只需深入了解源头并查看发生了什么即可。
不管怎样，我希望你能在工作中尝试一下！
A little late to the game with this answer but I felt compelled to respond to the question "how confident can I be that backbone will not just randomly fail when dealing with models".
No code just randomly fails; code fails for a specific reason which can always be traced back to somewhere. Often code appears to randomly fail because it's so complex and obtuse you can't follow it. In the case of backbone.js, the source is small (1,500 lines FULLY documented) and REALLY well documented.
If you need to trace down what is breaking, it's a simple matter of diving into the source and seeing what is going on.
Anyhow, I hope you got to try it out at your job!
在Planbox，我们已经在生产中使用 Backbone JS 6 个多月了，没有出现任何问题。我在这里写了一些关于我们的经验的帖子 和此处。
我们甚至将 Backbone JS 与 jQuery 一起用于我们的移动版本。
At Planbox We've been using Backbone JS in in production for over 6 months without any problems. I wrote a few posts about our experience here and here.
We even use Backbone JS for our mobile version along with jQuery.