given how many targets are supported by llvm there’s really little difference in cross platform support asides from building artifacts for the specific target platform. wrapping package delivery in a package manager removes the additional complexity to the end user.

main difference is auto fill support and detection based on domain and/or application. mainly saves a few clicks and also prevents passwords from leaking through clipboards.

Maybe they could white label a password manager (Bitwarden?)

not sure starting at which version, but in android you can set bitwarden as a default password manager system wide which integrates pretty seamlessly with firefox and other apps. only place i know bitwarden doesn’t really integrate well with firefox is on Linux but that seems more due to bitwardens lack of interest to implement freedesktop apis.

i agree though with additional revenue streams, they need to break dependence on Google search engine revenue. maybe spend research on alternative monitization to ads and sponsored content that could be implemented at a browser level and split revenue between browser and websites.

could be skimpflation. company’s have been changing ingredients slowly to lower the cost of ingredients to save on cost. doing it very slowly over years they end up saving money and no one really notices the changes.

if you can find an old ingredient/nutritional list from a few years ago you can compare ingredient order to see if it’s changed

One very nice feature is that when you use multiple profiles, you can specify in which of those external links open in.

is this similar to Firefox containers? dunno why mozzila makes it as a plugin and hasn’t bundled it in yet as a standard feature, literally can’t live without it.