Re:Firefox 73
by latexr on Wednesday February 12, 2020 @05:38AM
(#22307680)
> how we can have Firefox thrive and grow
By satisfying the needs of users who
> have used Firefox but have faced issues and would want to try it if <...>
You’re right that every time there’s a Firefox release, it rises to the top of HN with the same comments. I’ve stopped commenting, but I’ll do so now since you asked.
Gripes with Firefox I’ve seen on HN include bad midi support and lack of (or broken) support for macOS features such as the Keychain.
My reason for not using Firefox (and I inadvertently get people out of it) is that it’s atrocious for automation on macOS. It’s the only major browser without AppleScript support, and the bug report open for it is old enough to vote.
When I’ve talked to people from Mozilla about it, I’ve gotten the reply that AppleScript is a power user feature that regular users don’t care for. What they fail to understand is that power users build features for others. I have several tools that interact with web browsers that are relatively popular with non-power users. Every time they ask “can you add support for Firefox?” my answer needs to be “I’d like to, but they don’t provide the functionality”. You can be certain that several of those abandon Firefox, because they’d rather have the convenience of the tool.
You can have Firefox “thrive and grow” by giving its users what they need. It doesn’t matter how “private” Firefox is (and Mozilla has done plenty to not be trusted blindly on that regard) if people can’t use it as their daily browser.
By satisfying the needs of users who
> have used Firefox but have faced issues and would want to try it if <...>
You’re right that every time there’s a Firefox release, it rises to the top of HN with the same comments. I’ve stopped commenting, but I’ll do so now since you asked.
Gripes with Firefox I’ve seen on HN include bad midi support and lack of (or broken) support for macOS features such as the Keychain.
My reason for not using Firefox (and I inadvertently get people out of it) is that it’s atrocious for automation on macOS. It’s the only major browser without AppleScript support, and the bug report open for it is old enough to vote.
When I’ve talked to people from Mozilla about it, I’ve gotten the reply that AppleScript is a power user feature that regular users don’t care for. What they fail to understand is that power users build features for others. I have several tools that interact with web browsers that are relatively popular with non-power users. Every time they ask “can you add support for Firefox?” my answer needs to be “I’d like to, but they don’t provide the functionality”. You can be certain that several of those abandon Firefox, because they’d rather have the convenience of the tool.
You can have Firefox “thrive and grow” by giving its users what they need. It doesn’t matter how “private” Firefox is (and Mozilla has done plenty to not be trusted blindly on that regard) if people can’t use it as their daily browser.