I assume by DSL they mean some custom templating language built on top, for things like iterating and if-conditions. If it's plain JSON/YAML you can produce that using any language you wish.
For the most part I agree with you: there is less functionality and hence less to police. There are also fewer people in chats/channels, as for the most part they are private or undiscoverable.
There are definitely still breaches of etiquette though, e.g. people frequently tagging a whole channel when they have a support question, even though it contains hundreds of people.
Again, this just isn't true. Where are you getting your information from?
Feeding the world is technically easy, there is more than enough space for growing crops. The only reason that it's not done is the desire to eat meat and the lack of any real will to do it.
What would make it interesting? Most of the animal mass on earth is livestock for human consumption. More animals are reared to replace the ones that are slaughtered.
It might be interesting for wild fish, but I'm not sure if there are accurate numbers for the wild populations remaining.
Is it really beneficial to use a deck created by someone else? I thought part of the learning process is really engaging with the cards - by writing them, thinking about them, and making mental associations with things you already know.
I'm a big fan of rebasing to keep the commit history clean and as a form of self-discipline when coding to make sure I'm grouping the changes atomically.
I will try to give Jujutsu a go based on your recommendation!
C# actually has fairly good null-checking now. Older projects would have to migrate some code to take advantage of it, but new projects are pretty much using it by default.
I'm not sure what the situation is with Unity though - aren't they usually a few versions behind the latest?
I use it in my project to document the schema. We keep the markdown file in source control so that we update it whenever we make database changes. We also have an extension that allows viewing it as the diagram in vscode in our .vscode\extensions.json file.
There are some disadvantages however:
1. The foreign key relationships aren't completely clear
2. The diagram became difficult to navigate in vscode as our schema grew in size
Using an in-memory database does not increase my confidence that in my software either. I also started using dockerised dependencies in tests a couple of years ago.
Can you please explain what you did with a RAM disk to speed them up?
As I point out in another comment, this happened to me previously and they were loath to compromise. I'm therefore very reluctant to depend on an Aufhebungsvertrag.