1. 7

    I’ve always wanted to make games so the project closest to my heart is Dose Response. It’s a small open-world roguelike where you play an addict. Written in Rust, running on Linux, Windows, macOS as well as WebAssembly. Free/Libre/Open Source, pay what you want.

    Unfortunately, I did not have a lot of time and energy to update it after the 1.0 release yet.

    1. 4

      A great game! Thank you for sharing.

      1. 2

        Thank you for playing! I’m glad you like it!

    1. 4

      This is not a very good idea, IMO. Many utilities/tools tend to create folders and files in the home directory, like Ghidra for example, creates a ~/ghidra_scripts. It’s bound to get messy fast. It’s probably a better idea to maintain a separate “dotfiles” folder where you symlink config files/folders that you want to persist across installs, and version that using git instead.

      1. 3

        What do you mean?

        The first line in the ~/.gitignore file causes it to ignore everything. Anything you want to track you need to add explicitly and new files won’t even show up in git status.

        1. 2

          Oh right, yes. My bad. I’d failed to notice the first like in your .gitignore.

          1. 1

            Not mine, but yeah I wondered :-). I’m using the more traditional dotfiles approach as well.

            I had actually tried to put my home dir under git ages ago, running exactly into the issues you’ve mentioned. Ignoring everything by default and only adding files explicitly does sound like an interesting alternative to consider at least.

        2. 1

          This argument makes sense to me when it comes to synchronizing two or more different computers.

          What kind of version control systems is preferable when it comes to the synchronization/backup of the ~/Documents folder alone? I guess syncing Windows/Linux mashines should not be a problem here, no?

          I using rsync for backups these days, and never thought about looking into version control systems. Any experiences here?

          1. 2

            It depends. If your files for backup are generally text based, i.e. config files, then using a VCS is a good idea. Something like git offers great ease in managing them. But if your files are binaries, like pictures for example, then rsync is alright, I guess.

        1. 6

          I’m one of those people who learned English with British textbooks and for me that’s a mega useful feature, as I constantly opt for the British spellings, even though I know in Computer Science we’re not supposed to use them.

          I am spelling British and am rather unapologetic about it. Languages have dialects and people should spell in any colour they want to.

          (I see the strive for consistency, but as long as the particular codebase has not standardised on a spelling, I won’t walk around and figure out which one it uses)

          1. 2

            I’m Canadian, even for words that we consistently spell British (which is most of them I think), I spell American in source code. Most source code seems to be American and I want to minimize the number of identifier mispredictions for anyone editing it - including myself.

            1. 1

              It’s the same for non-English speakers. Few people write code in anything other than American English.

              1. 1

                But don’t they generally then also spell American English outside the code, then?

                I don’t (English is my second language, my spelling is British, but in code I do American for the same reasons gpm outlined). However, I come to contact with a lot of non-native speakers and I feel that pretty much all of them lean American in both their spelling and pronunciation in all contexts.

                1. 1

                  My point was primarily about English, not specifically only the American dialect.

            2. 2

              I’m an American and I use American spellings in my own code and writing about code. That said I see no reason why British people or nonnative speakers who learned British rather than American spellings should feel the need to switch. I think nearly every educated AmEng speaker is familiar enough with British useages (and vice versa) that there’s no serious barrier of comprehensibility.

              As a matter of fact, in my readings of the recently-deceased Joe Armstrong’s papers and other writing about Erlang, he (a British person who worked in Sweden) did in fact use British spellings like “colour” without any kind of problem.