Hacker News new | ask | show | jobs
by devit 1254 days ago
I'd suggest those priorities, in order:

1. Making a fully secure no-JavaScript browser for Tor usage

2. A secure browser that works on major websites

3. Android support

4. Embedding support

5. Extensions support

6. All missing features supported by both Firefox and Chrome, roughly in order of addition to the web standards

7. Replace Firefox

8. All features supported by any browser

1 comments

It’s rather uncommon that you consider TOR support to be a higher priority than “a browser that works”, so I’d like to hear more about the ordering of your first two priorities, specifically.
Because an unexploitable browser (which is the main fundamental advantage of Servo) is more important for Tor than elsewhere since an exploit will compromise anonymity.

Also, since Tor browsing is often done with JavaScript off, and removing JavaScript removes a huge amount of web features that need to be supported (including a JavaScript engine, which I think Servo still doesn't have a pure Rust implementation of), it's much easier to make a usable browser for this use case than others.