Live data from Hacker News

Mozilla's new Firefox Linux package for Ubuntu and Debian derivatives

blog.mozilla.org

91–100 of 176 posts

Re: Mozilla's new Firefox Linux package for Ubuntu and Debian derivatives

#91
post #45

Perhaps I'm missing something, but like 6 years ago, I downloaded firefox on linux from mozilla which came as a tar file that I extracted into my home directory and made shortcuts to. It has been working fine and auto updating ever since :shrug: I don't see what the point of this is.

It's handy if multiple users use the same machine, or if you're on a managed system.

Re: Mozilla's new Firefox Linux package for Ubuntu and Debian derivatives

#92
post #65

Takes 7 steps to install Firefox this way as opposed to apt-get install.

This comment doesn’t make any sense. Installing a deb file is done with apt, what are you actually referring to when you say “apt-get install”?

apt, apt-get, aptitude and synaptic are all front ends to the same package management system.

Re: Mozilla's new Firefox Linux package for Ubuntu and Debian derivatives

#93
post #5

The missed the key 5th benefit: Allows you to sudo apt-get purge snapd without annoying unwanted consequences.

I believe lxd is still only available as snap packages on Ubuntu. I am not using it anymore but it's actually quite nice. Fortunately it's now been forked as incus and both Debian and openSUSE will have it. Probably a red-haty distro too.

Re: Mozilla's new Firefox Linux package for Ubuntu and Debian derivatives

#94
post #55

Is there really a point these days in having the very last release rather than the ESR version packaged by Debian? If so what are the benefits for end users?

In case of security fixes, you will stay unpatched for a bit less time. ESR is intended for places that really don't like any form of change like rigid enterprises and banks and such. End users should probably steer clear of that unless they have a good reason not to; which they generally don't. Except for a false sense of security. I personally don't see a good reason to opt out of security changes for any longer th…

I don't see a problem waiting for alpha- and beta-testing to finish first before the new code is distributed to actual normal users.

Note, the "normal users" you describe are involuntary testers who got forced into the role because keeping testers on the payroll is so last century.

Re: Mozilla's new Firefox Linux package for Ubuntu and Debian derivatives

#95
I was already using the ~mozillateam PPA, because fuck Snap, but it'll be great to have an offical Firefox repository.

Ubuntu, if you're listening: fuck Snap. I'm never going to use it. I stripped from all my Ubuntu machines. If you try and force it upon me, I'm moving to Debian, no matter how much hurt that causes me.

Re: Mozilla's new Firefox Linux package for Ubuntu and Debian derivatives

#96
Huh. I just migrated off of the Flatpak to the .tar.bz2 version because I ran into the fact that the Flatpak version has no functioning mDNS resolution. The impact of that is all the stuff that expects .local to work.. doesn't. Can ping etc from shell, but Firefox just goes "Nope, no idea, doesn't exist, give up now". Lots of discussion on multi-year old bugs, but no fix that I could find. I generally solved it by doing everything on .home.arpa (and run step-ca to have TLS), but there are some things that just default to mDNS announcements and produce URLs referring to .local.

Re: Mozilla's new Firefox Linux package for Ubuntu and Debian derivatives

#97
post #66

> Getting the latest version with features and security fixes is key to having a good experience whenever you use Firefox. Now, our new APT repository is directly connected to the Firefox release process, so you will receive the latest updates whenever we make them available. Tip: you will still need to restart Firefox for the latest version. In the past when I've installed Firefox through a .deb, it has had this ann…

I'm pretty sure that forced restart is from the snap package, and you don't have that without snap.

Nope. There are many weird things about snap, but it actually handles Firefox updates very smoothly.

Re: Mozilla's new Firefox Linux package for Ubuntu and Debian derivatives

#98

Earlier quoted context omitted.

In case of security fixes, you will stay unpatched for a bit less time. ESR is intended for places that really don't like any form of change like rigid enterprises and banks and such. End users should probably steer clear of that unless they have a good reason not to; which they generally don't. Except for a false sense of security. I personally don't see a good reason to opt out of security changes for any longer th…

End users also have plenty of reason to dislike change. Change tends to mean things like exciting new spying and UI regressions. Meanwhile, security concerns are often overblown. If you're just using your browser for e.g. email, news, facebook, youtube, netflix, amazon, and your bank, and not venturing out into the seedier parts of the web, you're probably at ~0% risk of some RCE exploit. In any case, an adblocker is…

Yep. vaapi was crashing on several builds in a row on a popos machine, till it magically stopped doing that 2 weeks ago. ESR though, worked just fine.

Re: Mozilla's new Firefox Linux package for Ubuntu and Debian derivatives

#99
post #61
post #55

Is there really a point these days in having the very last release rather than the ESR version packaged by Debian? If so what are the benefits for end users?

If you are a web developer, you would better develop your app using the latest dev tools and targeting the latest web specifications only. Most companies don't prioritize legacy support, so there is no point in developing for Firefox ESR.

> Most companies don't prioritize legacy support,

On the other hand, the more legacy you support, the larger your potential customer base is. Also, if everyone else in the sector only supports the most recent release of only two browsers, you might have that extended customer base all to yourself.

> you would better develop your app using the latest dev tools and targeting the latest web specifications only.

That is one school of thought.

Another is that you should regularly use the oldest platform (hardware, OS, browser) that you want to support. That way you won't get to two weeks before release, decide you ought to test on a dual-core 4Gb machine like you were planning on supporting, and realise that although it technically runs, it's so frustratingly slow that no-one would want to, but there's not enough time to make the changes you'd need to get it working "acceptably". OTOH, if you were using it on hardware where it ran like a dog for you from the 3rd sprint, you'd probably have got round to making the changes for it to be acceptable on that era platform.

Re: Mozilla's new Firefox Linux package for Ubuntu and Debian derivatives

#100

> Getting the latest version with features and security fixes is key to having a good experience whenever you use Firefox. Now, our new APT repository is directly connected to the Firefox release process, so you will receive the latest updates whenever we make them available. Tip: you will still need to restart Firefox for the latest version. In the past when I've installed Firefox through a .deb, it has had this ann…

That's a terrible user experience. I don't remember that happening when I used Firefox through .deb files or the Arch AUR packages. I don't want it actually updating in the background. I'm fine with it checking for updates and even pre-staging the update files for the next time I restart the browser. Swapping out the app files underneath a running browser process in the background, so no new content can be opened, sucks.

Maybe I didn't use the .deb files and just used the .tar.gz. I could see that. I know I used .deb files for Chrome but I can't recall for Firefox, now that I'm thinking about it maybe I did just use the .tar.gz. I remember having to create and edit .desktop files for it. Seems counterintuitive to have a better update experience through a manually managed .tar.gz unzipped directory than through a package file actually meant to be managed through a more formal package manager.

Post reply on HN