Hacker News Reader

Comment by zmxz | Hacker News Reader

I'd love to, but it's simply unusable compared to Chrome when it comes to web development.

I have not found any shortcomings in Firefox for web development, so I'm wondering if you could you elaborate on what features are missing, or what killer features for web development Chrome has that Firefox doesn't?

The entire local file system api, for one: https://developer.mozilla.org/en-US/docs/Web/API/File_System... , which severely neuters any tooling designed to help you do real work on your own files.

Also a massive vulnerability surface letting arbitrary websites write whatever they want to your disk.

Definitely not. You have to explicitly select a directory from a native file system UI then confirm both read and write access for each directory, across each domain, typically each session. And system directories are blocked outright with no way to override.

This attitude is why people dismiss Firefox: “well if FF doesn’t implement it, it must be bad. Other browsers surely have glaring security holes”

(Source: I implemented the file system integration for vscode.dev)

Development console in Firefox is lacking compared to Chrome's. Also, the whole Firefox browser is massively slower. There have been benchmarks that prove what I'm typing here, I can't give you a definite list and I see that people started jumping on the downvote hammer so I'm not inclined to defend my opinion. It's my experience, and if someone else's experience differs - I'm glad for them.

AFAIK Firefox is the only browser that does 'persist logs' in dev console right. i.e I get to see the responses of all requests whereas Chrome only shows the current page responses. Chrome has also refused to acknowledge this as a bug.

How so? I use Firefox for web dev, and I don't find it unusable compared to Chrome.

Reply on news.ycombinator.com