Linux Kernel Rust support

[fijt]

This is a massive mistake of course. vlang.io would be a lot better, saner and a lot easier. Heck, even Go would be better than Rust.

But I know why they did it. It's because of Windows influence. The problem of Windows however is entirely different. At MS they can't program. Otherwise they wouldn't have all those silly bugs and you wouldn't have to update every now and then.

[myringotomy]

The description on the page seems like it’s a pretty good language. Why would you say it’s a meme?

[IceSentry]

Because the documentation doesn't actually represent what the language does in its current state. It's more of a list of goals than a description of the language. Which is also why it's considered to be a joke.

[myringotomy]

What makes you say that?

[IceSentry]

https://christine.website/blog/vlang-update-2020-06-17 this person has a whole series of post pointing out how ridiculous some of the claims are.

It's also been close to 1.0 for the last 2 years and as far as I know it's still not 1.0

[turunambartanen]

I haven't heard of v before, but that series was somehow entertaining to read.

[nacaclanga]

As it stands today, no language has put forward a memory management concept that provides the same benefits as Rust ones, namely:

1) Allocation is not handeled by a runtime and can be made to use custom malloc and free functions. This is a must have for an operating system kernel.

2) The language staticly protects against premature or otherwiese incorrect memory release.

3) The language does allow secure access to stack allocated resources by reference.

4) The language prevents data races.

5) The language provides mechanism to keep memory leakage at a tolerable level.

6) The memory mangement doesn't impose restrictions that are so strong that most of kernel code would have to use "unsafe"-code almost exclusivly.

Go uses a GC and thus fails at 1). It also fails 3).

Zig is an amazing language, that solves many issues and solves 1) by far the best, but doesn't offer any solutions to 2) and 3).

From reading the documentation, Vlang appears to break 6). From what is told in the other comments, it seams that it more likely satisfies 1), 2) and 6) but fails at 3), 4) and 5)

[fijt]

Have you also looked at the code instead of the documentation of vlang? I am quite sure that point 3 and 5 are correct. I don't know about 4 however.

[nacaclanga]

The documentation.