Re:Fossil versus Git
by sausagefeet on Saturday September 23, 2023 @08:45AM
(#37622763)
"One thing" depends on how you squint, though. If you view "version and track text information" then it makes sense to store tickets, wiki, code, yadda under the same tool.
I'm primarily a command line user, I don't use explorer to view, rename, move, copy files etc. Like I said, unix-y. If you think "manage computer stuffs" the OS should bundle all tools anybody could ever want.
Most popular Linux distros include a whole lot more than just a stripped down kernel.
Exactly, they include other programs. They don't ship a kernel that includes a music player.
That's a meaningless distribution as far as most OS uses are concerned.
Re:Fossil versus Git
by sausagefeet on Sunday September 24, 2023 @09:01AM
(#37632736)
And yet you don't use different file systems for small files vs large files, for text vs movies. One assumes that a filesystem can handle all of that kind of data. But one layer above we don't want all those under a unified interface.
> And yet you don't use different file systems for small files vs large files, for text vs movies.
Um, yes, I do. Not that it matters anyway, filesystems are not optimized to handle source code to begin with, they deal well with sectors/blocks and do that well.
Not sure how that's relevant, but I have ~150 repos locally and less than 10 on github. I also like the unix philosophy of having tools that do one thing and do it well.