eh, the final pieces are kind of all being worked on
multiprocessing to stop freezing issues and increase response speed
a permissioned API for extensions, easier and saner full themes system (faster/easier development time for updates, and a wider range of extensions/themes as a result)
and switching critical components to a safer language)
which imo are more important for users than doing something an existing firefox fork does (like, if there was demand for firefox with seamless tor, then they would get the firefox with seamless tor today, because it already exists)
multiprocessing to stop freezing issues and increase response speed
a permissioned API for extensions, easier and saner full themes system (faster/easier development time for updates, and a wider range of extensions/themes as a result)
and switching critical components to a safer language)
which imo are more important for users than doing something an existing firefox fork does (like, if there was demand for firefox with seamless tor, then they would get the firefox with seamless tor today, because it already exists)