Alex Gaynor recently announced he is formally stepping down as one of the maintainers of the Rust for Linux kernel code with the removal patch now queued for merging in Linux 6.19.
Alex Gaynor was one of the original developers to experiment with Rust code for Linux kernel modules. He’s drifted away from Rust Linux kernel development for a while due to lack of time and is now formally stepping down as a listed co-maintainer of the Rust code. After Wedson Almeida Filho stepped down last year as a Rust co-maintainer, this now leaves Rust For Linux project leader Miguel Ojeda as the sole official maintainer of the code while there are several Rust code reviewers.
In this thread: people who believe the myth of the safe C programmer. The one who has memorized the spec and is able to hold endless context in their brain while writing code. They themselves are C compilers.
You’re kidding yourself if you think most people in this thread are actually programmers. Most people here wouldn’t know the difference between C and Rust code if they saw it, let alone be able to write anything in either language.
the myth of the safe C programmer
I learnt C around about 1997 and I’ve used it off and on professionally since about 2006. I am not a myth, and there are many others like me.
What do you want me to write?
I want you to write kernel code for a few years. But we go to Lemmy with the machismo we have, not the machismo we wish we had. Write a JSON recognizer; it should have the following signature and correctly recognize ECMA 404, returning 0 on success and 1 on failure.
int recognizeJSON(const char*);I estimate that this should take you about 120 lines of code. My prior estimated defect rate for C programs is about one per 60 lines. So, to get under par, your code should have fewer than two bugs.
@eleijeep@piefed.social You had a couple months. At this point, I think that you’ve failed the challenge. I know that there’s a lot going on in the world, but frankly I doubt your commitment to dick-measuring contests on Lemmy if you’re not even able to write a bug-free JSON recognizer in C in eight weeks. I understand why you wanted to remain pseudonymous!
Let us all learn a lesson from eleijeep: writing correct C is very hard and probably can’t be done on-demand. Correct C isn’t a party trick.
I saw your reply but already at that point I knew that if I bothered to put in the effort, the only person who would have seen any code I wrote would have been you, since my comment was at -4 so nobody coming to this thread is going to read it or the reply chain, making it a wasted effort. Just like your lame “gotcha” comment here which nobody else will read, and by the way, proves nothing.