#aihype — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #aihype, aggregated by home.social.
-
"Tech CEOs are apparently suffering from AI psychosis" by @TechCrunch - Being farthest removed from the "last mile" where work needs to be done, CEOs are vulnerable to falling for a trap which they as leaders hold responsibility to prevent. Those who act on their beliefs without restraint are setting up their companies for failure. The article author hopes enough CEOs will get training to understand limits of #AI #tech. https://techcrunch.com/2026/05/27/tech-ceos-are-apparently-suffering-from-ai-psychosis/ #AIhype #AIpsychosis #business #oops #WTF
-
"Tech CEOs are apparently suffering from AI psychosis" by @TechCrunch - Being farthest removed from the "last mile" where work needs to be done, CEOs are vulnerable to falling for a trap which they as leaders hold responsibility to prevent. Those who act on their beliefs without restraint are setting up their companies for failure. The article author hopes enough CEOs will get training to understand limits of #AI #tech. https://techcrunch.com/2026/05/27/tech-ceos-are-apparently-suffering-from-ai-psychosis/ #AIhype #AIpsychosis #business #oops #WTF
-
"Tech CEOs are apparently suffering from AI psychosis" by @TechCrunch - Being farthest removed from the "last mile" where work needs to be done, CEOs are vulnerable to falling for a trap which they as leaders hold responsibility to prevent. Those who act on their beliefs without restraint are setting up their companies for failure. The article author hopes enough CEOs will get training to understand limits of #AI #tech. https://techcrunch.com/2026/05/27/tech-ceos-are-apparently-suffering-from-ai-psychosis/ #AIhype #AIpsychosis #business #oops #WTF
-
"Tech CEOs are apparently suffering from AI psychosis" by @TechCrunch - Being farthest removed from the "last mile" where work needs to be done, CEOs are vulnerable to falling for a trap which they as leaders hold responsibility to prevent. Those who act on their beliefs without restraint are setting up their companies for failure. The article author hopes enough CEOs will get training to understand limits of #AI #tech. https://techcrunch.com/2026/05/27/tech-ceos-are-apparently-suffering-from-ai-psychosis/ #AIhype #AIpsychosis #business #oops #WTF
-
"Tech CEOs are apparently suffering from AI psychosis" by @TechCrunch - Being farthest removed from the "last mile" where work needs to be done, CEOs are vulnerable to falling for a trap which they as leaders hold responsibility to prevent. Those who act on their beliefs without restraint are setting up their companies for failure. The article author hopes enough CEOs will get training to understand limits of #AI #tech. https://techcrunch.com/2026/05/27/tech-ceos-are-apparently-suffering-from-ai-psychosis/ #AIhype #AIpsychosis #business #oops #WTF
-
"Unfortunately, it’s difficult to make a crisp comparison, but the proxies that we have suggest that demand is growing much faster. For instance, both the quantity of tokens processed by Google in the last year, and by all providers according to Exponential View, have been growing by around 10×/year.
From another angle, we can look at token demand from today’s most intensive AI users: software engineers. Recent reports claim that some of Apple’s software engineers are permitted to use up to $300 in tokens per day, which works out to about 5 million output tokens per day with Claude Opus 4.7 API pricing, or 25 million output tokens per day with Kimi K2.6.16 Another point of comparison comes from Meta, whose 85,000 employees used 60 trillion tokens in one month across the organization. That figure included both input and output tokens; assuming a 25,000:1,000 input-to-output token ratio, that would be around 1 million output tokens per day and employee.
There were about 30 million software engineers worldwide as of 2025 (estimates range from 20 million to 50 million), and Stack Overflow’s 2025 survey on AI usage suggested that only around 47% of developers used AI on a daily basis, as of mid-2025. If all SWEs using AI daily were using it as intensely as Meta or Apple, they would demand somewhere between 10 and 350 trillion tokens per day in aggregate, i.e., between 200 million and 4 billion tokens per second. At the longest context sizes of 128,000:1,000, today’s Blackwell chips would struggle to serve all this potential demand for coding agents using models as large as Kimi K2.6. It also seems likely that both the number of developers using AI, and the intensity of their use will continue to grow rapidly."
https://epoch.ai/gradient-updates/is-a-compute-crunch-coming
#AI #GenerativeAI #AIBubble #Compute #AIHype #DataCenters #Inference
-
"Unfortunately, it’s difficult to make a crisp comparison, but the proxies that we have suggest that demand is growing much faster. For instance, both the quantity of tokens processed by Google in the last year, and by all providers according to Exponential View, have been growing by around 10×/year.
From another angle, we can look at token demand from today’s most intensive AI users: software engineers. Recent reports claim that some of Apple’s software engineers are permitted to use up to $300 in tokens per day, which works out to about 5 million output tokens per day with Claude Opus 4.7 API pricing, or 25 million output tokens per day with Kimi K2.6.16 Another point of comparison comes from Meta, whose 85,000 employees used 60 trillion tokens in one month across the organization. That figure included both input and output tokens; assuming a 25,000:1,000 input-to-output token ratio, that would be around 1 million output tokens per day and employee.
There were about 30 million software engineers worldwide as of 2025 (estimates range from 20 million to 50 million), and Stack Overflow’s 2025 survey on AI usage suggested that only around 47% of developers used AI on a daily basis, as of mid-2025. If all SWEs using AI daily were using it as intensely as Meta or Apple, they would demand somewhere between 10 and 350 trillion tokens per day in aggregate, i.e., between 200 million and 4 billion tokens per second. At the longest context sizes of 128,000:1,000, today’s Blackwell chips would struggle to serve all this potential demand for coding agents using models as large as Kimi K2.6. It also seems likely that both the number of developers using AI, and the intensity of their use will continue to grow rapidly."
https://epoch.ai/gradient-updates/is-a-compute-crunch-coming
#AI #GenerativeAI #AIBubble #Compute #AIHype #DataCenters #Inference
-
"Unfortunately, it’s difficult to make a crisp comparison, but the proxies that we have suggest that demand is growing much faster. For instance, both the quantity of tokens processed by Google in the last year, and by all providers according to Exponential View, have been growing by around 10×/year.
From another angle, we can look at token demand from today’s most intensive AI users: software engineers. Recent reports claim that some of Apple’s software engineers are permitted to use up to $300 in tokens per day, which works out to about 5 million output tokens per day with Claude Opus 4.7 API pricing, or 25 million output tokens per day with Kimi K2.6.16 Another point of comparison comes from Meta, whose 85,000 employees used 60 trillion tokens in one month across the organization. That figure included both input and output tokens; assuming a 25,000:1,000 input-to-output token ratio, that would be around 1 million output tokens per day and employee.
There were about 30 million software engineers worldwide as of 2025 (estimates range from 20 million to 50 million), and Stack Overflow’s 2025 survey on AI usage suggested that only around 47% of developers used AI on a daily basis, as of mid-2025. If all SWEs using AI daily were using it as intensely as Meta or Apple, they would demand somewhere between 10 and 350 trillion tokens per day in aggregate, i.e., between 200 million and 4 billion tokens per second. At the longest context sizes of 128,000:1,000, today’s Blackwell chips would struggle to serve all this potential demand for coding agents using models as large as Kimi K2.6. It also seems likely that both the number of developers using AI, and the intensity of their use will continue to grow rapidly."
https://epoch.ai/gradient-updates/is-a-compute-crunch-coming
#AI #GenerativeAI #AIBubble #Compute #AIHype #DataCenters #Inference
-
"Unfortunately, it’s difficult to make a crisp comparison, but the proxies that we have suggest that demand is growing much faster. For instance, both the quantity of tokens processed by Google in the last year, and by all providers according to Exponential View, have been growing by around 10×/year.
From another angle, we can look at token demand from today’s most intensive AI users: software engineers. Recent reports claim that some of Apple’s software engineers are permitted to use up to $300 in tokens per day, which works out to about 5 million output tokens per day with Claude Opus 4.7 API pricing, or 25 million output tokens per day with Kimi K2.6.16 Another point of comparison comes from Meta, whose 85,000 employees used 60 trillion tokens in one month across the organization. That figure included both input and output tokens; assuming a 25,000:1,000 input-to-output token ratio, that would be around 1 million output tokens per day and employee.
There were about 30 million software engineers worldwide as of 2025 (estimates range from 20 million to 50 million), and Stack Overflow’s 2025 survey on AI usage suggested that only around 47% of developers used AI on a daily basis, as of mid-2025. If all SWEs using AI daily were using it as intensely as Meta or Apple, they would demand somewhere between 10 and 350 trillion tokens per day in aggregate, i.e., between 200 million and 4 billion tokens per second. At the longest context sizes of 128,000:1,000, today’s Blackwell chips would struggle to serve all this potential demand for coding agents using models as large as Kimi K2.6. It also seems likely that both the number of developers using AI, and the intensity of their use will continue to grow rapidly."
https://epoch.ai/gradient-updates/is-a-compute-crunch-coming
#AI #GenerativeAI #AIBubble #Compute #AIHype #DataCenters #Inference
-
"Unfortunately, it’s difficult to make a crisp comparison, but the proxies that we have suggest that demand is growing much faster. For instance, both the quantity of tokens processed by Google in the last year, and by all providers according to Exponential View, have been growing by around 10×/year.
From another angle, we can look at token demand from today’s most intensive AI users: software engineers. Recent reports claim that some of Apple’s software engineers are permitted to use up to $300 in tokens per day, which works out to about 5 million output tokens per day with Claude Opus 4.7 API pricing, or 25 million output tokens per day with Kimi K2.6.16 Another point of comparison comes from Meta, whose 85,000 employees used 60 trillion tokens in one month across the organization. That figure included both input and output tokens; assuming a 25,000:1,000 input-to-output token ratio, that would be around 1 million output tokens per day and employee.
There were about 30 million software engineers worldwide as of 2025 (estimates range from 20 million to 50 million), and Stack Overflow’s 2025 survey on AI usage suggested that only around 47% of developers used AI on a daily basis, as of mid-2025. If all SWEs using AI daily were using it as intensely as Meta or Apple, they would demand somewhere between 10 and 350 trillion tokens per day in aggregate, i.e., between 200 million and 4 billion tokens per second. At the longest context sizes of 128,000:1,000, today’s Blackwell chips would struggle to serve all this potential demand for coding agents using models as large as Kimi K2.6. It also seems likely that both the number of developers using AI, and the intensity of their use will continue to grow rapidly."
https://epoch.ai/gradient-updates/is-a-compute-crunch-coming
#AI #GenerativeAI #AIBubble #Compute #AIHype #DataCenters #Inference
-
"New revelations about OpenAI’s finances paint a dim picture for the company, as The Information reported it generated just $5.7bn in the first quarter of 2026, with an adjusted operating margin of -122%.
This means that for every dollar of revenue the company generated, it lost $1.22.
As The Information’s Sri Muppidi noted, these operating margins were adjusted — and, presumably, didn’t conform to GAAP (or generally accepted accounting principles) standards — and excluded certain “large line items”, like stock-based compensation.
By that maths, that means that OpenAI lost $6.95 billion in the quarter, and because this is non-GAAP, it’s quite possible that losses are much higher, revenues are lower, and its margins are worse. The piece does not specify if operating margin includes or excludes training costs, nor does it break down what other exclusions there may be other than stock-based compensation.
The report also claims that OpenAI is “on track” to hit its goal of generating $30bn in revenue for 2026, although if it maintains these disastrous margins, it would end up losing $36.6bn."
-
"If we assume that its spend is comparable on AWS and Google Cloud — and it’s most-assuredly more! — that means Anthropic is spending around $3.75 billion in compute costs, or $11.25 billion a quarter, or $45 billion a year.
There’s also a very compelling argument that Anthropic’s costs will increase and will eat up that profitability, to once again quote the Wall Street Journal:
The company might not remain profitable for the full year as it plans spending increases due to its vast computing needs.
I also have to wonder: if you’re so profitable, why not IPO? Why not take this to the public markets?Unless, of course, you’re only non-GAAP EBITDA profitable based on a two-month-long discount specifically covering the period in which you’re profitable. And, of course, when you’re not a publicly-traded company, and so you don’t actually have to publish any numbers (and no, leaking them doesn’t count), and you’re not subject to SEC oversight.
I will give Dario Amodei credit: nobody does financial engineering and a press-led information war better than Anthropic. The willingness of the press to eat up incongruent numbers and the eagerness of many to jump up and find obtuse ways to explain away the obvious problems is only made possible when a company has perfected the art of manipulation and ingratiation of those who want to feel like they’re “first.”
If you take this as incontrovertible proof that Anthropic is profitable, you are deliberately ignoring the blatantly obvious ways these numbers are being massaged. We’ve got its CFO saying numbers that don’t match up with these leaks or Anthropic’s own marketing materials, and the aggressive and deluded way in which many people ignore them is equal parts frustrating and depressing."
https://www.wheresyoured.at/anthropics-profitability-swindle/
-
On how to unconvincingly weasel your way out of a big LLM 💩 …
[…] Mr. Rosenbaum’s book contains many quotes that are accurate, but the misattributed and invented quotes are scattered throughout.
[…] In his statement, Mr. Rosenbaum said that if the episode “serves as a warning about the risks of A.I.-assisted research and verification, that is why I wrote the book.”
https://www.nytimes.com/2026/05/19/business/media/future-of-truth-ai-quotes.html
#AI is a marketing term, not a technology. Preferred term should be the term #llm because that’s what it is. Also, I’m pretty sure this will be normalized soon enough and we will be told to just relax and accept this equivalent of ultra-processed food as acceptable compromise.
-
File under: AI Resistance
I'm reading – and enjoying immensely – @emilymbender and @alex's book #TheAICon.
I've been learning a lot of things and something that really stood out recently is the need to be careful about the language we use to describe these systems. Bender and Hanna helpfully explain:
"It matters what words we use when we talk about these technologies. For instance, in our writing, we don’t use the term “hallucination” to discuss the errors of LLMs, for two reasons. First, if it’s used tongue-in-cheek, it is making light of what can be symptoms of serious mental illness. Second,
“hallucination” refers to the experience of perceiving things that aren’t there. But LLMs actually don’t have perceptions, and suggesting that they do is yet more unhelpful anthropomorphization. That means we also avoid assigning thought processes to these systems, or saying that they can
“think”. Metaphors have power, they structure the frames of discourse, and they can subtly and insidiously encourage certain ways of understanding technology and the social systems it is embedded in."Antropomorphizing AI contributes to AI hype. Thanks Emily and Alex for helping me see things this way!
-
"[R]emember that US GDP growth currently is driven exclusively by rising tech spending. If these start to drop, the US economy will enter recession very quickly — even if tech investments decline only by a little bit, say 4 to 6 per cent, as happened after much smaller tech booms in the 1960s and during the 2009 recession.
Such a mild correction in investment spending is likely to still send stock markets in the US, UK and across Europe into a new bear market. A repeat of the tech crash in the early 2000s is a real risk with stock market drops of 50 per cent or more in the first year.
The question then becomes, when could we see such announcements by the hyperscalers? I think it is unlikely to happen in 2026. The efforts by OpenAI, Anthropic and others to keep the hype going at least until after their respective IPOs are likely to support the boom for now. But then what? The impossible maths of hyperscalers stays the same, but the marketing hype may fade. And eventually, reality will kick in.
Probably not in 2026, but possibly in 2027 or 2028. After all, Greenspan talked about irrational exuberance in December 1996, but the bubble only burst three years later in 2000.
Viewed through this lens, the IPO of these AI companies is probably nothing more than a major transfer of investment risk from the current owners to retail investors, pension funds and others who are willing to buy the hype."
https://www.ft.com/content/32bf8935-8d21-4689-ae34-8b4d3d5f6d93
-
Unfortunately, the field is still very white, male, and able-bodied
https://2026.stateofai.dev/en-US/demographics/
#amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev
-
Unfortunately, the field is still very white, male, and able-bodied
https://2026.stateofai.dev/en-US/demographics/
#amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev
-
Unfortunately, the field is still very white, male, and able-bodied
https://2026.stateofai.dev/en-US/demographics/
#amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev
-
Unfortunately, the field is still very white, male, and able-bodied
https://2026.stateofai.dev/en-US/demographics/
#amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev
-
Unfortunately, the field is still very white, male, and able-bodied
https://2026.stateofai.dev/en-US/demographics/
#amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev
-
Despite constant claims by #AI companies that #AGI is within one's grasp, people are not entirely buying it
https://2026.stateofai.dev/en-US/opinions/#reach_agi
https://www.jakecuth.com/work/agi-forecast-lab/
#amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev #Superintelligence #SuperhumanAI
-
Despite constant claims by #AI companies that #AGI is within one's grasp, people are not entirely buying it
https://2026.stateofai.dev/en-US/opinions/#reach_agi
https://www.jakecuth.com/work/agi-forecast-lab/
#amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev #Superintelligence #SuperhumanAI
-
Despite constant claims by #AI companies that #AGI is within one's grasp, people are not entirely buying it
https://2026.stateofai.dev/en-US/opinions/#reach_agi
https://www.jakecuth.com/work/agi-forecast-lab/
#amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev #Superintelligence #SuperhumanAI
-
Despite constant claims by #AI companies that #AGI is within one's grasp, people are not entirely buying it
https://2026.stateofai.dev/en-US/opinions/#reach_agi
https://www.jakecuth.com/work/agi-forecast-lab/
#amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev #Superintelligence #SuperhumanAI
-
Despite constant claims by #AI companies that #AGI is within one's grasp, people are not entirely buying it
https://2026.stateofai.dev/en-US/opinions/#reach_agi
https://www.jakecuth.com/work/agi-forecast-lab/
#amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev #Superintelligence #SuperhumanAI
-
#AIDeskilling is a real thing in the wake of #AI: 68% of all participants in the #StateOfAI2026 survey agree or strongly agree that due to their heavy reliance, they are becoming less and less skilled
https://2026.stateofai.dev/en-US/opinions/#ai_reliance_worse_developers
#amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev #Deskilling #WorkforceDeskilling #artificialIntelligence
-
#AIDeskilling is a real thing in the wake of #AI: 68% of all participants in the #StateOfAI2026 survey agree or strongly agree that due to their heavy reliance, they are becoming less and less skilled
https://2026.stateofai.dev/en-US/opinions/#ai_reliance_worse_developers
#amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev #Deskilling #WorkforceDeskilling #artificialIntelligence
-
#AIDeskilling is a real thing in the wake of #AI: 68% of all participants in the #StateOfAI2026 survey agree or strongly agree that due to their heavy reliance, they are becoming less and less skilled
https://2026.stateofai.dev/en-US/opinions/#ai_reliance_worse_developers
#amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev #Deskilling #WorkforceDeskilling #artificialIntelligence
-
#AIDeskilling is a real thing in the wake of #AI: 68% of all participants in the #StateOfAI2026 survey agree or strongly agree that due to their heavy reliance, they are becoming less and less skilled
https://2026.stateofai.dev/en-US/opinions/#ai_reliance_worse_developers
#amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev #Deskilling #WorkforceDeskilling #artificialIntelligence
-
#AIDeskilling is a real thing in the wake of #AI: 68% of all participants in the #StateOfAI2026 survey agree or strongly agree that due to their heavy reliance, they are becoming less and less skilled
https://2026.stateofai.dev/en-US/opinions/#ai_reliance_worse_developers
#amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev #Deskilling #WorkforceDeskilling #artificialIntelligence
-
"#AI is getting better and better!"
"Look, how far we've come!"
Yet, the percentage of participants for whom hallucinations and inaccuracies are pain point, have increased by 63%(!), let alone, truthfulness is the most requested feature with nearly 50%(!)https://2026.stateofai.dev/en-US/risks-pain-points/
#AIHallucination #amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev #artificialIntelligence
-
"#AI is getting better and better!"
"Look, how far we've come!"
Yet, the percentage of participants for whom hallucinations and inaccuracies are pain point, have increased by 63%(!), let alone, truthfulness is the most requested feature with nearly 50%(!)https://2026.stateofai.dev/en-US/risks-pain-points/
#AIHallucination #amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev #artificialIntelligence
-
"#AI is getting better and better!"
"Look, how far we've come!"
Yet, the percentage of participants for whom hallucinations and inaccuracies are pain point, have increased by 63%(!), let alone, truthfulness is the most requested feature with nearly 50%(!)https://2026.stateofai.dev/en-US/risks-pain-points/
#AIHallucination #amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev #artificialIntelligence
-
"#AI is getting better and better!"
"Look, how far we've come!"
Yet, the percentage of participants for whom hallucinations and inaccuracies are pain point, have increased by 63%(!), let alone, truthfulness is the most requested feature with nearly 50%(!)https://2026.stateofai.dev/en-US/risks-pain-points/
#AIHallucination #amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev #artificialIntelligence
-
"#AI is getting better and better!"
"Look, how far we've come!"
Yet, the percentage of participants for whom hallucinations and inaccuracies are pain point, have increased by 63%(!), let alone, truthfulness is the most requested feature with nearly 50%(!)https://2026.stateofai.dev/en-US/risks-pain-points/
#AIHallucination #amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev #artificialIntelligence
-
While Rust leaves "environmental issues aside", the concern of military use of #artificialIntelligence comes third(!) in the #StateOfAI2026 survey
https://2026.stateofai.dev/en-US/risks-pain-points/#ai_risks
https://github.com/rust-lang/rust-forge/pull/1040
#amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev #RustLang #RustForge
-
While Rust leaves "environmental issues aside", the concern of military use of #artificialIntelligence comes third(!) in the #StateOfAI2026 survey
https://2026.stateofai.dev/en-US/risks-pain-points/#ai_risks
https://github.com/rust-lang/rust-forge/pull/1040
#amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev #RustLang #RustForge
-
While Rust leaves "environmental issues aside", the concern of military use of #artificialIntelligence comes third(!) in the #StateOfAI2026 survey
https://2026.stateofai.dev/en-US/risks-pain-points/#ai_risks
https://github.com/rust-lang/rust-forge/pull/1040
#amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev #RustLang #RustForge
-
While Rust leaves "environmental issues aside", the concern of military use of #artificialIntelligence comes third(!) in the #StateOfAI2026 survey
https://2026.stateofai.dev/en-US/risks-pain-points/#ai_risks
https://github.com/rust-lang/rust-forge/pull/1040
#amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev #RustLang #RustForge
-
While Rust leaves "environmental issues aside", the concern of military use of #artificialIntelligence comes third(!) in the #StateOfAI2026 survey
https://2026.stateofai.dev/en-US/risks-pain-points/#ai_risks
https://github.com/rust-lang/rust-forge/pull/1040
#amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev #RustLang #RustForge
-
While the pentagon makes deals with #AI companies, the concern of military use of #artificialIntelligence comes second(!) in the #StateOfAI2026 survey
https://2026.stateofai.dev/en-US/risks-pain-points/#ai_risks
#amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev
-
While the pentagon makes deals with #AI companies, the concern of military use of #artificialIntelligence comes second(!) in the #StateOfAI2026 survey
https://2026.stateofai.dev/en-US/risks-pain-points/#ai_risks
#amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev
-
While the pentagon makes deals with #AI companies, the concern of military use of #artificialIntelligence comes second(!) in the #StateOfAI2026 survey
https://2026.stateofai.dev/en-US/risks-pain-points/#ai_risks
#amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev
-
While the pentagon makes deals with #AI companies, the concern of military use of #artificialIntelligence comes second(!) in the #StateOfAI2026 survey
https://2026.stateofai.dev/en-US/risks-pain-points/#ai_risks
#amCoding #amProgramming #StateOfAI #noAI #AIHype #softwareEngineering #softwareDevelopment #StateOfWebDev
