Firefox indeed.

You keep ignoring my questions. You think these answers and your post is valuable?? It contributes to spam and has no value.

So you don’t even have a single example. Well I consider your post as useless and spam. Please stop posting useless and spam like this. Edit: Also you still don’t answer a single question. Who is the judge? Who do I ask if my posts are okay to post? You?

Don’t make this a personal attack. Do you have any article you consider to be shitty? As an example, so we are on the same page. Do you ever wrote them a message or did an issue, so they are aware of the issue and can correct the mistake? Do you think they read this post of you and stop posting, because you do not agree with what they consider to be useful?

Sorry but, you are not the person who decides who can post and who cannot. I have seen shitty articles that others find useful, and I saw good articles that others find shitty. Do you get what I mean?

That does not answer my question. Who is judging what is bad and shitty guides, and who has the necessary experience? I disagree with you. Let people write articles that YOU think are shitty. Beginners or professional grade knowledge, I am for the open web where noobs share their knowledge as well. Assuming they are written by a human, not talking about Ai.

Do you have any article as an example what you consider shitty and you do not allow to be posted on the free web?

The question is, who decides what shitty guide is. You? Let people write what they want, you don’t have to use or read it. Also why not tell those you write shitty guides and tell them what is shitty, so they can improve. Instead trash talk on an unrelated forum??

deleted by creator

deleted by creator

BTW no word about the Next Gen Trait solver: https://rustc-dev-guide.rust-lang.org/solve/trait-solving.html

yay

Forking does not solve the problem, it escapes it. The problem in the main Rust Kernel will stay, not working together, arguing, while the fork might work for those who work on the fork. This is not a driver or feature where they can fork, work on it separately. It completely misses the point.

Forking does not solve the problem, it only escapes it. Its waste of time and effort in this case. The solution is that the devs work together. Otherwise it makes no sense to have Rust if no one works together. Discussion is the best way to handle this and to come to a solution. Its such an important topic that you have to discuss it, this is healthy, this is how it should be done. This is how its done.

There is no point in forking. The problem is not adding Rust to the Kernel, the problem is the C developers to get to work on it together. Forking does not solve this issue. Its not about proving being more efficient or not.

Why do you think its a problem that this is discussed a lot? Its a huge deal, so its only good its discussed and not accepted by everyone. I think this is healthy. We only read about the drama and a few quotes, but if you look closer then their argumentation makes a bit more sense. It is not just drama for the sake of drama. Some maybe toxic, that is another thing, because they would be toxic with other topics too.

Here is in a videoformat from ThePrimeagen (programmer at Netflix, or he was, not sure about current state) going through a recent discussion in the Linux Kernel mailing list about this topic. It’s about a hour long and adds some thoughts on its own too, which was valuable to me. - https://www.youtube.com/watch?v=8QcQ_128OIw

For code bases where this is a thing, you could use greps context lines: grep ---before-context 1 "^main"