Comment by bazoom42
6 months ago
Chrome clearly outcompeted Firefox despite Firefox’ faster XSLT implematation, so perhaps the performance of a feature which is almost never used is not that significant either way?
6 months ago
Chrome clearly outcompeted Firefox despite Firefox’ faster XSLT implematation, so perhaps the performance of a feature which is almost never used is not that significant either way?
Chrome is outcompeting (or cripling) Firefox - in taking control from the user, payed by the user - right now, with your comment all backward (and catch 22, cross-browser functionality bugs never to be fixed).
All downvoted ? If not performance of [ONE] feature like JS engine, what would make Chrome better ? (crippling others). JS is used so much only because all other options are kept broken (since Microsoft JS XMLHttpRequest - for applications not documents, being the lowest common denominator - against few bugs that needed to be fixed, not much changed) - otherwise there will be no need of JS for documents processing and less energy wasted - and the bill is payed not by corporations but by users, with extra tracking taxes.
Are you arguing XSLT can do anything JS can do? Because that is obviously not true.
4 replies →