[OpenIndiana-discuss] Firefox 32bit future
Hi, I noticed last year Mozilla made the default Firefox installation for Windows to be Firefox 64bit, then my Linux distro on my work laptop also switched to Firefox 64bit. Are there any figures on Firefox 32bit v 64bit deployment? Is there any immediate danger of Mozilla retiring the 32bit version of Firefox? Regards Russell ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Firefox 32bit future
On 01/25/18 10:40 AM, russell wrote: > Is there any immediate danger of Mozilla retiring the 32bit version of > Firefox? I believe the most immediate item of concern is that Firefox now uses code written in Rust, so you'll be limited to platforms that the Rust compiler generates code for, and I don't know if anyone is bothering to do 32-bit code generation for Solaris/illumos in Rust. Of course, with the elimination of Netscape plugin support, there's little reason to still use a 32-bit version of Firefox. -alan- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Firefox 32bit future
On 01/25/18 07:57 PM, Alan Coopersmith wrote: On 01/25/18 10:40 AM, russell wrote: Is there any immediate danger of Mozilla retiring the 32bit version of Firefox? I believe the most immediate item of concern is that Firefox now uses code written in Rust, so you'll be limited to platforms that the Rust compiler generates code for, and I don't know if anyone is bothering to do 32-bit code generation for Solaris/illumos in Rust. Of course, with the elimination of Netscape plugin support, there's little reason to still use a 32-bit version of Firefox. Previously the reason for using 32-bit Firefox, even on 64-bit platforms, was low to negligent difference in speed (or even faster 32-bit one), better plugin compatibility support and lower memory footprint. (And who needs more then 4GB for a web browser?) Now it could be "only" lower memory footprint in RAM as benefit of 32-bit FF, that could show significant, yet there is still to find test results with 64-bit FF showing much faster then 32bit one, but I suspect it would be the case. Ulike x86-64, where 64-bit apps are generally faster the 32-bit, on SPARC 32-bit apps are faster (and use less RAM), because they.. move less bits. So that's one another mention about 32 vs 64bit in general. Not that SPARC port is moving too fast, but it's like, second big platform for illumos distros. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Firefox 32bit future
On 25/01/18 18:57, Alan Coopersmith wrote: > On 01/25/18 10:40 AM, russell wrote: >> Is there any immediate danger of Mozilla retiring the 32bit version of >> Firefox? > > I believe the most immediate item of concern is that Firefox now uses code > written in Rust, so you'll be limited to platforms that the Rust compiler > generates code for, and I don't know if anyone is bothering to do 32-bit code > generation for Solaris/illumos in Rust. > > Of course, with the elimination of Netscape plugin support, there's little > reason to still use a 32-bit version of Firefox. Apart from the fact that 32bit versions die before gobbling *all* of your system RAM. I find this "feature" very useful! -- Al Slater ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Firefox 32bit future
On 02/01/2018 11:58 AM, Al Slater wrote: > On 25/01/18 18:57, Alan Coopersmith wrote: >> Of course, with the elimination of Netscape plugin support, there's little >> reason to still use a 32-bit version of Firefox. > > Apart from the fact that 32bit versions die before gobbling *all* of > your system RAM. I find this "feature" very useful! > I suggest using "ulimit -v" or, if you want to get really fancy, "newtask" with a project configured to have the specific resource controls you want. I don't think that compilation model is a good proxy for resource limits. It's too blunt, and has too many unnecessary side-effects. -- James Carlson 42.703N 71.076W ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Firefox 32bit future: Rustc
On 25.01.18 19:58, Alan Coopersmith wrote: > > On 01/25/18 10:40 AM, russell wrote: > > Is there any immediate danger of Mozilla retiring the 32bit version of > > Firefox? > > I believe the most immediate item of concern is that Firefox now uses code > written in Rust, so you'll be limited to platforms that the Rust compiler > generates code for, and I don't know if anyone is bothering to do 32-bit code > generation for Solaris/illumos in Rust. > I did some attempts to package rustc for OI, based on the kind of SmartOS, but with no success for now: https://github.com/cgrzemba/oi-userland/tree/rust/components/developer/rust For Rust community is Solaris a tier 3 platform which means no support. But the recipe tries to download the rust-std library wich is not available for Solaris. I have no pkgsrc build system to see how it works for SmartOS. I would be grateful if anyone can give some advice. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Firefox 32bit future: Rustc
On Fri, Jan 26, 2018 at 10:11 AM, Carsten Grzemba wrote: > > > On 25.01.18 19:58, Alan Coopersmith wrote: > > > > On 01/25/18 10:40 AM, russell wrote: > > > Is there any immediate danger of Mozilla retiring the 32bit version of > Firefox? > > > > I believe the most immediate item of concern is that Firefox now uses > code > > written in Rust, so you'll be limited to platforms that the Rust compiler > > generates code for, and I don't know if anyone is bothering to do 32-bit > code > > generation for Solaris/illumos in Rust. > > > I did some attempts to package rustc for OI, based on the kind of SmartOS, > but with no success for now: > https://github.com/cgrzemba/oi-userland/tree/rust/ > components/developer/rust > > For Rust community is Solaris a tier 3 platform which means no support. > But the recipe tries to download the rust-std library wich is not > available for Solaris. > I have no pkgsrc build system to see how it works for SmartOS. > I would be grateful if anyone can give some advice. > I created a component for Rust some time ago. I'll try to push it later today as an example. Not sure whether it will work with recent versions. > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Firefox 32bit future: Rustc
On 01/26/18 10:41 AM, Aurélien Larcher wrote: On Fri, Jan 26, 2018 at 10:11 AM, Carsten Grzemba wrote: On 25.01.18 19:58, Alan Coopersmith wrote: On 01/25/18 10:40 AM, russell wrote: Is there any immediate danger of Mozilla retiring the 32bit version of Firefox? I believe the most immediate item of concern is that Firefox now uses code written in Rust, so you'll be limited to platforms that the Rust compiler generates code for, and I don't know if anyone is bothering to do 32-bit code generation for Solaris/illumos in Rust. I did some attempts to package rustc for OI, based on the kind of SmartOS, but with no success for now: https://github.com/cgrzemba/oi-userland/tree/rust/ components/developer/rust For Rust community is Solaris a tier 3 platform which means no support. But the recipe tries to download the rust-std library wich is not available for Solaris. I have no pkgsrc build system to see how it works for SmartOS. I would be grateful if anyone can give some advice. I created a component for Rust some time ago. I'll try to push it later today as an example. Not sure whether it will work with recent versions. I updated my work on github but it throws still erros on build because it use cc instead of gcc for linking, although I set --default-linker=gcc and RUSTFLAGS="-C linker=gcc" The similar setup works with pkgsrc on smartos. Perhaps someone has an idea? ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
