console.log doesn’t have to be slow. Its only slow in Gecko. Its ridiculously fast in Chrome. We should probably simply optimize it.
Andreas On Aug 21, 2014, at 8:47 AM, Tim Chien <[email protected]> wrote: > On Thu, Aug 21, 2014 at 4:01 PM, Gabriele Svelto <[email protected]> wrote: >> On 21/08/2014 08:21, Tim Chien wrote: >>> Previously we had a creative invention from Frsela that turning on/off >>> a all-caps DUMP() function with mozSettings. I would love that being >>> formalized in Gecko. >>> https://github.com/mozilla-b2g/gaia/blob/master/shared/js/dump.js >> >> Standardizing all gaia applications on DUMP() would already be a big >> improvement even though the interface is currently very simple. Gecko >> has similar problems regarding logging with certain components being >> well made and others a total mess (often dumping output via 3/4 >> different unrelated methods). Also, the most common mechanism used in >> C++ code (PR_Log) is not available under chrome code and thus we >> normally resort to ad hoc logging solutions there (see the RIL component >> for example). >> >> Gabriele >> > > Yeah, but that would mean every app need to read that mozSettings > value (and have the permission to access that) right? Plus log will > not appear during app start-up until the mozSettings get() returns > positive value. > > I may be naive but I would really love that being done in Gecko... > > -- > Tim Guan-tin Chien, Engineering Manager and Front-end Lead, Firefox > OS, Mozilla Corp. (Taiwan) > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
