Random naive thought, could I use this to backup and version all of my user data? E.g. just point Lore at my ~/Documents folder and call it a day? I'm sure there's some scalability constraint but I have music projects, game projects, markdown notes, photos, videos, etc. and have thought in the past it'd be convenient to treat all my files like a monorepo.
Lore – Open source version control system designed for scalability
681–690 of 717 posts
Re: Lore – Open source version control system designed for scalability
#682Earlier quoted context omitted.
haha! The flaunt revisions flag is hilarious! --flaunt-revision= - Flaunt the revisions of extra commit IDs that are mirrorred. Is the tool taunting you?
afaik they're randomly generated so you're likely the first and last person to see that permutation
was wondering how and who created this site:)
Re: Lore – Open source version control system designed for scalability
#683Re: Lore – Open source version control system designed for scalability
#684Earlier quoted context omitted.
Well another factor could be that Perforce is a lot easier to use than Git - Actually, would like to think am good with git, but sometimes just wonder how it became so big considering the simple or important things (like check-ins and merges) are so complicated.
check-in isn’t a concept in git because there is no server in git. It’s just a log. The beauty of the merkle tree. It’s just GitHub became popular because people didn’t understand that you can rebase from any remote source. Delta patches become effortless
Oh sorry, yeah, didn't use the right term, meant commit... Still, conceptually in terms of source control, think it's the right term (meaning the process of having your code changes added into the main repo).
... and btw, haven't thought about git in awhile, and am reviewing its concepts. It does really have some nice features - always used to think the staging area was an unused feature (and at least for me, it kind of is), but local branches are super useful, and it seems like all that focus on git being a distributed vcs allows (and requires) a dev to work more locally first in very flexible ways. This is really, really nice. Still not sure all the complexity is worth it...
Know this has been said countless times, but some abstraction layer on top of git (that is actually apart of git itself so that it becomes standard) would have been really nice. Understandably, since git started its life in use by sharp linux-devs, usability probably wasn't at the forefront, but yeah, how many countless hours worldwide would have been saved if git was easier to use? (the dreaded botched friday-night commit and update)
Re: Lore – Open source version control system designed for scalability
#685Earlier quoted context omitted.
check-in isn’t a concept in git because there is no server in git. It’s just a log. The beauty of the merkle tree. It’s just GitHub became popular because people didn’t understand that you can rebase from any remote source. Delta patches become effortless
Oh sorry, yeah, didn't use the right term, meant commit... Still, conceptually in terms of source control, think it's the right term (meaning the process of having your code changes added into the main repo). ... and btw, haven't thought about git in awhile, and am reviewing its concepts. It does really have some nice features - always used to think the staging area was an unused feature (and at least for me, it kind…
Funny because `git pull` is an abstraction like you talk about. It's a `git fetch` followed by a `git rebase`. Staging or `stashing`, it's all just leaves on the merkle tree. The concept of time/branches/doesn't exist. Only previous hash, current hash. It's simple and people have ADDED complexity to make sense of it (coming from other VCS').
Re: Lore – Open source version control system designed for scalability
#686Earlier quoted context omitted.
In the US you can use Apple Pay anywhere NFC payments are accepted. It's generally completely open on the acceptance side at this point
It's anywhere close to open and requires vendors to seek approval from Apple for every implementation - Apple just has the market share to make everyone dance to their tune.
Apple Pay works on any terminal that supports NFC tap to pay payments. There are thousands, tens of thousands of terminals in the US that are not "Apple Pay" that you can use it on
Re: Lore – Open source version control system designed for scalability
#687Earlier quoted context omitted.
afaik they're randomly generated so you're likely the first and last person to see that permutation
was wondering how and who created this site:)
It's been around for over a decade at this point.
https://github.com/perotinus/git-man-page-generator
Earliest commits and mentions 2014. But could swear I saw it before that.
Re: Lore – Open source version control system designed for scalability
#688Earlier quoted context omitted.
was wondering how and who created this site:)
It's been around for over a decade at this point. https://github.com/perotinus/git-man-page-generator Earliest commits and mentions 2014. But could swear I saw it before that.
thanks for the history on this, funny stuff:)
Re: Lore – Open source version control system designed for scalability
#689Just today as I pushed some changes to Github, I was thinking how user-unfriendly Git's UI is: Enumerating objects: 5, done. Counting objects: 100% (5/5), done. Delta compression using up to 10 threads Compressing objects: 100% (3/3), done. Writing objects: 100% (3/3), 290 bytes | 290.00 KiB/s, done. Total 3 (delta 2), reused 0 (delta 0), pack-reused 0 remote: Resolving deltas: 100% (2/2), completed with 2 local obje…
Actually, it isn't that complicated. If you have a basic understanding of how git works (a little beyond just clone, commit, and push), this can be quite helpful when working with a slow connection or large repositories.
Re: Lore – Open source version control system designed for scalability
#690Earlier quoted context omitted.
Oh sorry, yeah, didn't use the right term, meant commit... Still, conceptually in terms of source control, think it's the right term (meaning the process of having your code changes added into the main repo). ... and btw, haven't thought about git in awhile, and am reviewing its concepts. It does really have some nice features - always used to think the staging area was an unused feature (and at least for me, it kind…
Funny because `git pull` is an abstraction like you talk about. It's a `git fetch` followed by a `git rebase`. Staging or `stashing`, it's all just leaves on the merkle tree. The concept of time/branches/doesn't exist. Only previous hash, current hash. It's simple and people have ADDED complexity to make sense of it (coming from other VCS').
True, the pull command is simple. But it's really the pushing and merging that cause the problems.
And, yeah, don't know if i'd call it simple in the way you're using the word. It's simple in that the tool is very "RISC" in nature instead of CISC, doing smaller simple operations instead of larger more complex ones (except for a few exceptions like pull). But for procedures like pushing your code, it's complex. You have to do a lot of things yourself that other VCS take care of. As you probably are aware of, you need to make sure you do things in the correct order, because the tool won't help you if you make a mistake. Don't think something like source control should be this way (especially when other VCS's don't require this amount of thought).
Just my two cents.