> One dev allowed remote debugging which introduced a backdoor and what's really bad about it is there was no prompt that the remote debugger had been started. He said he thought it would make debugging easier
This is just the start of the madness. Mistakes like this are typically from so-called JS/TS developers who ‘think’ they can maintain core browser technology.
We’ll certainly get more of these typical amateur mistakes in the AI age, and will certainly get this from vibe-coders who completely have no idea what they are doing.
This is a different league in engineering and we’re starting to realize that perhaps it is a bad idea to hire devs who have little experience in building production-grade browsers because they are too used to tolerating the clumsiness of the JS/TS ecosystem.