Replies: 1 comment 2 replies
-
A lot of the commits to chromium likely won't have any impact, since they're in platform agnostic pieces. So the surface that needs to be maintained isn't quite as large as you say. But it's still a large undertaking, so kudos to blueboxd for their work.
But that's exactly what this is? It's mainline chromium with patches for backwards compatibility support. Calling it anything else would be disingenuous. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is adapted from a previous post I made in another thread, I am reposting it here for more visibility:
About donations:
Don't be so modest, with the rate Apple is sunsetting older versions of MacOS, Chromium Legacy will become a BIG DEAL in the near future (most computers are Chrome machines, whether you like it or not, the internet is used 80% of the time on ANY computer, the internet IS the computer nowadays), you should definitely accept as much financial help as you can get, you WILL need it.
This project needs more people:
Some more tips, get as many people onboard to write code for Chromium Legacy, this project is wayyyyyy too big for one person. (Google must have an army of programmers working on Chrome, how can you possibly keep up with them if you don't have the people?)
Renaming the browser:
Also, think about renaming the browser, "Chromium Legacy" is a bad name, other browser names are "Chrome", "Edge", "Firefox", "Brave", "Opera", etc. And you got your browser named "Chromium Legacy", you have to do better than that to compete, brainstorm a better name or leave it open to suggestions, you have to do something about this.
I am open to feedback too, please post what is on your mind, thanks.
Beta Was this translation helpful? Give feedback.
All reactions