Joone 与 Encog - 生产应用程序
有人在生产应用中同时使用过 Joone 和 Encog 吗? 在生产应用程序中,您是否需要对产品中的一个或另一个产品进行一些改进?
Has anyone used both Joone and Encog in production applications? Is there something you needed to do in a production app with one or the other where the product fell short?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
两个都看了。 尽管在输入管理和规范化方面有一些不错的设计功能,但 Joone 仍处于休眠状态。 Encog 很活跃并且有希望。 它的各种抽象级别非常适合您自己的目的进行重写,尽管您可能会发现自己在开始之前花费了大量时间来弄清楚抽象类的各个层。 此外,由于这种分层,我不确定性能是否会很出色,尽管可以通过为您的特定应用程序重写适当的类来克服这一点。
Looked at both. Joone is pretty dormant though has some nice design features in terms of how inputs are managed and normalized. Encog is active and has promise. It's various levels of abstraction are well suited to overriding for your own purposes though you may find yourself spending a lot of time figuring out the various layers of abstracted classes before you get started. Additionally, because of this layering I'm not sure performance will be spectacular though that can be overcome by rewriting the appropriate classes for your specific app.
JOONE 似乎几乎已经死了,自 2007 年 1 月以来它一直处于“候选版本 1”(有很多错误)。Encog 刚刚发布了 2.0-beta2,并且是一个受到积极支持的产品。 我会选择Encog。 http://www.encog.org
JOONE seems to be mostly dead, its been on "release candidate 1"(with lots of bugs) since Januarl 2007. Encog just released 2.0-beta2, and is an actively supported product. I would go with Encog. http://www.encog.org