bro really didnt notice 1601 is start of a century (thus start of a "cycle") jk, anyways nice vid

It makes sense that MacOS uses the UNIX epoch, since it uses UNIX as its foundation.

1601 was chosen because it was a 400-year leap year cycle (No leap year every 100 years, but a leap year every 400)

Apple is trash, who'd have guessed!

It would be interesting to know what the accurate timestamp would be on the oldest file that still exists. In my work, I've had to modify files from 1983 that were ported from old DOS systems. I suppose it would date back to early versions of UNIX.

You probably should just let the system date be the date the old photo was digitized and put the date take in the damn file name

Why not TempleOS?

A folder of pictures of Josh Hutcherson is so real lmao

i love how in windows and linux you can edit the creation and last modify date on a file, makes it so easy to fake dates to make ARGs and stuff!

32 bit Unix time can use timestamps between 1901-2038, 64 bit Unix time can use timestamps between 292.3 billion years in both directions which every modern Unix-like including Linux and Mac OS uses, pretty sure Mac OS' implementation is only broken on gui level

On December 21st, 1677, a significant historical event was the siege of Cambrai, which was part of the ongoing Franco-Dutch war, where the French forces were laying siege to the city of Cambrai in the present-day northern France. I hope this helps...

January 1st 1601 is the first day of the 17th century

I never thought about sitting in a historical photo's timestamp today it was actually taken, that could be very useful.

unix epoch should be 64 bit not 32 bit, 32 bit unix epoch will reach it's limit in a couple of years lol

I don’t think it matters when the Gregorian calendar was adopted, but how the current way of computing leap years can be extrapolated to the past

Wait, so Linus become unusable as early as 2040?

never had this question but how old CAN a file be?

What happens if you try to set the date earlier in Linux?

MacOS is just Mack these days, right? So it's Pre-Mach UI bolted on top of a Mach reskin... which makes sense that it's like Windows with regard to time (all over the place) but just uses the Epoch like Mach does.

I even have files from the future

Ngl I thought you meant how old a file can be via aging, not setting a date on it

11:27 The C# programming language does something even crazier: they start all the way back from 1 January 1 AD in the proleptic Gregorian calendar and then increments by tenth-microseconds in signed 64-bit integers (same thing as Windows but starting at year 1 instead of year 1601). While .NET itself only supports dates between 1/1/1 00:00:00.0000000 and 31/12/9999 23:59:59.9999999, C# can theoretically represent dates and times between 17/4/29227BC 21:11:54.5224192 and 14/9/29228AD 02:48:05.4775807.

2262?! This is planned obsolescence from Apple. Outrageous!

Swift is a general-purpose cross-platform programming language, and it is not something that is tied with macOS. distantFuture is not a value related with APFS, but just something like Infinity but for dates.

I bet a lot of Mac OS X got messed with in the last 10 revisions of Mac OS X back before the invention of aPFS with the file system of HFS. of course there's also the Mac OS 9 and below the major redo.

My sata ssd had a corrupted file with the year 1968. It's a funny joke between me and my friend, he always said that I needed to reformat because my computer was getting corrupted files, I guess that file date was the best way of proving his point. 😂😂

Close enough. Welcome back, Science Elf.

I'm an ex forensics dev. We used to take extra care to properly extract even the weirdest file time metadata, but the average user typically complained if it was before 1970, so we ended up with a few workarounds to discard values which users wouldn't believe, even if that was _literally what the metadata said_. We got questions about those wack time zones too, for the dates which were sufficiently far back. Well, before time zones were fixed, everyone used to use their actual offset based on the city they lived in. So TZDB occasionally records that sort of trivia and uses it for sufficiently old dates. So for example, the time zone Australia/Sydney has an offset of UTC+10:04:52, until Feb 1895. Also, 2001 and 1601 were probably chosen for the same reason - it's the first year after a leap year, which makes leap year calculations much more convenient.

I have a note for Linux: convert over to 64-bit before we get another Y2K bug. 64-bit can represent time out to the heat death of the universe.

Re: Linux, the main reason for its consistency is that it's one platform API all the way through (POSIX) and the filesystems were designed to that spec... just take a look at how messy backward-compatible preparation for Y2K38 is making things. (eg. compare what ext4 is doing vs. XFS vs. libc vs. ...)

Re: macOS, it'd be interesting to see whether those mismatches between the POSIX parts of macOS and the Cocoa parts of macOS originate in OpenStep (where Cocoa has its roots in) or classic Mac OS via Carbon. I imagine they're at least partly the same as how many of Win32's warts were down to making sure that it'd be easy for Win16 programmers to transition their skills over.

The TL;DR for why NTFS can represent dates that Explorer can't display is probably down to "NT Kernel Subsystems"... 1990s Microsoft's plan for the NT kernel to be able to natively expose Win32, UNIX, and OS/2 personalities. Basically, the Win32 APIs that Explorer uses are NOT the NT kernel's native API... it's sort of like kernel-level Wine, except that the POSIX API used in WSL is a sibling, not a parent. That's also why it's possible for NTFS to store paths containing characters that are invalid on Windows, and to store case-sensitive filenames, if you know how to bypass the DOS-compatible translation layer. For all Windows's flaws, the NT kernel really is a nice piece of engineering. (The kernel's internal path mapper even supports null bytes in paths because it uses Pascal/Rust-style counted strings internally.)

"it is weird that X part of windows support something Y part of windows does" You don't say. NTFS paths are case sensitive, there is no need for drive letter either. Those are now limitations from the Win32 subsystem of the NT operating system. Not the OS "proper"

TIL Americans say epoch like epic

Now I wonder how old can a file be legitimately. No date editing, like, when was the first file that can be taken to something like windows and see the date

so if the maximum number of seconds Linux can understand represents about 69 years from it's reference date, does it mean that a bunch of Linux systems will have to be updated to support dates after 2039?

this 1601 thing is conected to leap years 1600 is special leap year divisible by 100 and 400 at the same time en.wikipedia.org/wiki/Leap_year

EE-POCK for the love of god!

The cycles of the Gregorian calendar are, by my understanding, just a happy accident. Any span of 400 consecutive years within the Gregorian calendar will be exactly 146 097 d = 20 871 wk. Had they chosen 1600, it would be offset from how we count centuries, which are the way they are because there is no year 0, as it goes 3 BC, 2 BC, 1 BC, 1 AD, 2 AD, 3 AD, etc.

I also don't think you can say Ubuntu is doing a good job because with that epoch and 32 bits, in 2038 you're shit out of luck.

You could have looked at what the type of the value used for time intervals is on macOS… It's a number of seconds using a Double, i.e. floating point.

it's pronounced e-poc not epic

I thought this was going to be about how long data can last on a usb or some sort of hard drive until it’s corrupt

Opening this video I thought "Unix Time, 1970", but you too said that immediately. Then I remembered I once had corrupt files on a USB Stick dated to 1901 and I was curious if that year would come up and lo and behold - Unix time, but negative. Neat!

It's *EPOCH* If you're going to be _less than epic_ and mispronounce it, at least SPELL it correct!!! Like saying Spock without the S and a hard E... "E-pock" like the French say it actually.

"More on that later" Didn't realise i was watching Dev's Game Dungeon

on my old iphone 11 i had a picture of salami that was dated as being from december 1903 for some reason

epoch and epic are to totally different words, even pronounced different.... enough with the BS...ya typical linux flog..its not funny ...its not entertaining... ya just teaching morons how to be better at being morons... i guess theres a silver lining...they are learning from the best of the best...SMH

1949 can be Y2K problem, because one of workarounds was to treat dates >=50 as 19xx and <50 as 20xx

1601 is first non leap year of 400 year cycle in Greogrian Calendar. Some times date is result of choosing that calendar starts in monday on sunday, in Clarion language it was days from 28 December 1800 for date Field, for time type it was minutes from 1 Jan 1990 ;) Excel as i rember has also 1901 (but it may be diffrent bettwen Mac and PC ;)