5 ms·

5 commands that when you forget them or when they go wrong you have to manually fix. And where when you automate them you realize on your laptop that something

5 commands that when you forget them or when they go wrong you have to manually fix. And where when you automate them you realize on your laptop that something went wrong and you have to go back and fix it, possibly losing hours depending on where your other computers are. Who would want that, possibly over many repos? Git isn't even working well with large files to be synced. Think about git submodules. So much can and does go wrong because Git is not designed to sync that way. Not worth the hassle for most people.

scarface_74 3y ago
You sound like the old guys (I’m 50) who are saying who needs all this git stuff instead of just putting the code on a network share. > So much can and does go wrong because Git is not designed to sync that way. Not worth the hassle for most people. Git isn’t worth the hassle for most developers??? And you really don’t see the issue with non atomic syncing for code repositories using DropBox?
- pdntspa 3y ago
  I get that you really really love git, but I am not you, nor is anyone else. We all have our own preferences. I don't like typing in tons of commands do so something simple when other tools exist. I like neat commits with a tidy explanation as to why they are there (preferably including the ticket/issue number), and I like them to persist through the life of the software. > And you really don’t see the issue with non atomic syncing for code repositories using DropBox? The only problem that ever came up in five years of this was that I could occasionally get a conflict if I switched too quickly. But that was easy to resolve, and Dropbox would always sync within 5 to 10 seconds. And no we did not have a network share to work from. The wifi in the building was horrendous so it was preferable to have everything local.
  - scarface_74 3y ago
    > We all have our own preferences. Your preference literally goes against every agreed upon best practice by every organization I’ve worked for for over two decades. > The only problem that ever came up in five years of this was that I could occasionally get a conflict if I switched too quickly This is literally the problem that git tools solve with merging changing.
    - pdntspa 3y ago
      What environment are you working in where single-user file sync has the same requirements as a thousand-tenant database? Why do I need atomicity here?
      - scarface_74 3y ago
        Really? If I change 10 files as one logical change. I want to ensure that when I go to the other computer I have all 10 of those changes. DropBox by definition is eventually consistent. You don’t know if all of your changes are synced. That’s not even to mention when I use an automatic refactoring tool that can literally change dozens of files.
        pdntspa 3y ago
        You wait for the little icon in the system tray to stop spinning, and you can look in the window at the sync log if you don't trust it. It would take about 10 seconds. My whole original point to this thread was that the dropbox client can handle tens of thousands of little file changes without breaking a sweat. You could replace text in the entire codebase with one command and it will swallow it all no problem. Yes it is eventually consistent, and yes dont touch the code on any other devices until it's done, but even if you are somehow refactoring your entire codebase every day, the change will be made manifest, and quickly. I don't know if you've ever peeked under the hood of a git repo, but it creates literally thousands upon thousands of tiny little files. Far more than whatever the repo is actually storing. For my uses, where I would run over to a machine and maybe tweak a line or two of code on the laptop and re-run it then return to my desk, there were literally never any problems if I didn't jump the gun (and it was easy to resolve if I did).
        scarface_74 3y ago
        > You wait for the little icon in the system tray to stop spinning, and you can look in the window at the sync log if you don't trust it. It would take about 10 seconds. And this compares to knowing that when I do a git add/git commit/git push, I know my code is on the server. When I do a git pull, I know my code is on the second computer. > Yes it is eventually consistent, and yes dont touch the code on any other devices until it's done Again, this is literally a problem that git was purpose built to solve and used by millions of developers every day across the industry from the smallest shop up to largest companies.
- deleted 3y ago
  [deleted]

scarface_74 3y ago

You sound like the old guys (I’m 50) who are saying who needs all this git stuff instead of just putting the code on a network share. > So much can and does go wrong because Git is not designed to sync that way. Not worth the hassle for most people. Git isn’t worth the hassle for most developers??? And you really don’t see the issue with non atomic syncing for code repositories using DropBox?

pdntspa 3y ago
I get that you really really love git, but I am not you, nor is anyone else. We all have our own preferences. I don't like typing in tons of commands do so something simple when other tools exist. I like neat commits with a tidy explanation as to why they are there (preferably including the ticket/issue number), and I like them to persist through the life of the software. > And you really don’t see the issue with non atomic syncing for code repositories using DropBox? The only problem that ever came up in five years of this was that I could occasionally get a conflict if I switched too quickly. But that was easy to resolve, and Dropbox would always sync within 5 to 10 seconds. And no we did not have a network share to work from. The wifi in the building was horrendous so it was preferable to have everything local.
- scarface_74 3y ago
  > We all have our own preferences. Your preference literally goes against every agreed upon best practice by every organization I’ve worked for for over two decades. > The only problem that ever came up in five years of this was that I could occasionally get a conflict if I switched too quickly This is literally the problem that git tools solve with merging changing.
  - pdntspa 3y ago
    What environment are you working in where single-user file sync has the same requirements as a thousand-tenant database? Why do I need atomicity here?
    - scarface_74 3y ago
      Really? If I change 10 files as one logical change. I want to ensure that when I go to the other computer I have all 10 of those changes. DropBox by definition is eventually consistent. You don’t know if all of your changes are synced. That’s not even to mention when I use an automatic refactoring tool that can literally change dozens of files.
      - pdntspa 3y ago
        You wait for the little icon in the system tray to stop spinning, and you can look in the window at the sync log if you don't trust it. It would take about 10 seconds. My whole original point to this thread was that the dropbox client can handle tens of thousands of little file changes without breaking a sweat. You could replace text in the entire codebase with one command and it will swallow it all no problem. Yes it is eventually consistent, and yes dont touch the code on any other devices until it's done, but even if you are somehow refactoring your entire codebase every day, the change will be made manifest, and quickly. I don't know if you've ever peeked under the hood of a git repo, but it creates literally thousands upon thousands of tiny little files. Far more than whatever the repo is actually storing. For my uses, where I would run over to a machine and maybe tweak a line or two of code on the laptop and re-run it then return to my desk, there were literally never any problems if I didn't jump the gun (and it was easy to resolve if I did).
        scarface_74 3y ago
        > You wait for the little icon in the system tray to stop spinning, and you can look in the window at the sync log if you don't trust it. It would take about 10 seconds. And this compares to knowing that when I do a git add/git commit/git push, I know my code is on the server. When I do a git pull, I know my code is on the second computer. > Yes it is eventually consistent, and yes dont touch the code on any other devices until it's done Again, this is literally a problem that git was purpose built to solve and used by millions of developers every day across the industry from the smallest shop up to largest companies.
deleted 3y ago
[deleted]