Maintaining a Chromium fork

[jane.n]

Our dev @yngve wrote a new post on his Vivaldi.net blog - "Soooo … you say you want to maintain a Chromium fork?". It gives a great overview of what it takes to build a Chromium based browser.

I certainly learned something new from reading it. Did you?

[Pathduck]

I love @yngve 's technical posts, they are always interesting reading

Even for a Git neophyte as myself - I think I understood some of it at least...

I certainly had no idea it was such an involved process getting Chrome built, I thought it was just
git pull; configure; make; make install

[Catweazle]

@jane-n , although I am not a programmer, I am quite clear that if you want to fork a Chromium (or other engine) for several different OS and do more than just change the logo, you have to invest a lot of work. A lot for a small team that has Vivaldi, which I really appreciate.

[guigirl]

My friend just read it, then exclaimed...

Well i'll be damned, til now i thought it was just a matter of sticking a V label neatly over the top of the C label.

Silly duffer, my friend.

[LonM]

For me what always shocks me is how much time and effort goes into merging each new chrome patch. That effort probably goes unseen for most people, but just know that it is greatly appreciated.

[Ayespy]

@LonM "...probably goes unseen for most people,..."

Let's be more objective. "certainly goes unseen for nearly everyone...."

[ingolftopf]

Thank you very much for your great work.