I do prefer C, due to its simplicity alone. I think that rewriting programs in Rust, or C++, just because "they are better" would be an unwise descision.
Don't get me wrong, I do believe they are great languages, however, sometimes you must count your merits, and choose the best tool for the job.
I think I left Google just in the nick of time.
My Google usage has stopped entirely (exept through alt frontends), and I also deleted my Google account. They will continue to promote their needless services, and even shove it down your throats. I wish good luck for us all, since Google will most likely continue to do this, and attempt to enact further restrictions upon the internet.
Oh, so that is where all of my modules are? That makes total sense, thanks!
If you are willing to abandon Linux, I would suggest FreeBSD for general purpose servers.
It is a full operating system, which starts you off with a CLI, that is easy to configure. There is a full handbook that describes the full process, and it is on their website. FreeBSD is an operating system, rather than a distribution of cobbled together packages. Due to this, operating system binaries, and package binaries, are separated. This makes configuration on the OS level consistent.
A lot of Linux programs come from the BSD family. FreeBSD also has its own hypervisor, named Bhyve. FreeBSD has its own version of Docker as well, they are called jails. It might take some time to learn, but I promise it will be worth the time.
Nuance is very important. When one speaks, sometimes they ignore the nuance of the other side. Therefore, they never get to truly know the other side, and true harmony can never be achieved. Sometimes, those who claim or imply to be nuanced, are the very ones who are the least nuanced. If one side is pushed into a corner, they will fight back, hard.
I am glad that this issue is being addressed. I think it is also worth mentioning, that it is more worth the time to document your code now, than it is to waste time later, trying to figure out what the code does. Many project leads are unwise when it comes to this, and therefore fail to allocate the proper time. This will inevitably lead to unmaintained/unreadable code later down the road. This is bad for many reasons: You cannot reuse the code, you cannot maintain old code, programmers will become angry, ETC...
The environment is deceptive. It is only when you turn on the computer, when the hostility will creep up like a bird on steroids, waiting to peck at you for seemingly a century ahead.
Who doesn't like compounding two words with different meaning by definition, but for some inexpiable reason have the same meaning in the programming world, by shortening them?
Now the poor, average programmer has to deal with strange words. One such example is "permission," which is normally used within a casual context, rather then within a more serious context, like a program handling secure data. The poor programmer can now no longer take his job seriously, and is now forever in an existential crisis, due to the lack of formality. ;)
I would use VIM, personally. It may take some getting used to, but once you get it, it can be very useful. (VIM does have syntax highlighting, by the way)