Oooh! I've been waiting for someone to try to replace LaTeX.

I used Zotero all through uni, but I've recently discovered JabRef. Zotero probably has more features and polish, but JabRef has one killer feature: Your plaintext BibLaTeX file is your reference database. So you can version control and collaborate on your reference file with git. No export required.

• OpenTyrian (likely available in your package manager)

It's not so much that I believe it 'by default'. Rather, when I've examined the historical case for the resurrection, the arguments that it really happened seem stronger than the arguments that it was a hoax, or a mass hallucination, or that he fainted etc.

My favourite game was always hacking around in Wine to make games work. Once I got them working I lost interest and moved on to the next game... Now I don't have time to play games. :(

You can also type ZZ (uppercase, so hold Shift) to write and quit. But for all of the above you have to be in normal mode, so if it doesn't work, try pressing Esc first.

Depends what you're trying to learn, and how much of a beginner you are. If you want to learn the shell, try the Software Carpentry tutorials:

• The Unix Shell - Software Carpentry
• Version Control with Git

If you know the basics, you might try honing your skills with CLI Mystery (murder mystery puzzle).

You'll probably want to learn how to use the following:

• SSH
• Command-line text editor. Choose one of the following:
  • Nano <- Smallest learning curve
  • Vim (or Neovim) <- My favourite (See Mastering the Vim Language)
  • Emacs <- Some people like it

The final tip is: It's usually better in the long run to spend 2 hours reading the documentation than 2 minutes searching the web. Reading the documentation helps you to understand the big picture, and gives you a much better foundation. Of course, if you're reading the documentation and don't understand something, searching the web is an OK way to figure it out.

Tax-deductible donations get you part way there.

It worked, but it was slow and dropped packets sometimes. I think the next team switched to Java. I met with them and walked them through the code and suggested they try a different approach. Hopefully they did!

I think they said in the release article that they were going to roll 115 out slowly because it's such a big change.

I'd suggest maybe stick with Godot 3 until 4.1 comes out. I just started playing with 4, and hit a bug where Godot will hard crash whenever you try to view the Terrains tab if you've created terrain sets, used them in your scene, then deleted the terrain sets.

Also, Godot 4 doesn't have as good support for older systems due to the new Vulkan backend. I worked around this by switching to the mobile renderer which works better on my old hardware.

Can I suggest duckdb? You can start out writing SQL directly on top of CSV and Parquet files. But then if you want/need to do something more complicated, you can import duckdb into Python, keep running the SQL you already wrote, convert it to a Pandas or Polars dataframe, transform it, then query the result in SQL.