Cet article explique en détail pourquoi Chromium n'est pas dans les dépôts de base Fedra, et c'est intéressant. Il explique en particulier que Chromium ne cherche pas a améliorer les bibliothèques qu'il utilise et à faire remonter les changements upstream, et qu'ils préfèrent embarquer des versions modifiées de ces bibliothèques. Un peu comme debian quoi.
Google is forking existing FOSS code bits for Chromium like a rabbit makes babies: frequently, and usually, without much thought. Rather than leverage the existing APIs from upstream projects like icu, libjingle, and sqlite (just to name a few), they simply fork a point in time of that code and hack their API to shreds for chromium to use. This is akin to much of the Java methodology, which I can sum up as "I'd like to use this third-party code, but my application is too special to use it as is, so I covered it with Bedazzler Jewels and Neon Underlighting, then bury my blinged out copy in my application.". A fair amount of the upstream Chromium devs seem to have Java backgrounds, which may explain this behavior, but it does not excuse it. This behavior should be a last resort, not a first instinct.
# Pourquoi Chromium n'est pas chez Fedora
Posté par Mildred (site web personnel) . En réponse au sondage Chromium / Google Chrome sous Linux. Évalué à 2.
Cet article explique en détail pourquoi Chromium n'est pas dans les dépôts de base Fedra, et c'est intéressant. Il explique en particulier que Chromium ne cherche pas a améliorer les bibliothèques qu'il utilise et à faire remonter les changements upstream, et qu'ils préfèrent embarquer des versions modifiées de ces bibliothèques. Un peu comme debian quoi.
Google is forking existing FOSS code bits for Chromium like a rabbit makes babies: frequently, and usually, without much thought. Rather than leverage the existing APIs from upstream projects like icu, libjingle, and sqlite (just to name a few), they simply fork a point in time of that code and hack their API to shreds for chromium to use. This is akin to much of the Java methodology, which I can sum up as "I'd like to use this third-party code, but my application is too special to use it as is, so I covered it with Bedazzler Jewels and Neon Underlighting, then bury my blinged out copy in my application.". A fair amount of the upstream Chromium devs seem to have Java backgrounds, which may explain this behavior, but it does not excuse it. This behavior should be a last resort, not a first instinct.