Code Reuse in Google Chrome Browser

Well, technically, Google chrome *isn't* performing code reuse. It both is and it isn't.

Googles 'reuse' is right on par ( as far as linux is concerned at least ) with people copy-pasting code all over their program, and this really is poor.

I downloaded the source a while back when it first came out and discovered lots of the libraries included with it, but this is *not* the way to do things.

At that stage the backend was alleged to compile, but their methodology was completely back to front. Their build system mostly entails rebuilding all those libraries they bundled in with chrome, albeit with their special build system, with their special patches to these libraries.

And this is something most windows centric devs just don't understand, because they don't have much of a concept of shared libraries and what they bring to the party.

Building google-special versions of dozens of libraries does nothing but send opensource development backwards, because it increases the number of copies of libraries with the exact same name, and the exact same purpose on your system needlessly, which both 1) wastes lots of build time 2) wastes disk space, 3) wastes memory with the multiple copies of libraries in ram 4) reduces security by not working with the *existing* system libraries which are tailored to the system.

Granted on windows you're not likely to have all the dependencies needed to make it tick, but there's no good reason to bundle these in chromes source.

They should be installed separately, possibly as a bundle, and built against the sources, that are provided pristine from upstream, and if something in a library is not to your liking, report a bug, get it fixed, and help the rest of us out instead of just going out and doing things different in progressively backwards and unmaintainable ways.

We people on Linux have solved the issue of 3rd party libraries years ago, so just put in dependences and let the distros install them and then use those.

sorry, can't continue line of thought, distractions broke the rant, so it may lose coherence near the end.