← All reports

The criticism of AI is part of a historical pattern where new technologies are blamed for issues that arise from their use.

TechnologyHistoryAIOct 19, 2026score 0.172 posts · 0 replies across 1 instances
The thread discusses the recurring pattern of blaming new technologies for issues, using historical examples from programming to AI. It highlights the cyclical nature of technological criticism and the importance of thorough testing. This matters because it reflects broader societal attitudes toward technological advancement and responsibility.

Claims

The criticism of AI is part of a historical pattern where new technologies are blamed for issues that arise from their use.
Parent: AIEntity: Technological advancementImpact: negativeDate: Oct 19, 2026Target: The pattern of blaming new technologies for issues

Source posts

@[email protected]
One thing I notice, coming from the past at full speed to crush this regressive "progress", is how they blame AI as if anyone forced them to use it. Back in the day, people coded in 0 and 1, and when assembly came along, they blamed it for laziness. Then compilers arrived, and again, they blamed their use, claiming they produced "slop". Then came Search Engines and Stack Overflow, and they blamed them for copy-pasting. And now we reach today, where they blame AI using the exact same logic. Code, if not carefully reviewed, will have its bugs regardless of how it was made. Whether from human exhaustion, flawed program logic, or alien technology and incompatibility. So, it is best to check and test it as much as we can. This won't make it bug-free, but it will greatly reduce errors. Which will still inevitably pop up as new ones due to legacy status, since times change, demands change, compatibility changes, and it always requires our adaptation. The thing is simple: whoever doesn't want to use them shouldn't, and they can go make their own programs, and we move on. Nobody is forcing you. But... Evolution waits for no one. Whoever doesn't follow gets left behind on the platform. The train makes brief stops and never passes through the same station again. #Programming #AI #Tech #Technology #Slop #Coding #OpenSource #Compiler #VibeCoding
0 boosts · 0 favs · 0 replies · Oct 19, 2026
#programming#ai#tech#technology#slop#coding
@[email protected]
One thing I notice, sparked by Linus Torvalds and the Kernel, coming from the past at full speed to crush this regressive "progress", is how they blame AI as if anyone forced them to use it. Back in the day, people coded in 0 and 1, and when assembly came along, they blamed it for laziness. Then compilers arrived, and again, they blamed their use, claiming they produced "slop". Then came Search Engines and Stack Overflow, and they blamed them for copy-pasting. And now we reach today, where they blame AI using the exact same logic. Code, if not carefully reviewed, will have its bugs regardless of how it was made. Whether from human exhaustion, flawed program logic, or alien technology and incompatibility. So, it is best to check and test it as much as we can. This won't make it bug-free, but it will greatly reduce errors. Which will still inevitably pop up as new ones due to legacy status, since times change, demands change, compatibility changes, and it always requires our adaptation. The thing is simple: whoever doesn't want to use them shouldn't, and they can go make their own programs, and we move on. Nobody is forcing you. But... Evolution waits for no one. Whoever doesn't follow gets left behind on the platform. The train makes brief stops and never passes through the same station again. #Programming #AI #Tech #Technology #Slop #Coding #OpenSource #Compiler #VibeCoding
0 boosts · 0 favs · 0 replies · Oct 19, 2026
#programming#ai#tech#technology#slop#coding