Hacker News new | ask | show | jobs
by Nextgrid 1433 days ago
I really can't think of how you can lose money because of a browser bug unless you put so much intentional complexity in what is essentially a CRUD app that a browser bug could trigger disastrous failure, in which case the fault is on the developer for overengineering rather than any browser bug.
1 comments

Yeah, this seems like a red herring at best.

I understand an argument against continuing to test, even though I find it insufficient, but liability doesn’t make sense here.