![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://beehaw.org/pictrs/image/1be75b15-2f18-429d-acf7-dcea8e512a4b.png)
Honestly I would probably not use it. One if the most important things I’m looking for in an API is reliability - and a project that has no financing is really just waiting to have its plug pulled.
You might be highly motivated right now to keep it going for many years. But without a steady income it might just be a burden to keep it going at some point.
(Nothing personally obviously, I don’t know you and wish you all the best!)
There are literally only chromium-based browsers and Firefox (and its forks) with any meaningful market share. Developing a new browser engine is extremely complicated and time consuming, so there really is no danger of having “too many” browsers. And of course all browsers based on chromium (Google Chrome, Edge, Vivaldi, Brave, …) support the same set of extensions, because they use the same engine. So extension compatibility is also not a problem.
Supporting the gazillion ever-changing web technologies and standards and layout systems for a completly new browser is a problem though.