11–20 of 216 posts
* The core idea sounds interesting. Make it the first paragraph, not paragraph seven.
* Spend more words describing what makes Oak different.
* "I built a version control system in my free-time called Jam". You probably didn't name your free time. "I built a version control system, called Jam, in my free time."
Does this try to solve the biggest problems with Git: submodules and LFS?
Planning on some monorepo features soon that should solve some submodule problems but haven't approached yet. I have some new ideas here. And yes, no separate LFS system!
Awesome. How does one decide which files should be stored externally, and manage that? And where is that decision stored?
"Git is forever" Many things were forever until they suddenly died, but I think this is especially true for git. I'm not saying this as a git hater, quite to the contrary. I think git is great. I also think git is an ill-fit for the majority of modern commercial software projects and there will be a breaking point where companies realize that and move on.
Lots of self-promotion, but no concrete comparisons where this tool does a better job than git. The only thing to go on is this single sentence: "With virtual mounts, agents locally and in the cloud no longer need a full copy of a repo to get working." > For the first 100 users that subscribe to a paid plan I will send you a personalized e-ink display I don't understand anyone who feels incentivized by this. Brogramm…
What I want from a version system is to capture event in history not like changes as a files but as events that capture a process. If I split a file in two I still want to be able to see blame correctly for the author of the function, not one file as freshly created and the other with a bunch of deletes. I wish commits could be folded into larger commits so that you can still capture the individual changes but also n…
Fossil merges do this. More people need to use Fossil; it's got a ton of great ideas.
"If I split a file in two I still want to be able to see blame correctly for the author of the function, not one file as freshly created and the other with a bunch of deletes."
Now this is a good idea that I've never seen in a VCS.
"Git is forever" Many things were forever until they suddenly died, but I think this is especially true for git. I'm not saying this as a git hater, quite to the contrary. I think git is great. I also think git is an ill-fit for the majority of modern commercial software projects and there will be a breaking point where companies realize that and move on.
Lots of self-promotion, but no concrete comparisons where this tool does a better job than git. The only thing to go on is this single sentence: "With virtual mounts, agents locally and in the cloud no longer need a full copy of a repo to get working." > For the first 100 users that subscribe to a paid plan I will send you a personalized e-ink display I don't understand anyone who feels incentivized by this. Brogramm…
I found the section titled “Local feature branches. Server main. One squash.” most interesting.
Grammar nitpick: "anyways" should almost awlays be "anyway"
Earlier quoted context omitted.
Planning on some monorepo features soon that should solve some submodule problems but haven't approached yet. I have some new ideas here. And yes, no separate LFS system!
> And yes, no separate LFS system! Awesome. How does one decide which files should be stored externally, and manage that? And where is that decision stored?
A few comments: * The core idea sounds interesting. Make it the first paragraph, not paragraph seven. * Spend more words describing what makes Oak different. * "I built a version control system in my free-time called Jam". You probably didn't name your free time. "I built a version control system, called Jam, in my free time."