el_abuelo

joined 1 year ago
[–] [email protected] 3 points 2 months ago (3 children)

Yes. Not intentionally of course. But yes.

I don't see how your way is any more predictable or consistent than using UTC. What even is "local time"? Are you assuming they haven't changed timezone since they created the data? Say....DST happened, or they drove over a border...?

Storing and manipulating in UTC is the most predictable and consistent because it is universal and unchanging. You only need to worry about "local time" at the point of displaying it.

[–] [email protected] 1 points 2 months ago

So many things would be fucked by a TZ change that it very rarely makes sense to consider it.

You're making a calendar app? Fuck it...some folks are gonna get confused...solved by simply emailing your users and telling them to reschedule shit because there's kind of a big event going on that everyone knows about and has been planning for for years. Hell in all liklihood this is probably easily solved by simply doing a mass migration of events scheduled before the TZ change.

You're coding for nuclear weapons? Maybe consider it. But probably not.

That is to say: there are ways to solve problems without resorting to writing the most complicated bullshit code ever seen. Unless of course you work on my team - in which case you'd be right at home.

[–] [email protected] 1 points 2 months ago* (last edited 2 months ago)

Maybe they're planning on dying before then? In which case they're fine.

[–] [email protected] 6 points 2 months ago (5 children)

Your comment is a full throated endorsement of just working in UTC up until the presentation layer. Whether you intended that or not is another question.

[–] [email protected] 36 points 2 months ago (1 children)

There are no gay people in Russia.

[–] [email protected] 3 points 2 months ago (1 children)

Yeah I'm curious as to whether there's not merit in taking the imperfect codebase and improving it.

[–] [email protected] 2 points 2 months ago (3 children)

It's easy to understand when you think most comments are similar to yours and don't provide any insight as to why this might be a problem.

Maybe you could update your post and share your knowledge and experience with others, so that there are less people in the world who don't see the problem.

[–] [email protected] 5 points 2 months ago

I agree mostly, but forks don't need to keep the upstream. They can go their own way.

[–] [email protected] 6 points 2 months ago (14 children)

Could they not add HEVC support? Or is there some technical limitation that meant starting from zero was a good idea?

[–] [email protected] 2 points 2 months ago

Yeah the US differs by a couple of weeks iirc

[–] [email protected] 8 points 2 months ago (4 children)
[–] [email protected] 4 points 2 months ago (1 children)

Um....delivering?

Maybe I'm missing the point as I'm not from the US (and I assume from your content that you are) - but here we pay a delivery fee which covers the cost of delivery, and a tip is an optional bonus for the delivery person if you feel like they went beyond.

view more: next ›