One problem is (even Linus acknowledged it in some interview, sorry I have no source) that in future C might no longer be the popular language to learn. I mean learning basics is one thing, but getting good at C and writing in the Kernel, while trying to dodge memory issues is a huge task to ask.

Lot of people learn Rust instead for systems programming today. Meaning in future it might be very useful to get new people into Kernel programming. And as said before, those who are not interested into Rust are perfectly fine using C. The Kernel is huge! Even new code in C is allowed, so this is not something that is going away. Remember, its an addition to the base, not replacement.

The situation of COBOL has nothing to do with Rust in Linux. C is not replaced by Rust, first. Secondly, there are legitimate reasons why Rust was introduced, as a secondary language. You are conflicting two different cases that are two different problems. It’s not replacing a language.

Developers who are not willing to learn something new and not adapt are the worst. Besides that, nobody is forced to learn Rust, only those who want to work on Rust parts.

Sharing a folder in virt-manager was a something. This is for Linux on Linux only. Didn’t use a virtual manager for a while now, but I have notes how to do it. I think there are two ways, one with virtiofs and the other way with virtio-9p if the guest doesn’t support virtiofs? I honestly forgot the details, so you might need to research a bit again. I’m relatively new to Virt-Manager and Qemu+Kvm, and don’t understand every detail. It was a challenge to figure out all of this. My notes:

Host

First create a directory on your host system (the real machine outside of virtual machine). This folder will be shared:

mkdir /home/tuncay/Public/vm_share/
chmod 777 /home/tuncay/Public/vm_share/

In the Virt-Manager for your Linux guest, set following settings first.

either

virtiofs:

    Virt-Manager:
    Add Hardware > Filesystem
        - Driver: virtiofs
        - Source: /home/tuncay/Public/vm_share
        - Target: share

or

virtio-9p:

    Virt-Manager:
    Add Hardware > Filesystem
        - Driver: virtio-9p
        - Source: /home/tuncay/Public/vm_share
        - Target: /share

Then go and start the guest virtual machine. In the guest execute following commands, depending on which previous settings you have. Just create a folder in the virtual machine and mount it with virtiofs. Here this means “share” is the target (we set previously under - Target: /share) and “home/tuncay/Public” is the folder you want to use IN THE guest. The “share” name will then be connected to Virt-Manager, which in previous settings resolves to - Source: /home/tuncay/Public/vm_share on your real machine.

virtiofs:

Either mount the drive every time you start the guest, or you can just mount it in /etc/fstab automatically, like in bottom example.

    Guest:
    mkdir /home/tuncay/Public/
    sudo mount -t virtiofs share /home/tuncay/Public

    ... or Guest /etc/fstab:
    share   /home/tuncay/Public       virtiofs        defaults        0       0

or use virtio-9p, but this one does not work with fstab and the command is slightly more complicated. You can write a script and save it in the guest. Either autorun the script or just when you need it by demand.

virtio-9p:

    Guest:
    mkdir /home/tuncay/Public/
    sudo mount -t 9p -otrans=virtio,rw,version=9p2000.L /share /home/tuncay/Public

But WoW plugins have nothing to do with Vim. That’s my point. You can use Lua in WoW, while using Vimscript in Vim.

My point is, then use Lua outside of Vim. What does this have anything to do with the language used in Vim? You can use Vimscript in Vim, and still use Lua outside of Vim. So what’s the problem? It’s not like Lua gets available to you outside of Vim, just because you switch to Neovim. What do I miss here?

Vim: Clearly evil, lightning fast. Relies on vimscript for any interactivity and can barely be used outside of the editor.

I don’t know why you want use Vimscript for anything outside of the editor. But if that your issue, then there is Neovim. It uses Lua instead Vimscript, but what is the benefit of using Lua outside of Vim? That changes nothing.

The Terminator is not here to kill you, its here to protect you from Emacs (which can change its form to anything).

Then I’m doing something wrong.

I use yay almost exclusively and have a few AUR stuff. And I used a custom Kernel too (Zen). Nothing broke unfortunately. I’m on EndevourOS, so very close to bare metal Archlinux. But before that I was on Manjaro and had AUR stuff too and was using Pamac (not to be confused with pacman) instead yay. And it broke something all the time.

Almost as old as the last Debian update.

I presume you will find it amusing that I’m from Germany.

I argue that every © Kernel programmer should (not forced!) familiarize with Rust. Many (but not all) are stubborn and won’t do that. The argumentation and questions brought up in this discussion (in the article) are very interesting and to -my surprise- humane. It’s an interesting read to see how Kernel developers argue and think.

skill issues

deleted by creator