3 ms·

You're inventing hypotheticals to say why they're going to charge you more, without evidence. Pay-per-minute autonomous driving is far more like old pay-per-mi

by SamBam 5y ago

You're inventing hypotheticals to say why they're going to charge you more, without evidence. Pay-per-minute autonomous driving is far more like old pay-per-minute phone plans than it is mystery-AWS-data-charges. You know when it's driving and when it's not. There's no unforeseeable per-lambda charges about it.

lp0_on_fire 5y ago
I think it's reasonable to worry that WV or another company might start charging a variable rate for different "types" of autonomous driving. Pay-per-minute phone plans could be just as mysterious when you factored in long distance and peak usage hours. It's not a huge logical leap to think that a subscription based service like this could lead to things such as: You want to travel between point A and B several miles apart in rural Kansas on a straight road with a road density of 2 vehicles per mile? "Sure, that's 8.50 an hour." Oh, you want to travel between Newark and Manhattan in the middle of a snowstorm? "That will be 15 an hour because we have to cover the costs for the real-time feed of data from our weather and control center" Oh, you have a camper, too? "That's an additional 2 bucks an hour for our towing package" Oh, you're traveling across state lines and the state over imposes an additional tax on autonomous driving. "we need to charge you 8.75 to cover the tax and our costs but only in that state."
dmitriid 5y ago
> You're inventing hypotheticals to say why they're going to charge you more, without evidence. Ah yes. There's no evidence. Except the countless instances of dark patterns everywhere on the web tricking into you paying money. Countless instances where you can't cancel a subscription, and have to go through multiple hoops to do it. Countless instances when there's a runaway billing in a SaaS that leaves people with huge bills. But sure. These are all just "hypotheticals", and not the reality how the absolute vast majority of subscription business works. > You know when it's driving and when it's not. There's no unforeseeable per-lambda charges about it. Ah yes. Because of course it will be as simple as "when it's on, it will be charged", and not "when an obscure setting is on, you will be charged, regardless of whether it will be self-driving or not".

by SamBam 5y ago

lp0_on_fire 5y ago

I think it's reasonable to worry that WV or another company might start charging a variable rate for different "types" of autonomous driving. Pay-per-minute phone plans could be just as mysterious when you factored in long distance and peak usage hours. It's not a huge logical leap to think that a subscription based service like this could lead to things such as: You want to travel between point A and B several miles apart in rural Kansas on a straight road with a road density of 2 vehicles per mile? "Sure, that's 8.50 an hour." Oh, you want to travel between Newark and Manhattan in the middle of a snowstorm? "That will be 15 an hour because we have to cover the costs for the real-time feed of data from our weather and control center" Oh, you have a camper, too? "That's an additional 2 bucks an hour for our towing package" Oh, you're traveling across state lines and the state over imposes an additional tax on autonomous driving. "we need to charge you 8.75 to cover the tax and our costs but only in that state."

dmitriid 5y ago

> You're inventing hypotheticals to say why they're going to charge you more, without evidence. Ah yes. There's no evidence. Except the countless instances of dark patterns everywhere on the web tricking into you paying money. Countless instances where you can't cancel a subscription, and have to go through multiple hoops to do it. Countless instances when there's a runaway billing in a SaaS that leaves people with huge bills. But sure. These are all just "hypotheticals", and not the reality how the absolute vast majority of subscription business works. > You know when it's driving and when it's not. There's no unforeseeable per-lambda charges about it. Ah yes. Because of course it will be as simple as "when it's on, it will be charged", and not "when an obscure setting is on, you will be charged, regardless of whether it will be self-driving or not".