Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

2015-12-13 Thread Nicholas Nethercote
On Sun, Dec 13, 2015 at 9:17 AM, Cameron Kaiser wrote: > > This would essentially mandate, then, that Gecko can only be built on > platforms with a Rust toolchain. That may be desirable, but it would > probably bust some of the obscure Tier-3 platforms and it would definitely > bust TenFourFox (we

Re: Rust as build requirement was Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

2015-12-13 Thread Cameron Kaiser
On 12/13/15 12:50 AM, Nicholas Nethercote wrote: On Sun, Dec 13, 2015 at 9:17 AM, Cameron Kaiser wrote: This would essentially mandate, then, that Gecko can only be built on platforms with a Rust toolchain. That may be desirable, but it would probably bust some of the obscure Tier-3 platforms

Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

2015-12-13 Thread Bobby Holley
On Sun, Dec 13, 2015 at 3:50 AM, Nicholas Nethercote wrote: > On Sun, Dec 13, 2015 at 9:17 AM, Cameron Kaiser > wrote: > > > > This would essentially mandate, then, that Gecko can only be built on > > platforms with a Rust toolchain. That may be desirable, but it would > > probably bust some of

Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

2015-12-13 Thread Robert O'Callahan
On Sun, Dec 13, 2015 at 2:28 PM, Bobby Holley wrote: > I don't know why we would allow there to be a long gap between (a) and (b). > Maintaining/supporting two sets of the same code is costly. So if we get > the rust code working and shipping on all platforms, I can't think of a > reason why we w

Re: Rust as build requirement was Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

2015-12-13 Thread Jack Moffitt
> On the other hand, in that same thread, metajack said, "The current plan is > to have Rust (in the form of rust-url replacing nsUrlParser) riding the > trains later this quarter." And indeed, Rust is now riding the trains with the moov parser. It's not required for the build yet, but Nightly (an

Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

2015-12-13 Thread Nicholas Nethercote
On Sun, Dec 13, 2015 at 11:28 AM, Bobby Holley wrote: >> >> I've been wondering about this. There's a big difference between (a) >> permitting Rust components (while still allowing fallback C++ >> equivalents) and (b) mandating Rust components. > > I don't know why we would allow there to be a lon

Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

2015-12-13 Thread Bobby Holley
On Sun, Dec 13, 2015 at 6:27 PM, Nicholas Nethercote wrote: > On Sun, Dec 13, 2015 at 11:28 AM, Bobby Holley > wrote: > >> > >> I've been wondering about this. There's a big difference between (a) > >> permitting Rust components (while still allowing fallback C++ > >> equivalents) and (b) mandat

Re: FYI: e10s will be enabled in beta 44/45

2015-12-13 Thread Daniel Veditz
On Mon, Dec 7, 2015 at 4:36 AM, Kurt Roeckx wrote: > On 2015-12-04 19:43, jmath...@mozilla.com wrote: > >> Not an issue since initial rollout to beta and release will be to users >> who do not have addons installed. >> > > Is it even possible to have no addons installed? Firefox installed a > nu

Re: APZ enabled on Fennec nightly

2015-12-13 Thread Jared Wein
Nice feedback on Reddit about the changes. Great job! https://www.reddit.com/r/firefox/comments/3wo4rm/nightlyandroid_scroll_speed_is_improving/ - jared On Wed, Dec 2, 2015 at 12:39 PM, Kartikaya Gupta wrote: > Thanks for trying it out and reporting these issues! I've filed them > as separate