←back to thread

Et Tu, Grammarly?

(dbushell.com)
279 points dbushell | 1 comments | 29 Mar 25 10:27 UTC | HN request time: 0.2s | source
Show context
emptysea ◴[29 Mar 25 15:40 UTC] No.43516362[source]▶
At work we have a lot of sentry errors related to browser extensions doing weird stuff.

Chrome’s Google translate is also notorious for breaking react based sites.

It ends up being a tedious triage process to ignore each new extension issue. We use the client side filtering to reduce our ingest volume. In general we have to have a lot higher thresholds to handle the noise vs our backends.

replies(2): >>43516812 #>>43516871 #
1. MartijnHols ◴[29 Mar 25 16:58 UTC] No.43516871[source]▶
It's not just noise though; clients are actually experiencing crashes and other issues because of it. I wrote an in-depth article on the Google Translate extension's interference of React (and other webapps): https://martijnhols.nl/blog/everything-about-google-translat...

It's no wonder frontend has a lot more errors, after all it has to support so many more client variations than a typical backend. It can be very hard to make a big webapp that works well for everyone.