please yell at me in the replies, i thrive on confrontation

This is like when people insist they’re alpha. That is to say, if you have to say it, it’s probably not true.

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.

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.

Ummmm you might care to remember that the USSR also “bailed out” Europe.

You know…in the sense that you were dragged into a war you had no intention of joining, by a foe that had already gone 11 rounds with the UK and Russia.

The UK spent an entire empire “bailing out” europe. Twice. But we don’t hark on about it.

But you’re right about one thing - no one is coming to bail you out. You’ve made it abundantly clear you will only act unilaterally. Europe will stay in its lane, quietly hope that Trump has a stroke, but ready to stand on its own for a 3rd time.

Sure if that works for you.

There are very few people in my field who can compete with me when it comes to capability and productivity - and that’s in a highly developed country with some of the world’s best educational institutions and companies to gain experience with.

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.

Pretty sure our right wing is left of your left wing. So no you can’t have it because you don’t have a system that supports anything other than the right-wing hellscape you got now.

As long as the upper tube underlaps the lower tube, all is good. If it overlaps though then yes, problem.

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?

Bodacious