Tango 的未来与 D1 的停产
知道 D1 将于 2012 年 12 月 31 日停止使用，考虑到官方发行版在 D1 下，还值得继续使用 Tango 吗？
Knowing that D1 will be discontinued effective December 31, 2012, is it still worth it to continue using Tango given that the official distribution is under D1?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
如果您谈论的是一旦 D1 的官方支持消失，是否值得继续使用 Tango 和 D1，那么我认为这与是否值得继续使用 D1 的答案几乎相同。 D1 缺乏对 dmd 的支持确实不会对 Tango for D1 是否仍然可用产生任何影响。真正的问题是，尽管缺乏支持，您是否要坚持使用 D1，还是要转向 D2。
现在，假设您想迁移到 D2...就
我个人而言，我建议首先考虑 Phobos，因为它是标准库，虽然它仍有改进的空间，但它还很远比 D1 更好。它还得到了明确的社区支持并持续增长。新项目最有可能使用 Phobos，并且只有从 D1 移植的项目才可能使用 Tango。
但是，如果您愿意，没有理由不能在 D2 中使用 Tango - 特别是当您从 D1 移植代码时。有一个 Tango 分支，最近已移植到 D2。就像任何第三方库一样，如果您愿意，您可以选择在代码中使用它。如果您愿意，您甚至可以将它与 Phobos 一起使用（与 D1 不同），尽管它们的风格非常不同。主要使用 Phobos 还是 Tango 完全取决于您。
如果您担心从长远来看 Tango 不会得到支持 - 特别是官方版本仍然仅限 D1 - 我认为没有人可以真正预测这一点。我预计会如此，但如果它没有真正进一步发展，我也不会感到惊讶，因为大多数 D2 用户将使用 Phobos。 Phobos将得到维护，因为它是标准库。谁知道 Tango 会发生什么。但 D2 分叉目前仍在维护中，社区可能会围绕该分叉发展（无论是 D1 Tango 用户转向 D2 还是 D2 用户决定使用它），并且它将继续成为一个强大的、支持良好的库。目前还没有办法知道。
因此，Phobos 是您最好的选择，但如果您愿意，也没有理由不使用 Tango。
If you're talking about whether it's worth continuing to use Tango with D1 once official support for D1 goes away, then I think that that's pretty much the same answer as whether it's worth continuing to use D1. The lack of D1 support for dmd really shouldn't have any effect on whether Tango for D1 is still usable. The real question is whether you want to stick with D1 in spite of its lack of support or whether you want to move to D2.
Now, assuming that you want to move to D2...
Personally, I'd advise looking to Phobos first and foremost, because it's the standard library, and while it still has room to improve, it's far better than it was for D1. It also has definite community support and continues to grow. New projects are most likely to be using Phobos and are only likely to be using Tango if they were ported from D1.
However, there's no reason why you can't use Tango in D2 if you want to - especially if you're porting code from D1. There is a fork of Tango which was recently ported to D2. And just like any 3rd party library, you can choose to use it in your code if you want to. You can even use it alongside Phobos if you want to (unlike with D1), though their styles are very different. It's really up to you whether you use Phobos or Tango primarily.
If your concern is that Tango will not be supported in the long run - especially with the official version still being D1-only - I don't think that anyone can really predict that. I expect that it will be, but it wouldn't surprise me if it doesn't really evolve much further, simply because the majority of D2 users are going to be using Phobos. Phobos will be maintained, because it's the standard library. Who knows what will happen with Tango. But the D2 fork is currently maintained, and it could be that a community will grow around that (be it D1 Tango users moving to D2 or D2 users deciding that they want to use it), and it'll continue to be a strong, well-supported library. There's just no way to know at this point.
So, Phobos is your best bet, but there's really no reason not to use Tango if you want to.
从 Tango 的一个分支（Jonathan 已经提到过）与 D2 配合使用这一事实来看，我坚信 D2 端口周围的用户群将会不断增加，而且我当然相信某些 Tango 模块甚至值得被转移到火卫一。首先想到的 Tango 是管道和选择器。 Phobos 没有提供任何可以与它们相媲美的东西，所以我相信 Tango2 的光明前景。
Judging by the fact that there is a fork (mentioned already by Jonathan) of Tango which works with D2, I firmly believe there will be an increasing user-base around the D2 port, and I certainly believe some of the Tango modules even deserve to be moved to Phobos. First Tango things that come to mind are conduits and selectors. Phobos does not offer anything even remotely comparable with them, so I believe in bright future of Tango2 .