News for hackers. Stuff that matters.
Re:Et Tu, Grammarly? by eadmund on Saturday March 29, 2025 @08:36AM (#43515058)
I don’t think that ‘hostile’ is really fair in this case, when ‘insufficiently competent’ will do (albeit at the cost of more syllables).

I am not a fan of Grammarly or their technical model, but I don think it’s fair to attribute malice when it is adequately explained by stupidity.

It’s been a long time since I did any front-end work: should both Grammarly’s extension and your own code use namespaced property names?

Re:Et Tu, Grammarly? by chuckadams on Saturday March 29, 2025 @11:55AM (#43516464)
Any sufficiently advanced stupidity is indistinguishable from malice.
Re:Et Tu, Grammarly? by QuadmasterXLII on Saturday March 29, 2025 @11:29AM (#43516294)
We tried applying cunningham’s law widely and it created disastrous incentives. It’s better to assume profitable yet destructive incompetence is malice.
Re:Et Tu, Grammarly? by dbushell on Saturday March 29, 2025 @08:42AM (#43515091)
yep, it's in Grammarly's interest to namespace or scope their CSS in a way that doesn't conflict. Not doing it adequately goes both ways, website CSS could break their extension, or their extension could break the website.
Re:Et Tu, Grammarly? by MartijnHols on Saturday March 29, 2025 @01:05PM (#43516925)
Unfortunately browsers don't really provide good solutions for extensions that need to inject or change sites. Look at Google's owner in-browser translate extension, its DOM manipulation breaks many interactive apps as well. There are no tools available in browsers for it to not need to do that.