Wonderful. Linus Torvalds says that AI is a useful tool, no questions about it, and that anybody who says the opposite has not used it. Even if they did.
How many anti AI people you think work at a place where they're forced to burn tokens because "AI is the greatest thing ever"?
He says that you either accept it, or do the impossible and fork the whole thing. Maybe in the future we will be using FreeBSD. At this rate anything is possible, maybe even going back to Winblows, if I'm going to use AI slop generated software I might as well.
Since Linus is no longer writing code and he's just a maintainer, he'd do well in stepping down and letting people who clearly has a better idea on how to maintain the kernel than he does do the job instead. He can retire and live off of his AI stocks until the market crash if he wants. And have the AI write another Python script for him.
Timeline
Post
Remote status
Context
3
@enigmatico neverclanking was never a sustainable position. mandatory copilot use was never a reasonable one. high performers try (and occasionally re-try) technology and don't keep the stuff that doesn't work. for some low grade intern tasks it now does.
if/when the AI models really did reach the industrial revolution stage of usefulness there is nothing that screaming from the streets would do about it--the luddites being steamrolled already proved that. the curiosity is that it hasn't reached that, and management was trying to act like it already had to the great disconnect of reality that it was. (they are now, to some extent, eating shit for that as the VCs rug pull token prices.)
if/when the AI models really did reach the industrial revolution stage of usefulness there is nothing that screaming from the streets would do about it--the luddites being steamrolled already proved that. the curiosity is that it hasn't reached that, and management was trying to act like it already had to the great disconnect of reality that it was. (they are now, to some extent, eating shit for that as the VCs rug pull token prices.)
@icedquinn @enigmatico even Donald knuth was amazed at claude, no?
@mischievoustomato @enigmatico a mixture of amazed and concerned has been the pretty default opinion for that kind of tech. people being forced to interact with it when it's not deliverable quality is ultimately where the hateboners came from.
art directors were already putting "ai art" on probation (and, ultimately, rejecting it because they are control freaks. even procedural art and nodal systems were often rejected) which is annoying because i like the procedural/node stuff and it keeps getting thrown in the graveyard.
it's this weird nexus point where it looks good enough to management and low quality to everyone else combined with management salivating over getting to fire everyone that has resulted in whatever the fuck we have now
art directors were already putting "ai art" on probation (and, ultimately, rejecting it because they are control freaks. even procedural art and nodal systems were often rejected) which is annoying because i like the procedural/node stuff and it keeps getting thrown in the graveyard.
it's this weird nexus point where it looks good enough to management and low quality to everyone else combined with management salivating over getting to fire everyone that has resulted in whatever the fuck we have now
Replies
2
@icedquinn @enigmatico @mischievoustomato tech is a graveyard of this stuff, I remember getting forced to use service oriented architecture for future stuff where you needed 4x as much RAM and wizards to autogenerate all your code, then after a couple years everybody realized it was shit and it disappeared. I don't think this is gonna disappear though
@sun @enigmatico @mischievoustomato code generation is one of those things that is always super neat and it ends up in the same pile as the node based processing stuff 
i liked imatix gsl for the reason that low friction xml->template->c is really nice for boilerplate management. but that field got stuck in "generate uml maybe" and even then usually bogged to a single form of state machine. sad.
i liked imatix gsl for the reason that low friction xml->template->c is really nice for boilerplate management. but that field got stuck in "generate uml maybe" and even then usually bogged to a single form of state machine. sad.