zgk7iqea

Don't cursor and vscode also have this problem?

Is phone number enumeration now considered a vulnerability? Really?

the age of subscriptions. what, you don't want to subscribe?

theres a clippy lint for that

Mozilla is an advertising company too. In terms of breakage, Im talking about more fundamental things like missing APIs and wrong rendering.

it is an architecture problem, too. LLMs simply aren't capable of AGI

it's the same kind of "workflow optimization" that notion and obsidian users suffer from. You spend so much time making your tools more productive but don't get any actual work done.

better spend your time well

Firefox should commit more to correctly implement web standards - not even gradients render correctly. A lot of the users are oddballs with strange configurations that break everything. No wonder devs optimize for chrome.

This is just as user friendly as the rest of the firefox configuration. I can't recommend it to anyone in good faith anymore.

google is a customer of fflabs and has enrolled them in summer of code. They also provide free fuzzing. ffmpeg is a foss, gpl-licensed project. nobody has any obligation to contribute, thus it isn't exploitation.

Very interesting, thanks.

One point from one of the linked threads I find particularly puzzling:

> I think the issue with XSLT isn't necessarily the size of the attack surface, it's the lack of attention and usage.

> I.e. nearly 100% of sites use JS, while 1/10000 of those use XSLT. So all of the engineering energy (rightfully) goes to JS, not XSLT.

XSLT is a finished standard. Not everything needs to evolve. If the implementation works and is safe, what speaks against keeping it?

Why not just write an XSLT implementation in JS/WASM, or compile the existing one to WASM? This is the same approach that Firefox uses for PDFs and Ruffle for Flash. That way it is still supported by the browser and sandboxed.