4 ms·

I love the versioning approach here - use git but still create fileV1.py, fileV2.py...

FpUser 4y ago
I did not look at their particular code but I had files named like this in my projects: api_v1, api_v2. Reason being that the software V2 still supported v1 api so both were present and needed.
- actinium226 4y ago
  A reasonable approach but from the README: "To run the code you will need to install Python and the PyGame library, and then run the latest .py file because I can't be bothered to actually use version control."
  - ChildOfEru 4y ago
    I'm just reminded of the last line of the README.md "I am in Electrical Engineering and I like writing shitty code to piss off my Computer Science friends." -- https://github.com/ehulinsky/AnalogChess/blob/main/README.md#code https://github.com/ehulinsky/AnalogChess/blob/main/README.md...
- The_Colonel 4y ago
  It's a relatively common approach in e.g. web services, but not in standalone games.
  - FpUser 4y ago
    I did not really look at the project, just at the comments so yes sure.
Kiro 4y ago
I do the same. I think it's nice to have the old version readily available as reference instead of hidden in git.
- DangerousPie 4y ago
  You need a better ide!
  - 8n4vidtmkvmk 4y ago
    phpstorm has good history. vs code can die in a fire.
    - Kiro 4y ago
      What has VS Code done to you to deserve that?
      - 8n4vidtmkvmk 4y ago
        :-) I don't hate it that much, in fact, I use it a bit, but I still think it's inferior, but the fact that it's so popular means that a lot of extension developers are now targeting it and only it which forces me to use inferior tooling for some things. I already have this problem with Git. I think Mercurial is better but all the good tooling is built around Git.
  - userbinator 4y ago
    It's so cliche to recommend a more complex tool --- with its own associated learning curve and more complex failure modes --- when there's already a simple method that works perfectly well, but isn't "best practice" or whatever the dogmatists call it. Can you run two or more versions and compare their behaviour simultaneously, even debug them side-by-side? I'm sure there's some sort of plugin and IDE ecosystem that you can spend tons of time learning how to configure just to be able to do that, but if all I need to do is to copy the files and rename them, why not? Do some people really love excess complexity so much?
    - JelteF 4y ago
      I agree with the general gist if your post, but still wanted to call out the "git worktree" because that would solve the problem you're describing. It's pretty much a better version of cloning the repo twice.

I did not look at their particular code but I had files named like this in my projects: api_v1, api_v2. Reason being that the software V2 still supported v1 api so both were present and needed.

actinium226 4y ago
A reasonable approach but from the README: "To run the code you will need to install Python and the PyGame library, and then run the latest .py file because I can't be bothered to actually use version control."
- ChildOfEru 4y ago
  I'm just reminded of the last line of the README.md "I am in Electrical Engineering and I like writing shitty code to piss off my Computer Science friends." -- https://github.com/ehulinsky/AnalogChess/blob/main/README.md#code https://github.com/ehulinsky/AnalogChess/blob/main/README.md...
The_Colonel 4y ago
It's a relatively common approach in e.g. web services, but not in standalone games.
- FpUser 4y ago
  I did not really look at the project, just at the comments so yes sure.

Kiro 4y ago

I do the same. I think it's nice to have the old version readily available as reference instead of hidden in git.

DangerousPie 4y ago
You need a better ide!
- 8n4vidtmkvmk 4y ago
  phpstorm has good history. vs code can die in a fire.
  - Kiro 4y ago
    What has VS Code done to you to deserve that?
    - 8n4vidtmkvmk 4y ago
      :-) I don't hate it that much, in fact, I use it a bit, but I still think it's inferior, but the fact that it's so popular means that a lot of extension developers are now targeting it and only it which forces me to use inferior tooling for some things. I already have this problem with Git. I think Mercurial is better but all the good tooling is built around Git.
- userbinator 4y ago
  It's so cliche to recommend a more complex tool --- with its own associated learning curve and more complex failure modes --- when there's already a simple method that works perfectly well, but isn't "best practice" or whatever the dogmatists call it. Can you run two or more versions and compare their behaviour simultaneously, even debug them side-by-side? I'm sure there's some sort of plugin and IDE ecosystem that you can spend tons of time learning how to configure just to be able to do that, but if all I need to do is to copy the files and rename them, why not? Do some people really love excess complexity so much?
  - JelteF 4y ago
    I agree with the general gist if your post, but still wanted to call out the "git worktree" because that would solve the problem you're describing. It's pretty much a better version of cloning the repo twice.