RE: https://mastodon.gamedev.place/@eniko/116930705404535012
The piece of software I want more than anything else is a fork of the Linux kernel from the commit immediately previous to LKML adopting their "AI code assistant commits allowed" policy
(And a fork of the kernel documentation from a few months earlier, as if I'm not mistaken they allowed "AI" there first)
I would also like to use "Mercurial"
(It is interesting that the one thing forcing me to use git is git-lfs, but git itself claims git-lfs is an external project and not a core git feature and refuses to look at bugs related to it. If it is external to git, how has it turned out so much more difficult to integrate it with hg or jj than it apparently is with git? Were there software architecture decision(s) which made that the case?)
@mcc git lfs is a hack to get functionality mercurial has natively, afaik
@mcc git also does, as of a few months ago: https://git-scm.com/docs/large-object-promisors
@mcc arguably this has been around since 2017, the primary goal of git lfs is so that a clone doesn't need to include old versions of large files that aren't present in the latest commit. this has been possible in git since 2017 via git clone --filter, the new effort is focused on making it possible to split large files and small files into different remotes (where the large file remote can be ex. a plain s3 bucket)
@leo git and mercurial aren't real; the real thing is github or bitbucket. because mercurial lfs has, to my knowledge, never been supported by a "foundry", mercurial lfs is not real.
@leo Huh. Does this mean they're finally going to fix the incompatibility between git archive and git-lfs
@mcc while we’re at it, can we dispose systemd and alsa as well? I might be too old to deal with that level of burocracy around everything. Maybe i just need to switch back to *bsd, if that’s reasonable on a thinkpad.
@Rk systemd is also slopcode, so if we're getting rid of systemd it has to go soon.
This aside don't have much patience for the "new thing is worse" philosophy that has linux users hating systemd and alsa. Maybe it's true alsa sucks but I think the old linux thing sucked also. I like launchd and coreaudio and quartz. I want something at the quality of Mac OS X 10.3. Not only can Linux not provide this, it insists I accept software written by "claude" onto my computer. Unimpressive.
@leo additionally, since bitbucket went away, i would describe git as "the mercurial wire protocol"
Luckily FreeBSD still has a pretty solid anti-AI-code position. I'll be switching over to that soon.
Among linux distros, gentoo seems to have the strongest stance against AI-code (not a total ban, but clear requirements for human oversight). But that still uses the now-AI-coded kernel.
@mcc agreed, i just want to have something that is not architecture tripping and fit for the purpose. I don’t care if it’s new or old, I just don’t want to waste days to integrate stuff. Dealing with all that in embedded systems has provided for endless pain, to the point I refuse jobs having me facing that. At this point, I welcome something new. But not slop. That’s my first non functional requirement.
@mcc fossil + huge repos or...
jj config set --repo snapshot.max-new-file-size 0
never used hg or svn, but I assume they've just "always been better"
@julf I am aware I can give up my software stack and device drivers (already a smaller set of device drivers than is available on Windows) and switch to BSD. I imagine, if I can't get my demands satisfied by Linux, I will eventually do this. However this will be very unpleasant, as I will have to give up my software stack and device drivers. I want to be able to run video games and low-latency audio applications, especially since I"m no longer using Windows.
@inscript the purpose of "git-lfs" or a system like it is to avoid huge repos.
hg has a git-lfs like system which is, from my cursory review, architecturally superior to git-lfs, but to my knowledge it has never been actually deployed by a professional-quality file host. it's possible a small number of niche hosts like heptapod may have added support in the last few years.
svn has always been superior to git.
@mcc Fair enough. I haven't used Windows (except as something I occasionally boot up in a VM for some proprietary software). I still have Linux on several machines, but mostly Debian, as I feel Linux really jumped the shark with systemd.
@mcc clearly, I'm not yet ankle deep in the arcana. my bad g.
@mcc afaik heptapod is what most people who use mercurial use? hg-git is an unofficial compatibility layer and i do not think it's remotely fair to say mercurial doesn't support something because it doesn't work well with hg-git
@mcc mercurial does also have experimental support for using a git lfs blob server, it doesn't look like the repo side is compatible with git lfs but there are some comments implying it tries to coexist with hg-git https://foss.heptapod.net/mercurial/mercurial-devel/-/tree/branch/default/hgext/lfs?ref_type=heads
@mcc there's also an open jj pr that makes it not actively conflict with git lfs (though you still need to use the git cli for lfs files) https://github.com/jj-vcs/jj/pull/9635
@mcc Yeah, it would be really rad if someone said "cool, we're explicitly political linux and yes we're going to fork as you've been suggesting people can do for many years"
@mcc I was really sad that git beat mercurial. I thought mercurial was a far better dvcs.
Both of these unix like kernels have anti AI policies.
https://www.redox-os.org/ (mit / rust)
https://ironclad-os.org/ (GPL / ada)
@mcc
At this point, I am so fucking burnt on Linux, have had distasteful AI-brained interactions with enough FreeBSD people I won't touch that project, cant stomach how Rust is adopting slop so Redox is out...
Is there something like VitruvianOS in reverse, so I can run unmodified Linux userland stuff over HaikuOS?
Fuck it, maybe ReactOS at this point.
@mcc I prefer MUSL for many reasons, but I guess that would be a thing that would sidestep a lot of the ugliness... Even remotely tenable?
@mcc No, sorry, I'm doing the thing where I am conflating/confusing gcc with glibc. Sorry.