Dave.

Which is worse?

• Entire driver written in a non memory safe language?
• The interface to the rest of the kernel is marked as unsafe and then the other X percent is safe from memory corruption?

Surely if X > 0 then this is still a net improvement?

If you read the phrasing carefully it’s quite clear that it will be doing things to the codebase, just “with oversight”.

How much oversight? Not sure, just some assurances that there will be oversight.

Vibe coding is essentially just a different phrase for that.

So, after sifting through all the other breathless articles from their website it seems that they’re going to :

• Use a LLM to attempt to sort out their documentation.
• Have a chatbot trained on the docs so you can ask it questions and possibly get coherent answers.
• Some sort of vague thing where the LLM provides guidance and suggestions on improvements to the codebase.

Lots of reassurance that they’re not going to let it do vibe coding but to be honest, they doth protest a little too much methinks.