We just ran a session  on what to do about the upcoming EOL for Firefox/Linux in 2017. In short, we’re not planning to diverge from Mozilla’s direction. The goal is to have Flash work today, and to become irrelevant over time. Hopefully reaching the point of being irrelevant by 2017. There are ways for you to help! See below.
Distributing Firefox and Chrom/ium plugins now possible
How can you help make Flash go away?
On any browser, any platform (that has Flash of course)
Use less Flash. See if you can do step 1. If you can proceed to step 2, etc.
- Make Flash Click to Play.
- Disable Flash.
- Uninstall Flash.
To do these on Chrome, browse to chrome://plugins/, On Firefox go to Add-ons -> Plugins.
If their is a site that doesn’t work without Flash, see if you can load their site on a mobile device. Either way contact them and ask them nicely about removing the Flash content to get more hits, or for enabling at least the mobile site for non Flash users.
Run a Beta browser
Generally both Firefox and Chrome will push new web technologies in their Beta browser. Many of them have the potential to help make Flash less relevant. Help make them more stable by testing them!
Run Firefox Nightly
Try running Firefox nightly. We could always use more testers. Specifically, we might get a more aggressive Mozilla when MSE is done being implemented (which should make youtube even more HTML5 video friendly).
Of course, there a bunch of other useful features Mozilla is working on to make browsing better. Help would be welcome there too! Report bugs on issues you have.
Other options considered.
- We add PPAPI support to Firefox ourselves / Hack it in
- Outcome: Non-starter. Unless Mozilla adds it we don’t want the maintenance burden.
My Todo List
- Investigate why Youtube Live videos sometimes don’t work without Flash. (Even in Chromium).
- Figure out why my Nightly install doesn’t have working H264..
UPDATE – because it’s not designed to yet! See here – http://andreasgal.com/2014/10/14/openh264-now-in-firefox/
If you have H264 working in Firefox it’s likely due to GStreamer support included in the Ubuntu (and many other distros) builds. Upstream Gst1.0 support is waiting on infrastructure .
Hopefully I captured everything right.. but if I didn’t please let me know!
Running 32 bit Ubuntu when the hardware technically can do 64 bit
- hardware issues varied from EUFI 32 bit only, to printer and driver issues
- application included wine (try building wine on 64 bit…) and virtualization
- some 64 bit users use 32 bit images for virtualization to use less RAM
- Not in survey but I know of others who use 32 bit specifically to work with Android.
Arch vs Desktop Environment vs Release
Please do not use this to really compare desktop environments! If multiple answers I took the least resource intensive one! (Next time I do this.. I should just require users to pick a primary one)
Impacts over Releases
- Switch from Ubuntu – also includes plans to stay on old unsupported version until hardware dies
- Moderate is somewhat a catch all
- If I do this again, I should just have a 1-5 sliding scale, in addition to a text field.
- Users are concerned about having to throw out old machines, not having an upgrade path to go from 32-> 64 bits, and the cost to upgrade.
- Select Comments (many more in the raw data of course!)
- As an aspiring software developer, phasing out 32 bit support would be great for me as it means one less build to maintain.
- I plan on reinstalling Ubuntu on this laptop as a 64bit install at some point anyway.
- Unless the schedule changes, no impact. We’re planning to do the switch late 2015 / early 2016.
- I will have to stay on 16.04 forever on that machine. The needed drivers are not going to be available in an open-source form.
- My parents + my children have no PC
- we have old PC’s in the hospital and i don’t think this hardware would be upgraded.
- If the majority of freely given computers we receive are still 32-bit by then, we’d have to respin another distro. But, like PowerPC; all good things must come to an end.
- Just need to figure out how to make the switch. If it means re-installing, bah.
- It is terrible, because my eeePC only has 1GB in it.
- One more reason to decommission the hardware.
I think the original plan can still work, but like any good survey we know have more questions to ask!
- Lubuntu/Xubuntu support for 14.04 LTS is 3 years not 5. It’s going to be a LOT higher impact if they don’t have support in 2019/2020 (which would be the case if 16.04 is 3 years too). This could obviously be mitigated by moving 32 bit to ports and having it be opt in. Lubuntu/Xubuntu 18.04 with 3 years would get us to 2021.
- What can we do to make virt use less RAM? (Lots of Virtualbox)
- What can we do to make bare metal use less RAM?
- Building Wine on 64 bit? (The two easiest methods are defunct if we remove 32 bit images I think… http://wiki.winehq.org/WineOn64bit)
- Can we do an actual upgrade path? Or at least start officially testing 32->64 “upgrade” re-installs?
Just to complete the application compatibility story (not from survey), Games are starting to be 64-bit only:
Raw Data can be found here: https://docs.google.com/spreadsheets/d/1iA062pCR1ayAMEKveUToEhq–9awyDXTEaL4fhsj8TU/edit?pli=1#gid=0
I’m considering a proposal to have 16.04 LTS be the last release of Ubuntu with 32 bit images to run on 32 bit only machines (on x86 aka Intel/AMD only – this has no bearing on ARM). You would still be able to run 32 bit applications on 64 bit Ubuntu.
Please answer my survey on how this would affect you or your organization.
Please only answer if you are running 32-bit (x86) Ubuntu! Thanks!
If you can’t see the form below click here.
I just created an add-on that literally just changes the one bit* needed to disable SSL 3.0 support in Firefox
You can get it here: https://addons.mozilla.org/en-US/firefox/addon/disable-ssl-30/
*It’s trivial to do in about:config, yet I don’t really want to recommend that to anyone..
I did a comparison when 14.04 was first released on the memory usage of different Ubuntu flavors. Some takeaways:
- Lubuntu has zRam (automatically compress memory to save space) enabled by default making it hands down the most usable version with low-memory. It’s the only flavor to have it enabled on the LiveCD.
- The real cost of 64 vs 32 bit is usually only 128 MB.
- Lubuntu (32-bit) still boots with just 160 MB of RAM!
- The Ubuntu kernel can’t boot with only 128 MB of RAM.
All testing was done in virtual machines (Virtualbox) and obviously with different hardware you’re results will vary. You can infer some of my methodology from the notes below. This was done months ago and I don’t remember all of the details. The results may have changed with software updates, especially to Firefox.
Raw testing notes