- cross-posted to:
- firefox@lemmy.ml
- hackernews@lemmy.smeargle.fans
- hackernews@derp.foo
- cross-posted to:
- firefox@lemmy.ml
- hackernews@lemmy.smeargle.fans
- hackernews@derp.foo
There’s this new browser built on Firefox that seems to be picking up steam on GitHub lately.
It looks like it’s trying to be a more feature-rich, “batteries included”, version of Firefox with hardening out of the box.
Has anyone used it? What do you think about it?
I had asked why it is like that before, and basically it sounds like the rendering engine and the UI and all in Firefox are all tightly integrated.
Whereas with Chromium you can pretty easily embed the engine into anything.
Unfortunate.
I’ve heard something similar but wonder how true that is.
This fork kinda disproves it to some extent?
I’ve never had anything to do with code for native apps, but it just seems odd. Why would the rendering engine be tightly coupled with the window decorations? If they can be changed between versions I imagine they can be changed between forks?
Like I said, I’m no authority, just curious about this aspect.
Floorp is still Firefox at its core as it’s still using Firefox’s UI and building on top of it, while Chromium can be embedded into a GUI (see Vivaldi and projects like CEF and Electron). That doesn’t discredit it, in fact some of Floorp’s changes are pretty good for customisabiity and user experience. That being said, I was told that the engine powering Firefox was able to be embedded but it had many issues to the point where integrating Chromium was easier.
On a similar note, I know Pulse Browser is part of an overarching project to make forking of Firefox an easier job, and I know they and the Floorp people are friendly.