jesus christ, Linux has had a 100% LLM takeover.
-
jesus christ, Linux has had a 100% LLM takeover.
this project is completely cooked.
even after the AI bubble pop, it's not clear how to recover from this level of bullshit from this level of bullshitter.
https://lwn.net/SubscriberLink/1099594/be20382b54a9b4cd/
> Linus Torvalds believes that blaming LLMs for the kernel community's problems is wrong, when the problem is LLM users who do not understand how to use them or how the kernel works. A properly trained LLM is a useful tool, but it takes a lot of time to reach that point.
> Torvalds and others repeatedly said low-quality contributions from new developers should receive low priority, and that the community should stop trying to make contribution easy. Many developers said, repeatedly, that trying to mentor those developers is almost always a waste of time; they do not listen.
> There is some concern about companies maintaining private kernels with LLM help, but there does not seem to be much to be done about it.
> Kernel developers should not be required to use LLMs to work in the community, but those who do need to have enough resources available to generate acceptable results.
The requirement to add Assisted-by tags to patches created with LLMs will be removed, but maintainers still want to know about how a patch was created.so how's it going already?
> The development community is struggling to keep up with the flood of security patches, and will continue to for some time. Some of the most urgent fixes may bypass maintainers and go straight to Torvalds. Maintainers were cautioned against telling their employers about vulnerabilities before public disclosure happens.
Really, I'm not out to suck ass as much as Microsoft. That will just be a completely unintentional side effect.
@davidgerard Well. So much for the Year of the Linux Desktop.
-
jesus christ, Linux has had a 100% LLM takeover.
this project is completely cooked.
even after the AI bubble pop, it's not clear how to recover from this level of bullshit from this level of bullshitter.
https://lwn.net/SubscriberLink/1099594/be20382b54a9b4cd/
> Linus Torvalds believes that blaming LLMs for the kernel community's problems is wrong, when the problem is LLM users who do not understand how to use them or how the kernel works. A properly trained LLM is a useful tool, but it takes a lot of time to reach that point.
> Torvalds and others repeatedly said low-quality contributions from new developers should receive low priority, and that the community should stop trying to make contribution easy. Many developers said, repeatedly, that trying to mentor those developers is almost always a waste of time; they do not listen.
> There is some concern about companies maintaining private kernels with LLM help, but there does not seem to be much to be done about it.
> Kernel developers should not be required to use LLMs to work in the community, but those who do need to have enough resources available to generate acceptable results.
The requirement to add Assisted-by tags to patches created with LLMs will be removed, but maintainers still want to know about how a patch was created.so how's it going already?
> The development community is struggling to keep up with the flood of security patches, and will continue to for some time. Some of the most urgent fixes may bypass maintainers and go straight to Torvalds. Maintainers were cautioned against telling their employers about vulnerabilities before public disclosure happens.
Really, I'm not out to suck ass as much as Microsoft. That will just be a completely unintentional side effect.
@davidgerard NetBSD is feeling really nice these days.
Yes, the Nouveau is too old to recognize my graphics card, and the audio doesn't work for reasons I'm yet to investigage. It's not a setup everyone could accept. But for my needs, it's a relief to have a computer in my house that isn't subject to all this.
-
@davidgerard Well. So much for the Year of the Linux Desktop.
@kawa @davidgerard
Congratulations to Linux, the best salesman of Linux skepticism and skepticism accessories. -
jesus christ, Linux has had a 100% LLM takeover.
this project is completely cooked.
even after the AI bubble pop, it's not clear how to recover from this level of bullshit from this level of bullshitter.
https://lwn.net/SubscriberLink/1099594/be20382b54a9b4cd/
> Linus Torvalds believes that blaming LLMs for the kernel community's problems is wrong, when the problem is LLM users who do not understand how to use them or how the kernel works. A properly trained LLM is a useful tool, but it takes a lot of time to reach that point.
> Torvalds and others repeatedly said low-quality contributions from new developers should receive low priority, and that the community should stop trying to make contribution easy. Many developers said, repeatedly, that trying to mentor those developers is almost always a waste of time; they do not listen.
> There is some concern about companies maintaining private kernels with LLM help, but there does not seem to be much to be done about it.
> Kernel developers should not be required to use LLMs to work in the community, but those who do need to have enough resources available to generate acceptable results.
The requirement to add Assisted-by tags to patches created with LLMs will be removed, but maintainers still want to know about how a patch was created.so how's it going already?
> The development community is struggling to keep up with the flood of security patches, and will continue to for some time. Some of the most urgent fixes may bypass maintainers and go straight to Torvalds. Maintainers were cautioned against telling their employers about vulnerabilities before public disclosure happens.
Really, I'm not out to suck ass as much as Microsoft. That will just be a completely unintentional side effect.
@davidgerard yeah it's amazing how much my willingness to move OS has increased recently
-
jesus christ, Linux has had a 100% LLM takeover.
this project is completely cooked.
even after the AI bubble pop, it's not clear how to recover from this level of bullshit from this level of bullshitter.
https://lwn.net/SubscriberLink/1099594/be20382b54a9b4cd/
> Linus Torvalds believes that blaming LLMs for the kernel community's problems is wrong, when the problem is LLM users who do not understand how to use them or how the kernel works. A properly trained LLM is a useful tool, but it takes a lot of time to reach that point.
> Torvalds and others repeatedly said low-quality contributions from new developers should receive low priority, and that the community should stop trying to make contribution easy. Many developers said, repeatedly, that trying to mentor those developers is almost always a waste of time; they do not listen.
> There is some concern about companies maintaining private kernels with LLM help, but there does not seem to be much to be done about it.
> Kernel developers should not be required to use LLMs to work in the community, but those who do need to have enough resources available to generate acceptable results.
The requirement to add Assisted-by tags to patches created with LLMs will be removed, but maintainers still want to know about how a patch was created.so how's it going already?
> The development community is struggling to keep up with the flood of security patches, and will continue to for some time. Some of the most urgent fixes may bypass maintainers and go straight to Torvalds. Maintainers were cautioned against telling their employers about vulnerabilities before public disclosure happens.
Really, I'm not out to suck ass as much as Microsoft. That will just be a completely unintentional side effect.
@davidgerard
9front is the way forward. -
@davidgerard Well. So much for the Year of the Linux Desktop.
@kawa@mas.to @davidgerard@circumstances.run
It's not just the year of linux on the desktop — it's the year of slop on the desktop. Deskslop even. Let's delve in to see how much it's been compromi- uhh I mean beep boop improved
-
@davidgerard Well. So much for the Year of the Linux Desktop.
@kawa @davidgerard It's now the year of the Linux Deskslop.
-
@kawa @davidgerard It's now the year of the Linux Deskslop.
@Rob_T_Firefly @kawa @davidgerard i see what you did there
-
jesus christ, Linux has had a 100% LLM takeover.
this project is completely cooked.
even after the AI bubble pop, it's not clear how to recover from this level of bullshit from this level of bullshitter.
https://lwn.net/SubscriberLink/1099594/be20382b54a9b4cd/
> Linus Torvalds believes that blaming LLMs for the kernel community's problems is wrong, when the problem is LLM users who do not understand how to use them or how the kernel works. A properly trained LLM is a useful tool, but it takes a lot of time to reach that point.
> Torvalds and others repeatedly said low-quality contributions from new developers should receive low priority, and that the community should stop trying to make contribution easy. Many developers said, repeatedly, that trying to mentor those developers is almost always a waste of time; they do not listen.
> There is some concern about companies maintaining private kernels with LLM help, but there does not seem to be much to be done about it.
> Kernel developers should not be required to use LLMs to work in the community, but those who do need to have enough resources available to generate acceptable results.
The requirement to add Assisted-by tags to patches created with LLMs will be removed, but maintainers still want to know about how a patch was created.so how's it going already?
> The development community is struggling to keep up with the flood of security patches, and will continue to for some time. Some of the most urgent fixes may bypass maintainers and go straight to Torvalds. Maintainers were cautioned against telling their employers about vulnerabilities before public disclosure happens.
Really, I'm not out to suck ass as much as Microsoft. That will just be a completely unintentional side effect.
@davidgerard "the community should stop trying to make contribution easy." is an incredible statement. Yes, everyone was spoiled by the extremely friendly and welcoming kernel submission experience, jumping through 900 flaming hoops on the LKML to get screamed at.
-
@kawa @davidgerard It's now the year of the Linux Deskslop.
@Rob_T_Firefly @kawa @davidgerard sad but true
-
J jwcph@helvede.net shared this topic
-
jesus christ, Linux has had a 100% LLM takeover.
this project is completely cooked.
even after the AI bubble pop, it's not clear how to recover from this level of bullshit from this level of bullshitter.
https://lwn.net/SubscriberLink/1099594/be20382b54a9b4cd/
> Linus Torvalds believes that blaming LLMs for the kernel community's problems is wrong, when the problem is LLM users who do not understand how to use them or how the kernel works. A properly trained LLM is a useful tool, but it takes a lot of time to reach that point.
> Torvalds and others repeatedly said low-quality contributions from new developers should receive low priority, and that the community should stop trying to make contribution easy. Many developers said, repeatedly, that trying to mentor those developers is almost always a waste of time; they do not listen.
> There is some concern about companies maintaining private kernels with LLM help, but there does not seem to be much to be done about it.
> Kernel developers should not be required to use LLMs to work in the community, but those who do need to have enough resources available to generate acceptable results.
The requirement to add Assisted-by tags to patches created with LLMs will be removed, but maintainers still want to know about how a patch was created.so how's it going already?
> The development community is struggling to keep up with the flood of security patches, and will continue to for some time. Some of the most urgent fixes may bypass maintainers and go straight to Torvalds. Maintainers were cautioned against telling their employers about vulnerabilities before public disclosure happens.
Really, I'm not out to suck ass as much as Microsoft. That will just be a completely unintentional side effect.
@davidgerard Middle-aged men, on very comfortable salaries. This is what happens.
-
@jookia@social.tchncs.de @davidgerard solidarity, you weren't alone with that experience I feel
-
@davidgerard Middle-aged men, on very comfortable salaries. This is what happens.
“You’ll never leave”
jokes on you, dense chucklefuck im packing my bags (or trying)
-
jesus christ, Linux has had a 100% LLM takeover.
this project is completely cooked.
even after the AI bubble pop, it's not clear how to recover from this level of bullshit from this level of bullshitter.
https://lwn.net/SubscriberLink/1099594/be20382b54a9b4cd/
> Linus Torvalds believes that blaming LLMs for the kernel community's problems is wrong, when the problem is LLM users who do not understand how to use them or how the kernel works. A properly trained LLM is a useful tool, but it takes a lot of time to reach that point.
> Torvalds and others repeatedly said low-quality contributions from new developers should receive low priority, and that the community should stop trying to make contribution easy. Many developers said, repeatedly, that trying to mentor those developers is almost always a waste of time; they do not listen.
> There is some concern about companies maintaining private kernels with LLM help, but there does not seem to be much to be done about it.
> Kernel developers should not be required to use LLMs to work in the community, but those who do need to have enough resources available to generate acceptable results.
The requirement to add Assisted-by tags to patches created with LLMs will be removed, but maintainers still want to know about how a patch was created.so how's it going already?
> The development community is struggling to keep up with the flood of security patches, and will continue to for some time. Some of the most urgent fixes may bypass maintainers and go straight to Torvalds. Maintainers were cautioned against telling their employers about vulnerabilities before public disclosure happens.
Really, I'm not out to suck ass as much as Microsoft. That will just be a completely unintentional side effect.
@davidgerard wow, I thought I had more time to get rid of Linux completely. It is a much more pressing issue it seems.
-
“You’ll never leave”
jokes on you, dense chucklefuck im packing my bags (or trying)
Gonna format a storage device that can hold partitions for both Chimera Linux and NetBSD.
That way if I have to slink to linux land for compatibility issues i have a backup
-
@davidgerard "the community should stop trying to make contribution easy." is an incredible statement. Yes, everyone was spoiled by the extremely friendly and welcoming kernel submission experience, jumping through 900 flaming hoops on the LKML to get screamed at.
@moralrecordings @davidgerard real strong “old men yell at those goddamn kids to get off their lawn” vibes from that whole thing.
Open source projects do definitely need to think about succession and passing projects on to the next generation, but I’m pretty sure “fuck you all, piss off” isn’t going to go down in history as one of the better plans for this.
-
@davidgerard Well. So much for the Year of the Linux Desktop.
@kawa @davidgerard Thank God Linux is rarely used on servers or embedded devices.
-
@jookia@social.tchncs.de @davidgerard@circumstances.run a further question is, what about git? will that also slopify?
-
@jookia@social.tchncs.de @davidgerard@circumstances.run yeah. I suppose. Time to see if I can restore the Commodores I had as a child.
-
jesus christ, Linux has had a 100% LLM takeover.
this project is completely cooked.
even after the AI bubble pop, it's not clear how to recover from this level of bullshit from this level of bullshitter.
https://lwn.net/SubscriberLink/1099594/be20382b54a9b4cd/
> Linus Torvalds believes that blaming LLMs for the kernel community's problems is wrong, when the problem is LLM users who do not understand how to use them or how the kernel works. A properly trained LLM is a useful tool, but it takes a lot of time to reach that point.
> Torvalds and others repeatedly said low-quality contributions from new developers should receive low priority, and that the community should stop trying to make contribution easy. Many developers said, repeatedly, that trying to mentor those developers is almost always a waste of time; they do not listen.
> There is some concern about companies maintaining private kernels with LLM help, but there does not seem to be much to be done about it.
> Kernel developers should not be required to use LLMs to work in the community, but those who do need to have enough resources available to generate acceptable results.
The requirement to add Assisted-by tags to patches created with LLMs will be removed, but maintainers still want to know about how a patch was created.so how's it going already?
> The development community is struggling to keep up with the flood of security patches, and will continue to for some time. Some of the most urgent fixes may bypass maintainers and go straight to Torvalds. Maintainers were cautioned against telling their employers about vulnerabilities before public disclosure happens.
Really, I'm not out to suck ass as much as Microsoft. That will just be a completely unintentional side effect.
@davidgerard@circumstances.run killing a project any percent
