I think that flu thing is an old wives tale. You usually get flu because you breathed it in. The association with cold is because during cold weather people spend more time in poorly ventilated areas.
I think that flu thing is an old wives tale. You usually get flu because you breathed it in. The association with cold is because during cold weather people spend more time in poorly ventilated areas.
Same. Often finish the can with a feeling of disappointment and thirst.
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.
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.
Maybe they’re planning on dying before then? In which case they’re fine.
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.
There are no gay people in Russia.
Thanks, that’s very kind!
Whatever you say kiddo
Yeah I’m curious as to whether there’s not merit in taking the imperfect codebase and improving it.
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.
I agree mostly, but forks don’t need to keep the upstream. They can go their own way.
Could they not add HEVC support? Or is there some technical limitation that meant starting from zero was a good idea?
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.
Well he didn’t just get takeout for some reason /s
Did you consider getting takeout?
Because that was what the article was about…I actually am a Linux user and fan, folks just misreading the intentions of my post.
I would genuinely love to see it, because I’m stuck on mac hardware to do my job and I really hope one day they get crucified for their anticompetative practices so I can freely choose the OS my business uses.
Que no los dos?
Well to be fair it probably is pessimism. That doesn’t make you a pessimist in the same way that me expecting to wake up every morning doesn’t make me an optimist.