Files in Git don't have timestamps, only commits do. It got swept up when `git commit --date=...` was run.

oh I see. proper archeology would be to have more commits then

Funny part is, that NFSv4 supports SIDs for user authentication, but the Linux implementation leaves it out (among all the other ACL features) simply on the basis that Linux doesn't support them at all.

The FreeBSD, Solaris, Mac OS X, and Windows (yes, even Windows) implementations of NFSv4 are fully featured with this stuff.

I really wanted NFSv4 ACLs but Linux doesn't like it while FreeBSD doesn't make use of my hardware (intel p/e cores) in the most efficient way.

Related: Fossil has a `fusefs` subcommand: https://fossil-scm.org/home/help/fusefs

The DIRECTORY/checkins/ directory doesn't list out anything by itself, but you can look things up by any of the supported checkin names (hash, tag, branch, date...): https://fossil-scm.org/home/doc/trunk/www/checkin_names.wiki

Someday I’ll use fossil.

Someday (maybe if there’s a way to do Git LFS style stuff in it)

Consider Fossil[1], which packages the entire repository state—code history, wiki, tickets, forum—into a single file, and that state gets cloned.

When/if you need to change hosting providers, you get to lose zero data in Fossil because of it.

[1] https://fossil-scm.org/

I considered Fossil several years ago and while it's really cool (everything being integrated is awesome), I don't like Fossil from a philosophical perspective. There's no way to clean up history, it preserves everything as is. If that's what you want, great, but as part of my git workflow I like to mess around and then go back and clean up and organize my commits before pushing them.

I love fossil. Something about it's opinionated workflow that matches what I think. But

network effects. I just can not bring my team to use fossil. They have to share code with others. Other departments. And everyone (99%+) uses git. It just feels like a disservice to force them to use fossil. It is a catch-22.

It is similar to so many other things in the tech space. Trying to get fellow developers to use functional style idioms. Trying to enforce immutability. It is like something big (like a facebook or google project) has to force the community to get on board.

It was actually part of Microsoft Plus! for Windows 95. It wasn't directly available for Windows 98 at all, but the Windows 98 install disc does include an INF file so you can install it, provided you have a copy of Plus! for Windows 95.

It was also included with Windows NT 4.0, Windows 2000, Windows Me, and Windows XP (both the original and x64 versions). Finally removed in Vista to never return.

Raymond Chen has two blog posts that first describes why Space Cadet was removed because of a 64-bit rounding mode bug and then a follow-up post a decade later clarifying that that might not be the full story.

It's a fun bit of Windows history trivia.

- https://devblogs.microsoft.com/oldnewthing/20121218-00/?p=58... - https://devblogs.microsoft.com/oldnewthing/20220106-00/?p=10...

Delphi and Lazarus are still kicking, the latter is free and open source.

I know you asked for "the language", but Object Pascal really ain't that bad to get around. If you were proficient in VB6, you should be fine adapting. :-)

> "Right joins are just left joins in the wrong direction, you don't need that crap"

SQLite has supported all types of joins since version 3.39 in 2022.

I must've messed something up, but I remember some joins (was it full outer join?) being unbelievably slow? Was I doing something wrong?

Too vague of a question to give you an answer you'll likely sound satisfactory :)

You probably just needed to create indexes over your data to speed things up.

Well, look at that, now it is downhill from here!

I have bad news for you: Zip supports storing extended attributes as well.

Is Radicle an alternative to Fossil?

It seems to have similar ideas, but two big differences seem to be that 1. it's based on git 2. more focus on a truly decentralized p2p architecture

This is a current architectural limitation, manifests (defining check-ins) and tickets are different types of artifacts and you cannot combine the card types into the same artifact. Changing this would likely break backwards compatibility with previous Fossil versions and I'd expect resistance. It may still be worth bringing up on the Fossil forum if you desire the feature.

Personally speaking though, I don't want things automagically closed GitHub-style based on parsing a check-in comment. An issue ought to be closed with intention.

> I don't want things automagically closed GitHub-style based on parsing a check-in comment.

Sure, I get that. I was just disappointed that none of the project management stuff seemed terribly integrated in any way from my brief review. It seemed like opportunities there that were not taken.