Where are technical specs?

[tvtv]

I just heard about "a new browser" and decided to take a look. As a professional web developer, i care about the technology "under the hood" yet you have not published any of the browser specs on your website it appears? That should be a good selling point but seems to have been overlooked. As developers, we can spread the word either positively or negatively. In this case I want to know about things such as: 1. the Javascript engine you're using, is it V8? Is it an earlier incarnation of the Opera code? Is it homegrown? How does it compare, with published test results, against the major browser Javascript engines like Chakra, Edge, Nitro, Carakan... 2. specs on the HTML engine, similar to above... 3. memory footprint, leak test, max number of open tabs possible, any leaks found while keeping it open and running for 30 days, stuff like that... 4. security test results, compatibility results, how does it handle older/newer PDF file versions -- is a PDF renderer even built in or does it use the outdated NPAPI module interface? As you can see there is a lot of information that needs to be published front-and-center on your website so that technical folks can read and make a judgement if they are going to spend their time even installing it to test. Hopefully you can add this info to your website soon. Thanks for reading.

[Ayespy]

@tvtv:

I just heard about "a new browser" and decided to take a look. As a professional web developer, i care about the technology "under the hood" yet you have not published any of the browser specs on your website it appears? That should be a good selling point but seems to have been overlooked.

As developers, we can spread the word either positively or negatively. In this case I want to know about things such as:
1. the Javascript engine you're using, is it V8? Is it an earlier incarnation of the Opera code? Is it homegrown? How does it compare, with published test results, against the major browser Javascript engines like Chakra, Edge, Nitro, Carakan…
2. specs on the HTML engine, similar to above...
3. memory footprint, leak test, max number of open tabs possible, any leaks found while keeping it open and running for 30 days, stuff like that...
4. security test results, compatibility results, how does it handle older/newer PDF file versions -- is a PDF renderer even built in or does it use the outdated NPAPI module interface?

As you can see there is a lot of information that needs to be published front-and-center on your website so that technical folks can read and make a judgement if they are going to spend their time even installing it to test. Hopefully you can add this info to your website soon.

Thanks for reading.

It's built on Chromium, so it's Blink and V8. The UI, however, is HTML5, JS , CSS, REACT. Memory footprint, due to technologies used in the construction, is a bit more than Chrome or Opera on average, but developers look to optimize that. PDF viewer is the one built in to Chromium. There is no compatibility with NPAPI since about five engine updates ago.

There are numerous articles, blog posts and interviews that reveal these details. There is no "tech specs" page devoted to them as yet.