Earlier quoted context omitted.
If you read that tweet, it mainly says that they made the choice based on DRM licensing. Well, plus a vague "it lost on many dimensions in a head to head comparison enumerating gaps vs. Chrome". Which I can't argue, because there are no specifics to disagree with. That said, I work on Gecko and it is indeed an old crufty codebase with numerous issues. From what I've seen of Blink, it seems surprisingly similar (overa…
DRM was not the main issue we faced, just one of many. I wasn't vague, Twitter limits size to 280 chars. We developed a decision spreadsheet with the data in almost all the rows weighing against Gecko. Your "seeming enthusiasm for burning some bridges behind him" is bunk. On what did you base it? Again, we started Brave based on Gecko (multiprocess sandboxed embedding via Graphene, which was developed for FirefoxOS).…
Perhaps "vague" is too loaded a word? I did not mean it as an insult or complaint, I was just pointing out the fact that the reasons were unclear because they were mentioned but not described. Twitter's character limit is a perfectly valid reason for that. And the literal meaning of the word "vague" applies perfectly.
> Your "seeming enthusiasm for burning some bridges behind him" is bunk. On what did you base it?
> ...To suggest I did anything uneconomic out of spite is silly.
I was not suggesting that.
Sorry, it seems I did not describe myself well. "Burning bridges" was not a reference to making anti-Gecko technical decisions. It's about unrelated public postings that I object to, but I don't think that here is a place to get into it.
I am confident that the bases for your technical choices were well-founded and I have no reason to suspect that they were made out of spite.