No! It really doesn't differ qualitatively from previous technological revolutions. That's the whole point. People like Dario present it as qualitatively different.
They are just deluded or biased by their vested interests in magnifying the impact of their work.
@ylecun
-
AI Revolution Claims: Hype or Genuine Paradigm Shift?
By
–
-
AI as Scapegoat: Trade Uncertainty Drives Job Concerns
By
–
There are many causes for that. AI is a good scapegoat. But uncertainties about international trade is likely a much bigger one.
Technological progress does cause temporary shifts in some jobs, but it never causes long-term mass unemployment. -
Technological Progress Displaces Jobs: Historical Perspective
By
–
"one economist Nobel laureate was wrong once about one thing, therefore all economists are wrong" is not good logic. The whole history of technological progress is one in which people became more productive and some professions were progressively displaced or eliminated. Yet
-
Critical perspective on destructive and dangerous AI practices
By
–
It's still wrong, destructive, and dangerous.
-
Technological Revolution Labor Market Effects Economists Analysis
By
–
Dario is wrong.
— Yann LeCun (@ylecun) 18 avril 2026
He knows absolutely nothing about the effects of technological revolutions on the labor market.
Don't listen to him, Sam, Yoshua, Geoff, or me on this topic.
Listen to economists who have spent their career studying this, like @Ph_Aghion , @erikbryn ,… https://t.co/PI3q8ZsobSDario is wrong.
He knows absolutely nothing about the effects of technological revolutions on the labor market. Don't listen to him, Sam, Yoshua, Geoff, or me on this topic.
Listen to economists who have spent their career studying this, like @Ph_Aghion , @erikbryn , -
PyTorch Tensor Architecture: Storage and Multi-Access Design
By
–
The basic structure of a PyTorch tensor is also borrowed from SN/Lush: a storage (a flat array of numbers, for every numerical type) to which one or multiple tensor structures can point, so the same data can be accessed in multiple ways and shared.
-
Lush/SN Lisp Interpreter and Compiler Development History
By
–
And yes, Lush/SN used a homegrown Lisp interpreter, to which a compiler was added in the early 1990s.
-
Better terminology for multidimensional arrays in machine learning
By
–
Do you have a better name than "multidimensional array" though? The name tensor is convenient, if mathematically inaccurate.
-
Tensor Engine History: From Bell Labs to PyTorch
By
–
The tensor engine was first implemented inside SN3 (before it was called Lush) in 1992 at Bell Labs by Léon Bottom and me.
The naming convention has survived to this day in PyTorch and other libraries. The naming of the tensor operations was reused in EBlearn (C++ deep learning -
Balancing Tech Optimism with Democracy and Risk Management
By
–
On peut être à la fois techno-optimiste et anti-techno-féodaliste, pro-démocratie, conscient des risques et travaillant à maximiser les effets bénéfiques et à minimiser les effets négatifs.