This is a phenomenal outlook, actually. Joining and working with other projects is then like attending an interfaith group comprised entirely of heretics arguing about the right way to disagree.
not if 'never rebase, it is a trick of the devil' is part of the Dogma and adhered to.
I'm being a little silly; but a team I worked on moved from P4 -> Git. It was an older develoepr base, so they wrote 1:1 translation wrappers for most P4 commands to git, and forced all developers to use them. Banning Rebase (in private branches, not even main) was one of the requirements to not break the wrappers.
My general consensus on the practice is that it prevents the developers from learning Git. Short-term gain for long-term ignorance. I'm much more a fan of "Learn the tool upfront and reap the benefits", don't handicap the organization from the start.
Just this morning, I spent over an hour trying to fix things after I made a git mistake. I ended up having to check out a fresh copy and manually reapply my changes.
This sort of thing is why I both fear and hate git.
I'll have to check this game out. My flawed abstractions clearly cause me issues. Maybe it could help.
Also, it’s made in Godot, and whilst an older versiob of the engine, I’ve found it a valuable codebase for a couple of things. I particularly like how they deal with level creation, their file format for custom levels is very KISS.
This was presented at a conference (maybe FOSDEM?) some years ago. I as impressed, this showed what I had tried to train at work for years with mixed success.
Unfortunately there was no .deb or .rpm available at least at the time, that would be acceptable to distribute in Linux shop. So I built one myself. It was not perfectly easy (at least not for a greybeard not used to such game engine stuff), but in the end I got it building and running myself, still with some quirks not making it suitable for distribution.
I never found the time to polish it and whenever I looked at the repo again there was no activity. Now I see 2 months ago there were at least some commits.
Potentially useful project, but stalled before it got popular? I would wish it a second chance.
Edit: Downloading and installing random binaries is not something I can promote at my work. Of course a .deb or .rpm is nothing but a binary, but at least in theory (hello xz) you can audit what is built there and rebuild it yourself.
As long as they look like honest people I let everybody enter my home / borrow my car / access my internet banking / ... versus a default negative attitude?
After typing "git init" in the terminal in the level called "The command line", I then wanted to try my luck so I typed "vim". Now the terminal is stuck. How do I exit vim?
Love this, and may be helpful for incoming interns who are fuzzy on Git. Up until now my strategy has been to let them figure it out and point them to https://ohshitgit.com/ if they screw up.
Imagine if apps just… worked like this, somehow. Start off with a realtime visualization and point and click commands, and as you learn them you can evolve into a straight CLI…
I prefer reading instead of hearing some TTS or Voice AI reading things.
For proper audio experience, a VA makes things probably better, though that has some cost to it as well.
Otherwise just stick to text.
If you're going to pitch something as a game, it needs voice. Integration is simple. What's the problem? Are git incantations too powerful to be spoken aloud?
> If you're going to pitch something as a game, it needs voice
No?.. Idk what games you play, but there are an endless mountain of games with no voiceovers. It makes a lot more sense for games that have a lot of text (like this one), because reading is far faster than listening to speech. In general, I vastly prefer text to voice.
