If the architecture is irrelevant and it's just a matter of turning it on by default they could have done that with LFS long ago.

Git lfs can't do it by default because:

1. It is a separate tool that has to be installed separately from git

2. It works by using git filters and git hooks, which need to be set up locally.

Something built in to git doesn't have those problems.

But then they could have just taken the LFS plugin and made it a core part of git, if that were the only problems.

	▲	thayne 2 days ago \| parent [-]
		If it didn't have those problems, it wouldn't really be git lfs, it would be something else.