>> Thank you for this list. I started reading through it, but I noticed a high
>> percentage of patches that were port-specific build fixes or port-specific
>> features like support for legacy ARM chips. For example, “...on ARM
>> traditional” (<https://trac.webkit.org/changeset/142616>). Those patches are
>> cost to core WebKit development, not benefit.
> I don't want to mis-interpret your statement here. Can you clarify what you
> mean by "Those
> patches are cost to core WebKit development, not benefit.”
Consider <https://bugs.webkit.org/show_bug.cgi?id=117281> — a patch for legacy
CPUs that don’t have floating point processing. That patch took three months of
reviews, spanning three different core JavaScript hackers, to get right. And
after that, it was still wrong, and it required three follow-up fixes.
That’s cost.
Geoff
_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev
