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.
-z ----- Original Message ----- > From: "Lloyd Hilaiel" <[email protected]> > To: "Austin King" <[email protected]> > Cc: [email protected], [email protected], "Zachary Carter" > <[email protected]> > 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 <[email protected]> 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! > > lloyd > > > > > thanks, > > ozten > > _______________________________________________ > > Dev-fxacct mailing list > > [email protected] > > https://mail.mozilla.org/listinfo/dev-fxacct > > _______________________________________________ > Dev-fxacct mailing list > [email protected] > https://mail.mozilla.org/listinfo/dev-fxacct > _______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
