Archive

Archive for September, 2015

Project Candle: Mozilla 的低功耗改进计划

September 14th, 2015 No comments

在发起了性能改进计划(AreWeFastYet.com)和内存使用改善计划(AreWeSlimYet.com)之后,最近 Nicholas Nethercote 发起了新的功耗改进计划: Project Candle。

Nicholas Nethercote 是 Valgrind 的主要作者,背着顶会论文2000+次引用的光环 🙂

具体如何改进我还一窍不通,不知道低功耗怎么做的。Mozilla 已经建立了专门的 IRC 频道和邮件列表,具体可以看 Candle 的项目Wiki

第100篇Blog

September 11th, 2015 No comments

sqrt(Hooray)!

Firefox Technical Architecture Group

September 11th, 2015 No comments

Dave Camp 一个月前在邮件列表中宣布了新的 Firefox 架构领导小组:

We don’t have a lot of people whose responsibility extends to the entire Firefox frontend. Most of us are focused on individual pieces of our large codebase. Meanwhile, we have a set of large technical challenges ahead of us. In particular, gofaster and figuring out what comes after XUL are going to be sweeping changes that affect large swaths of code.

We are asking Dave Townsend, Richard Newman, Rob Helmer, Mark Hammond, and Robert Strong to explicitly take over technical stewardship of the Firefox products. Their responsibilities will be:

* Document and build consensus around larger projects that affect Firefox products.
* Help resolve technical issues that cross functional areas of the project.
* Provide a point of consistent technical decision making.
* Be a point of contact for and coordinate cross-technology projects with other Mozilla groups such as Platform and Content Services.
* Be available to technical contributors for guidance, mentoring, etc.

This may look a lot like Module Ownership – this is no coincidence. Mark Finkle (as Firefox Mobile module owner) and I (as Firefox Desktop module owner) will be delegating a lot of the technical responsibility for those modules to that group. It may also remind some folks of the Super Reviewers. It’s similar to that in spirit (a group of people charged with a global view of the product) but not in mechanics (no sr? flags, and limited to the Firefox frontend modules).

This isn’t a permanent appointment. We’ve asked these people to help get us started working through the gofaster and deXULinisation initiatives, but we’ll cycle people in an out as events warrant. Nor do we expect these people to do it alone. We expect them to be working closely with all the engineers on the team.

Thanks to the Firefox Architects for stepping up.

 

现在差不多已经成型了:

https://wiki.mozilla.org/Firefox/Technical_Architecture_Group

不过目前在 Mozilla 之外还没有看到什么内容.

SpiderMonkey 开始计划提供 JS 覆盖率信息

September 9th, 2015 No comments

Mozilla Bugzilla 上已经有了对应的 meta bug. 具体的实现可能需要再等一到两个月.

Nicolas B. Pierron [:nbp] 2015-07-30 08:05:23 PDT
This is a meta bug to add Code Coverage for JavaScript code executed in SpiderMonkey. We have multiple reasons to do that:

The most important is to support release management team, by producing Code Coverage information over executed JavaScript code, and producing gcov-like data files. This would help improve the quality of Firefox, and help evaluate the quality of our tests to accept/refuse new features.

The second reason is to expose this information to the dev-tools, such that JavaScript developers do not have to instrument their code to have code coverage results within the dev-tools.

The third, if the overhead is neglectable, is to make use of the same information to improve IonMonkey register allocation and removal of unused basic blocks ahead of time.