It’s a slippery slope. So far Linus has gone from using it to find bugs, to using it as a programming assistant, and now ostensibly to vibecode entire features.
Where will it end? Will Linus shut off external contributions and let the agents loose like Bun did? That would be a tragedy in my book.
The phrase vibecode has become totally meaningless. The original use was too “give in too the vibes” and let the agent go wild. There is no indication that is what Linus is doing.
The fact is LLM’s have proven to be good at finding bugs. Suitably constrained they can be diligent and helpful assistants.
The Bun experience is instructive and if that was Linus’ end goal it would be concerning but I don’t see any evidence that any of the Linux maintainers are interested in that sort of wholesale conversion. The good projects with taste will adjust to the new tools and the slop projects will eventually collapse under their own contradictory architectures.
It’s a slippery slope. So far Linus has gone from using it to find bugs, to using it as a programming assistant, and now ostensibly to vibecode entire features.
Where will it end? Will Linus shut off external contributions and let the agents loose like Bun did? That would be a tragedy in my book.
We can just fork the latest kernel version we feel comfortable with.
The phrase vibecode has become totally meaningless. The original use was too “give in too the vibes” and let the agent go wild. There is no indication that is what Linus is doing.
The fact is LLM’s have proven to be good at finding bugs. Suitably constrained they can be diligent and helpful assistants.
The Bun experience is instructive and if that was Linus’ end goal it would be concerning but I don’t see any evidence that any of the Linux maintainers are interested in that sort of wholesale conversion. The good projects with taste will adjust to the new tools and the slop projects will eventually collapse under their own contradictory architectures.