So I joust found this brilliant scientific paper called "Replication of Quantum Factorisation Records with an 8-bit Home Computer, an Abacus, and a Dog" which mocks quantum computer researchers for optimising factorisation of prime numbers in a way, so that it is as easy as possible to calculate them with a quantum computer. While you may not understand the technical or mathematical explanations they include a lot of jokes and its very funny to read. One of the jokes is,that they call quantum computers a "physics experiment", which is the explanation behind this joke.

Remember guys, using GIFs of Racoon's in a discussion is ok, as long as you keep them below 1mb.

I dont want to live in this reality any more.

I recently started learning rust, and I was ready for one hell of a fight. I heard all those horror Storys about the compiler complaining about every single detail and that developing rust means having a constant fight with the compiler about seemingly irrelevant things. However, so far I have to tell, that while its somewhat true, that the compiler is somewhat picky, it is incredibly helpful. Never before have I seen such good and helpful compiler messages. It not only says what you did wrong, but also gives direct help on what to do to fix your code. I also really like, that it gives you direct references to the rust book in the compiler messages.

Prior to starting my journey with rust I did quite a lot of python, some C and some bash and their interpreter/compiler messages are nothing when comparing them with rust. Especially the bash error messages are awful if you do not know what they mean and how to fix them.

I personally havent really used emacs for organizing, but I really like it for bash coding and writing software documenation in orgmode. I am even starting to get a little bit comfortable at writing my .emacs file but at some point I will have to do a lot of reorganizing and updating and I kind of dont want to do it (I still use .emacs and not emacs.d/init.el and all keybindings still use the legacy global-set-key command).

Apart from the work I am putting into it it is really great, because when I actually get to do stuff I can do so with great efficency. I am even starting to miss my emacs keybinds when not using emacs (especially ctrl-k for killing from your cursor position to the end of the line ctrl-a for jumping to the beginning of a line and ctrl-e for jumping to the end of a line). At this point when I am writing stuff in emacs (as example working on a bash script) I at maximum use my mouse for scrolling.

Fuck, I really did turn into the meme (and I am not even using it for longer than 4-5 months at maximum)___

Someone once told me somewhere, that if I am trying to learn rust, I should learn C first, so that I know how to shoot myself in the foot, learning to avoid doing so, so that the borrow checker of rust doesnt seam to unforgiving (since you somewhat know, what happens if you dont follow best practices). So thats what I did (somewhat) for the past 6 months. I wrote some stuff in C, but mainly I had quite of a deep dive into operating systems (mainly linux), working mechanics of memory and the CPU and a lot more (I will try to make a list of the stuff I learned and the ressources used below). My question to you is, if there are any additional concepts/things I should learn beforehand, to start learning rust.

The (somehwat complete) list of things learned for the past 6 months:

• Stack Behaviour (Why its so fast, what its used for,....)
• The heap (why its useful, but dangerous)
• Theoretical Concepts of threading (Concurrency vs. paralellism)
• Theory of race conditions (how and why they occur, and some tricks to avoid them)
• Concepts of Memory allocation on an OS level (Address Spaces)
• System calls and the separation between kernel and user space
• Signals
• Basics of Inter-Process-Communication
• CPU-Scheduling (CPU-/IO-Bursts, context switches, different scheduling algorithms up to ROund RObin (based on complexity))
• How loops, conditions and function calls get implemented in Assembly / how the CPU performs these
• Bitwise Operations

I probably forgot a significant part of the stuff I learned, but its quite hard turning it into a list, without writing a whole book, and trying to remeber everything.
Most of these things are mainly theory, since I havent gotten around to code that much in C. However I definitively have some experience in C. This includes on how to handle pointers, basics of handling the heap, strings (even if I absolutely hate them in C) and some system calls (I played around with sbrk for custom memory management without malloc).

The ressources I used for learning is primarily the YouTube-Channel CoreDumped (I highly recommend), LowLevel and some other ressources, but these were the most helpful ones.

So, feel free to send me down my next rabbit hole before starting rust.

So, I am soon going to finally set up my first home server. Exams are not that far away, I am motivated as shit, my first own domain is bought and I want to level up my sysadmin skills.

Currently my plans look like this:

• Host Jellyfin
• Host my own NAS
• Some form of hosted musicstreaming integration with my local music
• Automate Backups and push them on my server
• make all of the above things available where ever I want using my own self hosted domain.
• run my own dns

In the long term I also want to be able to host my own webapps, since I will soon start to develop one for someone.

Now I want to know what suggestions do you have, for stuff thats really cool and that I can selfhost.

Edit: thanks for all the replies. Definitely going to look into this.

These times may also create some really strong women.