Erik Wittern

I believe you understand it correctly. That said, compiler performance (i.e., type checking performance) is an issue in many code bases, including the one in our company.

Agreed, a universally applicable rule is hard to write. Our implementation is most definitely incomplete, but for us, it basically removed all crashes. Maybe someone feels compelled to improve on the implementation, we are happy to receive PRs.

GitHub - getcouped/eslint-plugin-react-google-translate: ESlint plugin for highlighting React patterns which can potentially cause browser exceptions while Google Translate is in use. ESlint plugin for highlighting React patterns which can potentially cause browser exceptions while Google Translate is in use. - getcouped/eslint-plugin-react-google-translate

Whether your app breaks because of the Google Translate "invasion" depends on its structure. You can make an app robust by avoiding certain patterns (e.g., sibling text nodes). We wrote an ESLint plugin to detect (some) problematic cases, which resolved the issue for us 🤞: github.com/getcouped/es...

The 2023 way of doing it could be favorable, especially to junior devs: one sees an answer plus context, one has to understand it to make it work.

But maybe AI tools could do more to close that gap, like provide rationale, pros and cons, potential weaknesses of the code suggestion etc.