Can nvenc do dual pass encodings these days?

This section contains his reasoning.

Wow what a betrayal, poor guy. He works for an open source release for a year and they just rip it away from him. Fuck Alex Austin.

Yes, movie people complain that more than 24 fps looks like soap operas (because digital TV studio cameras moved to 60 fps first).

I think it’s all performative bullshit, not good policy.

Some decision maker has to appear innovative to his superiours, so he decides to have some number of locations assigned to a trial group and some bullshit installed. Even if it fails, just as long as he finds the right moment to start appearing critical of the experiment he can still pull off his play. After all moving fast and failing fast are also virtue in modern corporate bullshit lingo.

By their admins setting HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\Common\General PreferCloudSaveLocations to 0 using GPO probably

Ahh right! Thanks for correcting me. Now that you mention it I remember too. It also makes sense, a year is roughly 365.2425 days long. Add 0.25 (one out of four), subtract 0.01 (one out of hundred), add another 0.0025 (2.5 out of thousand which is 1 out of 400)

Leap years are each fourth year, except each hundredth year, except each thousandth fourhundredth year.

1896 leap year
1900 not leap year
1904 leap year
…
1996 leap year
2000 leap year
2004 leap year
…
2096 leap year
2100 not leap year
2104 leap year

Then you just arrange the 10 year window in different positions to overlap 1 to 3 leap years to reveal the three outcomes of the bug.

- / - - - / - - - /
- - / - - - / - - -
- - 0 - - - / - - -

- is a normal year, / is a leap year, 0 is an exceptional non-leap year.

Sure, here’s one example for each case:

1 day off: 3650 days before 1907-01-01 is 1897-01-02

2 days off: 3650 days before 2027-01-01 is 2017-01-03

3 days off: 3650 days before 2025-01-01 is 2015-01-04

The python version seems buggy as fuck. Depending on which year you run it it’s off by 1-3 days

To be a little more precise, Linux is still available for 32-bit x86, just not from the Fedora distro. The Linux project is just now dropping support for 486 CPUs, because the maintenance burden for a virtually unused system type is too high for the mainline. That still leaves 32-bit Pentiums and newer though.

Is dropping support for 32bit hardware more important than being able to run on everything?

Yes evidently, because they dropped that hardware support in 2019. Specifically they dropped 32-bit x86 kernels in Fedora 31

lol, the “j l’ai lu” domain is pretty funny