>>110066711
>Linus goes on a vibecoding spree
No he didn't.
If you can read the code and fix it, it's just assisted coding.
Vibecode require you to be a retard that can't understand code or don't bother reading it.

>>110066711
Linus is very technically involved in the process, so I wouldn't call it vibecoding. I feel like vibecoding should be reserved for when you're just prompting as if you are semi-technical user.

Linux has been shit for a long time, too many cooks in the kitchen. They've been letting Intel ram random shit into the kernel and letting it rot since forever ago, but they will remove older, perfectly working things for no reason other than "it's old."

At this point if you care about long term stability on your platform of choice you pretty much HAVE to use NetBSD or OpenBSD, heck Haiku even.

>>110066711
>Linux's kernel uses AI
>Windows runs Linux kernel via WSL
>shitple mucshits also runs Linux kernel but who the fuck cares
>consoles all run Linux kernel
>tfw literally every PC and console user supports AI
Wow.

>>110066784
name 1 actual issue with the kernel itself and not user applications

>>110066784
>shilling haiku unironically
Could've told us you're a streetshitter.

>>110066791
>>consoles all run Linux kernel
FreeBSD for PS4/5, literally Windows for the Xbox Series series, IIRC Switch also uses FreeBSD.

>>110066803
I just did, they constantly remove perfectly good drivers and even whole architectures.

>>110066804
Haiku is WHITE and BASED. Street shitters can't use it, it baffles them.

>>110066791
>Windows runs Linux kernel via WSL
WSL2*. WSL1 runs on a subsystem that is compatible with linux 4.4
>consoles all run Linux kernel
so far 0 consoles run linux. except that thing that ran android from 2012
>>110066804
jeets don't know what a haiku is

>>110066816
>I just did, they constantly remove perfectly good drivers and even whole architectures.
30 year old architectures and driver code that are infested with security vulns that not a single person on this earth wants to maintain deserve to be removed hence not an actual issue

>>110066784
Isn't everything in haiku with root access? You just don't have massive virus and spyware problems because nobody is using it

>>110066850
>muh viruses and spyware
Those are WINDOWS problems, exclusive to WINDOWS. The reason other OS's don't have viruses and spyware is because they're not MS AI/jeetslop Windows.

>>110066784
OpenPlacebo is the least secure OS ever made. NetBSD team is retarded, which is too bad because the base is really good. Haiku is too far behind, you might as well suggest KolibriOS at that point.

File: bsdjidf.png (11 KB, 558x86)

11 KB PNG

>>110066946
>OpenPlacebo is the least secure OS ever made.
zip it jew

>NetBSD team is retarded
actually netbsd is great and they barely change much, latest still runs fine on my old Mac SE/30

>Haiku is too far behind
It has everything you need, even modern browsers and a VM now, and 3D is working with many new cards now, finally. It's great.

>>110066975
>not wanting a swiss cheese OS with 0 security is jewish
>recommending actually secure alternatives is not
OK CIA

WINDOWS = VIBECODED
MACOS = VIBECODED
LINUX = VIBECODED
/G/ = RAPED

>>110066784
the more i look into BSD the more it seems like a worse version of linux thats only kept alive by the likes of apple because of its KEK license

dont know haiku but it seems to also have a KEK license but i cant speak to its technical merit

also i believe the bsd devs openly talk about reverse engineering linux drivers anyway soo

>>110066791
AI is fine as long you know how to program and is not blindly inserting code, simple as.
It's a tool that is very good at programming but sometimes makes some absurdly retarded mistakes and you have to point em out.

>>110066711
Nobody is writing code by hand except gatekeeping grognards that should have killed themselves years ago and other assorted masochists.

>>110066931
We had massive AUR virus problems earlier this years. Windows is the OS that most people use so the effort to make viruses will always be there. A computer that everything is running on root on the current day is a toy OS.

>>110067116
>virus
It wasn't a virus, dipshit Windoze user.

>>110067149
I call malware and virus all the same shit. You can't deny the AUR problem with just read the package build bro.

>>110067172
Never did. And these supply chain attacks will continue to spread. Won't be long until they find AI-powered worms, the big AI firms are already talking about how they exist, and may have escaped lel. It already seems like poor practice to pull software off Github. The rolling release model itself is a security risk.

>>110067230
what does rolling release have to do with anything lol
the aur gets malware because everyone can put packages on it, i can probably add malware to the aur right now if i wanted to

>>110067230
>It already seems like poor practice to pull software off Github.
Good news, the whole "recomp" shit is about doing exactly that

>>110067326
>what does rolling release have to do with anything lol
Every release will have to be scrutinized, and all its dependencies, in the future. You won't be able to just download the trunk from shithub.

>>110067334
I won't run that slop.

>>110067344
nobody is scrutinizing hundreds of billions of vibecoded slop mate, if anything linux is moving to a different security model altogether (containerized immutable stuff)

>>110066711
are before and after switched??

>>110068412
nvm

File: 1773299357206659.png (205 KB, 1068x1044)

205 KB PNG

>>110066816
>FreeBSD for PS4/5
>IIRC Switch also uses FreeBSD
So they support AI

>>110066990
OR GAPED FOR SHORT

>>110066711
Based. Drag the luddites kicking and screaming. Linux is finally usable thanks to being able to point my agent towards the console to fix whatever bullshit is going on.

I guess it's finally time to switch to BSD.

>>110066848
you keep the old architectures in because it's free structural userbase. you are required to do absolutely nothing to keep them around and deny them from other competitors looking to eat at your market share. it cements you as the only big guy around and turns you into an impenetrable fortress. these users don't care about corpo cuck vulns either, making them the perfect userbase to have, especially for a project as lazy about security as linux. (inb4 you come tell me how compile time features make the whole project insecure because you're a dumb reddit cretin regurgitating views not your own like an npc rehearsing programmed dialogue.)
removing structural userbase features is the quickest way to open up the market you dominate for foot in the door folks to begin becoming a pain in the ass for you. this was how the web won over desktop and linux won over windows.

Refactoring software is more addictive than heroin

>>110066711
What do you expect from a guy who tried to sell a $70 chinese screwdriver?

>>110069169
isn't the thing built so that if you actually give a shit, you can add and update the thing?
Yes, I understand the same logic can be applied the other direction - but that is what is happening. People want x86_64. It gets maintained, not because someone is performing a charity. It gets maintained because someone wants it and is doing something about it, largely for their own purposes.

If you want support for thirty year old hardware, then maintain it.

It's like people bitching over tech companies buying up (and literally destroying) niche books for LLM training. Fucking retards weren't going to do ANYTHING to preserve those books, and the obvious conclusion is those books would legitimately disappear. They now exist in digital format, and vicariously in the resulting models themselves.

If you care, do something.
If you won't, you don't really care and you're just groaning to groan.

>>110066848
are the security vulns in the room with us right now?

Thats how you should use AI in coding, he obviously knows everything that happened and its consequences, nothing of that is vibe coding

File: 1791860475799729.gif (1.95 MB, 480x264)

1.95 MB GIF

we wouldn't have to remove old drivers and shit from the kernel if they weren't in the kernel to begin with.
linus needs to vibecode linux into the microkernel it always should have been

>>110069422
if the thing's removal causes enough of a stir, it probably was something someone was willing to maintain.
the real problem is that linux is siloed into blocs of autism, and the head autist of each would object to adding someone keen but otherwise green for fear of his pretty garden of autism getting messed up.
either way, you'd want to keep your old shit around because it's easier to choke out competition than to compete with it. if aosp, win32, linux, ecmascript wasn't so backwards and even forwards compatible they would have had real competitors by now.