- cross-posted to:
- privacyguides@lemmy.one
- android@lemmy.world
- cross-posted to:
- privacyguides@lemmy.one
- android@lemmy.world
cross-posted from: https://lemmy.world/post/1766078
Bromite’s actively maintained fork is going to have its own branding starting from next release according to the latest release notes:
Please note: this is the last release, the next one will be in https://github.com/uazo/cromite
You must log in or register to comment.
Brave is almost the same and Vanadium is better on Grapheme devices I don’t recommend Bromite or even a fork It will probably have the same Update issues like Bromite which makes it a terrible option
He was the developer working on Bromite with csagan, and he was likely not the cause of the delays, since the builds on his repo have been keeping up with Chromium all year. I’ve been using it since Bromite stopped getting updates and it works really well. Brave was my second option because of the fingerprinting protection and adblocking, but they don’t disable JavaScript JIT like Bromite and now Cromite. User script support is also really handy for me
I get an image of a scarecrow in my head whenever I say Cromite
deleted by creator
Still don’t understaand why devs prefer fork in instead of improving existing apps and duplicate efforts.
Bromite hasn’t been touched for 6 months, so this is the opposite of duplicating effort, it’s an effort to save the project!
I was not aware of that. Thanks for the information.
It’s exactly what you said: improving an existing app. For certain reasons, the original Bromite branding can’t be used and since the original project’s developer is basically left the project, this was the only way: forking and rebranding. The owner of this fork project was one of the main, most active contributors to Bromite anyway, so it should be fine. I wonder, though if there’s going to be a Cromite WebView as well, because I still use the Bromite WebView… Does anybody know?
Something similar happened with youtube-dlc, allowing yt-dlp to be born
I wish Bitwarden auto fill worked better with this browser.
Yes, apparently it has to be on some kind of builtin list of allowed browsers, otherwise it won’t work. But sadly the PR is still stalling…
