10.21.13 Engineering Progress Report for Firefox Accounts and Sync.next
lhilaiel at mozilla.com
Thu Nov 7 14:55:30 PST 2013
Thanks for the background, Zach. This makes total sense.
On Nov 8, 2013, at 12:43 AM, Zachary Carter <zcarter at mozilla.com> wrote:
> I touched on it briefly in my other reply, but, simply, the generated bundle is bloated, ugly, and of questionable stability. The work required to get it into a state that could potentially pass gaia review was deemed not worth it, especially with the raw_password endpoints and parts of the client already being written in gecko. We're in the process of rewriting gherkin for the web first instead of node.js for similar reasons.
> ----- Original Message -----
>> From: "Lloyd Hilaiel" <lhilaiel at mozilla.com>
>> To: "Austin King" <ozten at mozilla.com>
>> Cc: sync-dev at mozilla.org, dev-fxacct at mozilla.org, "Zachary Carter" <zcarter at mozilla.com>
>> Sent: Tuesday, November 5, 2013 1:04:49 AM
>> Subject: Re: 10.21.13 Engineering Progress Report for Firefox Accounts and Sync.next
>> On Oct 24, 2013, at 8:00 PM, Austin King <ozten at mozilla.com> wrote:
>>> On 10/24/13 8:17 AM, Zachary Carter wrote:
>>>> For FxAccounts on FxOS, we've determined that landing the browserified
>>>> FxAccounts client library in gaia is not really viable.
>>> Why isn't it viable? These kinds of details are helpful for evaluating
>>> Desktop strategies.
>> I too am curious to hear the backstory!
>>> Dev-fxacct mailing list
>>> Dev-fxacct at mozilla.org
>> Dev-fxacct mailing list
>> Dev-fxacct at mozilla.org
More information about the Dev-fxacct