On 31/10/2021 05:14, skybuck2000 wrote: > Anyway I hope to have convinced you somewhat that GIT is not ideal for > me, it's risky if something bad happens to it's database, it's > cumbersome to use, it's slow for that reason, lot's of overhead.
What you know is almost always better that some random unknown alternative that contains 'worries'. There is no perfect 'versioning' system that is good for everyone (cf. "Mona Lisa v2.5.1" ;-). I bet Git feels like one of those taxi rides through an unfamiliar city.. Git itself is fast. Changing mental models, and getting new 'wins' from that change can be, like you said, slow. > So far I have used GIT mostly with git commands, I know there is a GUI > but then I feel more disconnected, for now it makes more sense to work > like I was working in ms-dos to get more a feel for it. I would recommend trying at least the git-gui and gitk at least for their alternate view points when exploring Git. > > Problem with GIT gui approach is that git gui might change over time > as many guis do and that idea seems horrible to me, unless there are > some big benefits, I also do not want to be dependent on some > non-windows gui for software development. Because the basic data model of Git hasn't changed and is rock solid all the gui's essentially show the same stuff at different levels of prettiness and soft rounded graphics. Git-gui and gitk are TCL apps which are multi-OS. > 1. Big Open Soure Linux Operating System, here making simple copies would fill up harddisks very quickly, so I can understand only storing "differences". This is one of the BIG LIES we tell. Git stores snapshots. It will _show_ diffs between commits, but it's still between snapshots. It is only later at the database level that compression is applied. > I couldn't care less about storage space The Git community is poor at highlighting the *backup capability* of remotes, and when to 'push'. They are more worried about storage access times .. > 4. Difference engine, detecting differences You do know you get automatic de-duplication because filename metadata is stored independently of content (blobs), so copied file contents take up zero room! > 5b remote branches Mental mind trap: these are held locally when fetched. You can reference them _instantly_ and start a new work-branch directly from them, without having to create a 'local' version first > 1. Continue working with my own versioning system for very fast code development when developing solo. It's an option. However if your development becomes a team, you are likely to run into scaling issues (see Mr Torvalds's issues ;-) > GIT is more focused on sharing quality/working code and integrating code > and less on experimental/broken/flawed/buggy code. OOOH So missing the point... Git gives control to the user so they can do the latter in the privacy of their own dev environment. It then provides the tools so that they don't have to be embarrassed when publishing their polished code ! You should see some of my hacks on Matlab (interpreted, 3 fails a minute). Having lots of versions allows me to go back to interesting outputs that would otherwise have been lost in most other versioning systems (remember its 100% snapshots!) The hard part of Git, and all those other fads and tools, is to reason about the hidden issues that forced or constrained or enabled the methods being proposed. Instant perfect replication and fast incremental compiling has made the machining of a 3d model of the Titanic so much faster than that of the original, and it's sister ship. Versioning methods were developed for the Engineering Drawing Offices c.1900. Things have changed (though mk1 human, dunno?). I'll stop there. Some much that could be discussed, but mileages vary. -- Philip -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/fcc1ff4c-546d-aedd-6cf6-d2ef81f3cd6a%40iee.email.
