3 ms·
Because I'm the only one using it, it occassionally has backwards incompatible API changes, most browsers ship with their own engines, it has a compilation step
by kodablah 8y ago
Because I'm the only one using it, it occassionally has backwards incompatible API changes, most browsers ship with their own engines, it has a compilation step anyways for the wrapper, it is self-contained, etc. How do these packages ship Chrome or FF? They don't make them ship Blink or Gecko as shared system-wide libs IIRC. My browser is no different. (now, Qt on the other hand, is a different story, like Gtk or whatever)
- The-Compiler 8y agoChromium and Firefox are kind of an exception there, as they are big enough for distributions to justify bundling the engine, and they are also the upstream projects where those engines are developed.