I don’t know that I’d call that a chromium browser but I’ve only looked at its docs for 10 minutes. Hard to say where chromium integration begins and ends there without digging into the code. Seems like, at most, it’s using the web rendering engine from the chromium project. But it also seems to suggest it has its own modules for executing/rendering js/css/html.
Probably not included in the “should be avoided” category.
I’m currently using it in a browser called Falkon. It’s not as big as Firefox or Chrome, but it is endorsed by KDE. Also, Apple’s Safari is using something similar.
I don’t know that I’d call that a chromium browser but I’ve only looked at its docs for 10 minutes. Hard to say where chromium integration begins and ends there without digging into the code. Seems like, at most, it’s using the web rendering engine from the chromium project. But it also seems to suggest it has its own modules for executing/rendering js/css/html.
Probably not included in the “should be avoided” category.
Now I’m curious what it’s used for.
I’m currently using it in a browser called Falkon. It’s not as big as Firefox or Chrome, but it is endorsed by KDE. Also, Apple’s Safari is using something similar.
Not at all.
Safari is using WebKit, which they based on KDE’s old KHTML engine, which is now discontinued.
Falkon uses qtwebengine which is Chromium’s web engine + integration with QT user interface.
A Linux browser that uses WebKit (like Safari) is GNOME Web.