I don't care that its losing marketshare as long as its still used and supported, just like how I don't really care that most computer users aren't using the command line anymore. The age of the average user being choosy about their web browser is over, and the hand wringing about market share is not important. Users either use the browser that ships with their OS (safari, the limited people on edge), or they download chrome because youtube and gsuite have been giving them banner ads to download chrome for a decade and that's where their autofill passwords are saved.
Instead, mozilla should really lean in on catering to the techie who is going to come to the conclusion to use firefox no matter what mozilla really does anyhow, just from the fact that its not google and you can do more with privacy oriented extensions. It's always frusterating when mozilla does things they really don't have to do, like break certain CSS configs with the move to proton for no reason other than change is good I guess (like, why pull another python 2/3-esque debacle when you don't really have to and could just support legacy syntax?), or taking out niceties like the built in RSS reader, which I found handy to confirm a feed looked OK before throwing it into my actual RSS reader. There are other issues too. Maybe I'm not doing it right in firefox, but I have to go into chrome to find the correct CSS selectors to use in a given webpage for javascripting.
Instead, mozilla should really lean in on catering to the techie who is going to come to the conclusion to use firefox no matter what mozilla really does anyhow, just from the fact that its not google and you can do more with privacy oriented extensions. It's always frusterating when mozilla does things they really don't have to do, like break certain CSS configs with the move to proton for no reason other than change is good I guess (like, why pull another python 2/3-esque debacle when you don't really have to and could just support legacy syntax?), or taking out niceties like the built in RSS reader, which I found handy to confirm a feed looked OK before throwing it into my actual RSS reader. There are other issues too. Maybe I'm not doing it right in firefox, but I have to go into chrome to find the correct CSS selectors to use in a given webpage for javascripting.