Technology
This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.
Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.
Rules:
1: All Lemmy rules apply
2: Do not post low effort posts
3: NEVER post naziped*gore stuff
4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.
5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)
6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist
7: crypto related posts, unless essential, are disallowed
view the rest of the comments
Why use these numbers when the number in question is 9 years?
I can certainly say that 9 years is too long to fail to update a map that contains a dangerous route.
I guess you missed the point.
Yes, we can all certainly say that's too long.
But carry that thought farther as I explained.
If you are going to make someone legally responsible for something like this, you need to draw a line where it is.
So where do you draw that line?
You reasonable can not, and that is because the premise that Google should be responsible for such a thing is ridiculous.
This case is just a standard US justice system where they just 'Sue everyone' and see where the chips fall.
This is a ridiculous argument. We set limits on things all the time. That the limit will be arbitrary doesn't mean there simply cannot be liability. 1 year is fine, 6 months is fine, hell, 1 month is fine. The company's internal processes will expand or contract to fit legal liability.
You don't need to draw a line for this case. You just need to decide if 9 years is too long.