3 ms·
> Is it because it is 4:45ET? Then why not list it as that? Because a lot of their customers are too stupid to understand timezones.
by lmm 2y ago
> Is it because it is 4:45ET? Then why not list it as that?
Because a lot of their customers are too stupid to understand timezones.
- dylan604 2y agoI guess that's saying more about the left coast customers then, right? as all of the customers from the other time zones have to do the conversion.
- lmm 2y agoWell, if someone misunderstands and sends their payment by 1:45ET or 1:45CT, it's not a problem for the bank.
- hinkley 2y agoIf more businesses were based in Indiana we would understand this problem better. Gary Indiana is a population center on Lake Michigan, across the Illinois/Indiana border from the Chicago exurbs. They’ve elected to be in the same time zone as Illinois, while the rest of the state is in the same time zone as Ohio. And 1997-2006 was just a clusterfuck where another county joined with Gary, and a bunch of counties decided not to follow DST. I am not smart enough to know what time it is without asking a computer.
- DiggyJohnson 2y agoThis is just a rude guess and not relevant to the actual reason
- lmm 2y agoRude perhaps, but I think it very much is the actual reason. "If they listed it as 4:45ET their support costs would be higher" is perhaps the more polite way of putting it, but the meaning is not actually any different.
- hinkley 2y agoI’m too stupid to understand time zones. Because everyone is too stupid to understand them at 2 am when alarms are going off. All backends should always be in UTC, even if your boss tells you we will “never” move our servers to another time zone. Because they’re going to buy or be bought by a company based in Chicago or New York or find a vertical so fat they want a second office there, or both. And then they will not remember promising you that you would never have to do a time zone migration. Why are you being so grumpy, just fix it?