Adding functionality to FireFox via extensions is IMO the reason why it is such a popular browser. If you take that freedom 'away' from people by providing them 'pre-baked' solutions, that will not be for the best.
我担心将上述扩展拉入官方（甚至可能是 Mozilla 品牌）发行版会导致这些扩展的开发速度减慢，因为它们的作者必须担心与浏览器发行版提供商协调他们的开发。
I fear that pulling mentioned extensions into an official, maybe even Mozilla-branded, distribution would cause a slowdown in the development of those extensions because their authors would have to worry about coordinating their development with the provider of the browser distribution.
I think it is unnecessary to fork for that, because you can both things already - that is, have multiple profiles, and have all the developer tools as extensions.
You could even install two different profiles and run them from two different executables (portable Firefox makes this easy) allowing you to have a completely different plugin set as well as extension set for both.
但目标平台是什么？ 开发平台（好吧，那么）或“标准”平台——如果是后者，他们就不会使用它，因此开发和测试会加倍或更糟。 只是针对 Gnu Emacs 进行成像，但在 XEmacs 中进行开发。
在您的目标平台上进行开发和测试，否则将面临不愉快的意外......
Thinking about this more, I can't see how it would help.
Say you fork Firefox into a dev version, that is then used by extension developers.
But what is the target platform? The dev-platform (okay, then) or the "standard" platform -- if the latter, they aren't using it, and so dev and testing be be doubled or worse. Just imaging targetting Gnu Emacs but doing the dev in XEmacs.
Develop and test on your target platform, or face unpleasant surprises....
发布评论
评论（6）
在我看来，通过扩展向 FireFox 添加功能是它成为如此受欢迎的浏览器的原因。 如果你通过向人们提供“预先制定的”解决方案来“剥夺”人们的自由，那并不是最好的。
Adding functionality to FireFox via extensions is IMO the reason why it is such a popular browser. If you take that freedom 'away' from people by providing them 'pre-baked' solutions, that will not be for the best.
与扩展相比，这有什么优势？ 您实际上并不相信有人会将代码移植到 C 吗？
What advantage would that give over extensions? You don't actually believe, that someone will port code to C?
我担心将上述扩展拉入官方（甚至可能是 Mozilla 品牌）发行版会导致这些扩展的开发速度减慢，因为它们的作者必须担心与浏览器发行版提供商协调他们的开发。
I fear that pulling mentioned extensions into an official, maybe even Mozilla-branded, distribution would cause a slowdown in the development of those extensions because their authors would have to worry about coordinating their development with the provider of the browser distribution.
您随时可以准备自己的 Firefox 安装程序...
You can always prepare your own Firefox installator...
我认为没有必要为此进行分叉，因为您已经可以做到这两件事 - 即拥有多个配置文件，并将所有开发人员工具作为扩展。
您甚至可以安装两个不同的配置文件并从两个不同的可执行文件运行它们（便携式 Firefox 使这变得容易），从而允许您拥有完全不同的插件集以及两个不同的扩展集。
I think it is unnecessary to fork for that, because you can both things already - that is, have multiple profiles, and have all the developer tools as extensions.
You could even install two different profiles and run them from two different executables (portable Firefox makes this easy) allowing you to have a completely different plugin set as well as extension set for both.
再想一想，我不知道这会有什么帮助。
假设您将 Firefox 分叉为开发版本，然后由扩展开发人员使用。
但目标平台是什么？ 开发平台（好吧，那么）或“标准”平台——如果是后者，他们就不会使用它，因此开发和测试会加倍或更糟。 只是针对 Gnu Emacs 进行成像，但在 XEmacs 中进行开发。
在您的目标平台上进行开发和测试，否则将面临不愉快的意外......
Thinking about this more, I can't see how it would help.
Say you fork Firefox into a dev version, that is then used by extension developers.
But what is the target platform? The dev-platform (okay, then) or the "standard" platform -- if the latter, they aren't using it, and so dev and testing be be doubled or worse. Just imaging targetting Gnu Emacs but doing the dev in XEmacs.
Develop and test on your target platform, or face unpleasant surprises....