Tesla just increased its spending plan to $25B — here’s where the money is going | TechCrunch
Tesla CEO Elon Musk kicked off the company’s first-quarter earnings call with a monetary heads-up — or depending on the mindset of the investor, a warning. Tesla’s capital expenditures will skyrocket to $25 billion in 2026, far outpacing its previous annual spend as it races to stay ahead of the competition and transitions to an AI and robotics company, according to its first-quarter earnings report.
That figure, which covers what Tesla plans to spend on physical assets outside of its day-to-day operating expenditures, is three times higher than its annual capex budget in previous years. For comparison, Tesla’s annual capital expenditures were $8.5 billion in 2025, $11.3 billion in 2024, and $8.9 billion in 2023.
Tesla had announced in January that it expected capital expenditures to be in excess of $20 billion in 2026, already a substantial increase meant to cover its AI initiatives, including investments in compute infrastructure and data centers, and the expansion and ramp of its manufacturing and R&D production lines, among other items.
This $5 billion uptick suggests these initiatives will require more money than previously planned. But so far, its quarterly capital expenditure, which was $2.5 billion, was in line with previous quarters, the report shows.
Of course, Musk views this as a positive, a sentiment many other shareholders will likely also share since it positions Tesla as a company investing in its future, namely AI and robotics.
“With 2026 we’re going to be substantially increasing our investments in the future,” Musk said in the earnings call Wednesday. “So you should expect to see significant, a very significant increase in capital expenditures, but I think well justified for a substantially increased future revenue stream.”
Musk was quick to note that Tesla isn’t the only company raising its capital expenditure budget. Amazon, for instance, has projected $200 billion in capital expenditures in 2026, across “AI, chips, robotics, and low earth orbit satellites.” Google is slated to spend between $175 billion and $185 billion in capital expenditures in 2026, up from $91.4 billion the previous year.
Techcrunch event
San Francisco, CA
|
October 13-15, 2026
The increase in Tesla’s capital expenditures is linked to Musk’s desire and ambition to evolve the company beyond building and selling EVs, solar, and energy storage.
Some of the capex spend will go toward Tesla’s core technologies such as its battery and AI software, according to Musk. The company plans to invest in AI training, chip design, and “laying the groundwork” for increasing manufacturing production, as well as invest in its robotaxi operations and its new semiconductor research fab in Austin.
The Fremont, California, factory will likely suck up some of that capital as the company ends production of the Tesla Model S and Model X and begins building its Optimus humanoid robot at scale. The company said Wednesday it has also cleared ground outside its Austin factory for a dedicated Optimus manufacturing facility.
Tesla plans to increase its internal production of Optimus for testing and then “probably” make Optimus “useful outside of Tesla sometime next year,” he said.
Tesla is also putting money toward strengthening its supply chain “across the board,” Musk said, adding that this covers batteries, energy, and AI silicon.
All of this spending, which CFO Vaibhav Taneja said will last a couple of years, comes with a literal cost. The company — which enjoyed a brief 4% share price bump due, in part, to an unexpected $1.4 billion in free cash flow — will head into negative territory later this year, Taneja said.
Tesla shares erased their gains in after-hours trading as Musk and Taneja laid out these plans to investors. Still, Tesla is sitting on loads of cash. At the end of the first quarter, Tesla reported $44.7 billion in cash, cash equivalents, and short-term investments.
“While this may seem like a lot, and we will have the impact of negative free cash flow for the rest of the year, we believe this is the right strategy to position the company for the next era,” Taneja said.
Tesla CEO Elon Musk kicked off the company’s first-quarter earnings call with a monetary heads-up — or depending on the mindset of the investor, a warning. Tesla’s capital expenditures will skyrocket to $25 billion in 2026, far outpacing its previous annual spend as it races to stay ahead of the competition and transitions to an AI and robotics company, according to its first-quarter earnings report.
That figure, which covers what Tesla plans to spend on physical assets outside of its day-to-day operating expenditures, is three times higher than its annual capex budget in previous years. For comparison, Tesla’s annual capital expenditures were $8.5 billion in 2025, $11.3 billion in 2024, and $8.9 billion in 2023.
Tesla had announced in January that it expected capital expenditures to be in excess of $20 billion in 2026, already a substantial increase meant to cover its AI initiatives, including investments in compute infrastructure and data centers, and the expansion and ramp of its manufacturing and R&D production lines, among other items.
This $5 billion uptick suggests these initiatives will require more money than previously planned. But so far, its quarterly capital expenditure, which was $2.5 billion, was in line with previous quarters, the report shows.
Of course, Musk views this as a positive, a sentiment many other shareholders will likely also share since it positions Tesla as a company investing in its future, namely AI and robotics.
“With 2026 we’re going to be substantially increasing our investments in the future,” Musk said in the earnings call Wednesday. “So you should expect to see significant, a very significant increase in capital expenditures, but I think well justified for a substantially increased future revenue stream.”
Musk was quick to note that Tesla isn’t the only company raising its capital expenditure budget. Amazon, for instance, has projected $200 billion in capital expenditures in 2026, across “AI, chips, robotics, and low earth orbit satellites.” Google is slated to spend between $175 billion and $185 billion in capital expenditures in 2026, up from $91.4 billion the previous year.
Techcrunch event
San Francisco, CA | October 13-15, 2026
The increase in Tesla’s capital expenditures is linked to Musk’s desire and ambition to evolve the company beyond building and selling EVs, solar, and energy storage.
Some of the capex spend will go toward Tesla’s core technologies such as its battery and AI software, according to Musk. The company plans to invest in AI training, chip design, and “laying the groundwork” for increasing manufacturing production, as well as invest in its robotaxi operations and its new semiconductor research fab in Austin.
The Fremont, California, factory will likely suck up some of that capital as the company ends production of the Tesla Model S and Model X and begins building its Optimus humanoid robot at scale. The company said Wednesday it has also cleared ground outside its Austin factory for a dedicated Optimus manufacturing facility.
Tesla plans to increase its internal production of Optimus for testing and then “probably” make Optimus “useful outside of Tesla sometime next year,” he said.
Tesla is also putting money toward strengthening its supply chain “across the board,” Musk said, adding that this covers batteries, energy, and AI silicon.
All of this spending, which CFO Vaibhav Taneja said will last a couple of years, comes with a literal cost. The company — which enjoyed a brief 4% share price bump due, in part, to an unexpected $1.4 billion in free cash flow — will head into negative territory later this year, Taneja said.
Tesla shares erased their gains in after-hours trading as Musk and Taneja laid out these plans to investors. Still, Tesla is sitting on loads of cash. At the end of the first quarter, Tesla reported $44.7 billion in cash, cash equivalents, and short-term investments.
“While this may seem like a lot, and we will have the impact of negative free cash flow for the rest of the year, we believe this is the right strategy to position the company for the next era,” Taneja said.
When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.
#Tesla #increased #spending #plan #25B #heres #money #TechCrunchElon Musk,Tesla
![Masochistic YouTuber Punishes Himself by Writing a First Person Shooter Entirely in COBOL
So: masochism. You might know that it takes its name from 19th-century Austrian nobleman and writer Leopold Ritter von Sacher-Masoch—and specifically from the content of his famous work, Venus in Furs, which catalogued the narrator’s submissive nature and fondness for experiencing pain and humiliation. Masoch himself was apparently not amused by the fact that his name became attached to such predilections—probably fair, given that the term was first used in a book entitled Psychopathia Sexualis, which also pioneered negging by speculating that Masoch himself “would have achieved real greatness had he been actuated by normally sexual feelings.” Happily, modern attitudes to the “S” part of BDSM are significantly more enlightened than they were in the 1880s and 1890s. In entirely unrelated news, a YouTuber by the name of icitry—whose bio on the site reads simply “try now, suffer later”—has written a whole first-person shooter in freaking COBOL. If you’ve never had to deal with COBOL, well, good for you, and you should probably keep it that way. The language is amongst the oldest computer languages, and was developed in the 1960s for managing business mainframes. It’s probably what drove poor Ginsberg in Mad Men out of his mind. COBOL remains in use today, largely in such legacy mainframes and other places where it’s not feasible to replace existing systems that, for all their foibles, still work.
One purpose for which it absolutely does not remain in use—and, in fact, has never been used—is programming first-person shooters. So why in the name of all that is good and holy would anyone do this to themselves? [embed]https://www.youtube.com/watch?v=qzpZQe7JT-o[/embed] In his video, icitry explains that the project started with him wondering, “What’s the dumbest but still technically possible language for writing a small FPS style game?” The answer was, yes, COBOL, and because the laws of the universe dictate that anything that can happen must happen, icitry got to work. Long, painstaking, tedious hours of work.
As he points out, COBOL is “old, verbose, missing most features even the shittiest modern languages have … and is definitely not created for game development.” All of this is true, although in fairness to COBOL, it was created at a time when people were still figuring out how programming should work and what a programming language should aim to be. Its earliest standard predated the idea of structured programming, although it soon attracted criticism from advocates of that concept— Edsger Dijkstra, in particular, famously hated the language and said its use “cripples the mind.” To modern eyes, just trying to parse a COBOL program is enough to induce a headache, let alone trying to write a game in it—but, miraculously, icitry manages to get his Wolfenstein 3D-esque project to work. He dodges COBOL’s complete lack of graphical functions by basically treating the game as what he calls a “frame generator”: his code computes the contents of each frame and uses a standard output function to write the results into a simple image format. This is rendered by ffplay—which, yes, is probably cheating, but not even old Leopold would try to write an entire graphics API from scratch in COBOL.
Elsewhere, icitry dodges COBOL’s lack of input management by using the console to input single characters to his game. He doesn’t so much dodge COBOL’s lack of any vector math functions—which are kind of important for a game where the entire gameplay loop revolves around calculating and manipulating 2D movement vectors—as he does just work around them by kinda writing them himself. And then, as if this wasn’t all enough self-punishment, he goes the extra mile by implementing DOOM engine functions like variable ceiling height. The whole project is a testament to mankind’s ingenuity, resourcefulness, and ability to withstand all manner of self-inflicted punishment. Watching the game run, you’d never guess it was written in a language so manifestly unsuited for the task at hand. Still! At least it’s not FORTRAN, right? Right?? *smash cut to an Austrian aristocrat at his desk with a copy of The Fortran Automatic Coding System for the IBM 704 and the DOOM source code* #Masochistic #YouTuber #Punishes #Writing #Person #Shooter #COBOLCOBOL,Doom,Wolfenstein 3D](https://i1.wp.com/gizmodo.com/app/uploads/2026/06/cobol-fps-1280x853.png?ssl=1 "Masochistic YouTuber Punishes Himself by Writing a First Person Shooter Entirely in COBOL
So: masochism. You might know that it takes its name from 19th-century Austrian nobleman and writer Leopold Ritter von Sacher-Masoch—and specifically from the content of his famous work, Venus in Furs, which catalogued the narrator’s submissive nature and fondness for experiencing pain and humiliation. Masoch himself was apparently not amused by the fact that his name became attached to such predilections—probably fair, given that the term was first used in a book entitled Psychopathia Sexualis, which also pioneered negging by speculating that Masoch himself “would have achieved real greatness had he been actuated by normally sexual feelings.” Happily, modern attitudes to the “S” part of BDSM are significantly more enlightened than they were in the 1880s and 1890s. In entirely unrelated news, a YouTuber by the name of icitry—whose bio on the site reads simply “try now, suffer later”—has written a whole first-person shooter in freaking COBOL. If you’ve never had to deal with COBOL, well, good for you, and you should probably keep it that way. The language is amongst the oldest computer languages, and was developed in the 1960s for managing business mainframes. It’s probably what drove poor Ginsberg in Mad Men out of his mind. COBOL remains in use today, largely in such legacy mainframes and other places where it’s not feasible to replace existing systems that, for all their foibles, still work.
One purpose for which it absolutely does not remain in use—and, in fact, has never been used—is programming first-person shooters. So why in the name of all that is good and holy would anyone do this to themselves? [embed]https://www.youtube.com/watch?v=qzpZQe7JT-o[/embed] In his video, icitry explains that the project started with him wondering, “What’s the dumbest but still technically possible language for writing a small FPS style game?” The answer was, yes, COBOL, and because the laws of the universe dictate that anything that can happen must happen, icitry got to work. Long, painstaking, tedious hours of work.
As he points out, COBOL is “old, verbose, missing most features even the shittiest modern languages have … and is definitely not created for game development.” All of this is true, although in fairness to COBOL, it was created at a time when people were still figuring out how programming should work and what a programming language should aim to be. Its earliest standard predated the idea of structured programming, although it soon attracted criticism from advocates of that concept— Edsger Dijkstra, in particular, famously hated the language and said its use “cripples the mind.” To modern eyes, just trying to parse a COBOL program is enough to induce a headache, let alone trying to write a game in it—but, miraculously, icitry manages to get his Wolfenstein 3D-esque project to work. He dodges COBOL’s complete lack of graphical functions by basically treating the game as what he calls a “frame generator”: his code computes the contents of each frame and uses a standard output function to write the results into a simple image format. This is rendered by ffplay—which, yes, is probably cheating, but not even old Leopold would try to write an entire graphics API from scratch in COBOL.
Elsewhere, icitry dodges COBOL’s lack of input management by using the console to input single characters to his game. He doesn’t so much dodge COBOL’s lack of any vector math functions—which are kind of important for a game where the entire gameplay loop revolves around calculating and manipulating 2D movement vectors—as he does just work around them by kinda writing them himself. And then, as if this wasn’t all enough self-punishment, he goes the extra mile by implementing DOOM engine functions like variable ceiling height. The whole project is a testament to mankind’s ingenuity, resourcefulness, and ability to withstand all manner of self-inflicted punishment. Watching the game run, you’d never guess it was written in a language so manifestly unsuited for the task at hand. Still! At least it’s not FORTRAN, right? Right?? *smash cut to an Austrian aristocrat at his desk with a copy of The Fortran Automatic Coding System for the IBM 704 and the DOOM source code* #Masochistic #YouTuber #Punishes #Writing #Person #Shooter #COBOLCOBOL,Doom,Wolfenstein 3D")
![Masochistic YouTuber Punishes Himself by Writing a First Person Shooter Entirely in COBOL
So: masochism. You might know that it takes its name from 19th-century Austrian nobleman and writer Leopold Ritter von Sacher-Masoch—and specifically from the content of his famous work, Venus in Furs, which catalogued the narrator’s submissive nature and fondness for experiencing pain and humiliation. Masoch himself was apparently not amused by the fact that his name became attached to such predilections—probably fair, given that the term was first used in a book entitled Psychopathia Sexualis, which also pioneered negging by speculating that Masoch himself “would have achieved real greatness had he been actuated by normally sexual feelings.” Happily, modern attitudes to the “S” part of BDSM are significantly more enlightened than they were in the 1880s and 1890s. In entirely unrelated news, a YouTuber by the name of icitry—whose bio on the site reads simply “try now, suffer later”—has written a whole first-person shooter in freaking COBOL. If you’ve never had to deal with COBOL, well, good for you, and you should probably keep it that way. The language is amongst the oldest computer languages, and was developed in the 1960s for managing business mainframes. It’s probably what drove poor Ginsberg in Mad Men out of his mind. COBOL remains in use today, largely in such legacy mainframes and other places where it’s not feasible to replace existing systems that, for all their foibles, still work.
One purpose for which it absolutely does not remain in use—and, in fact, has never been used—is programming first-person shooters. So why in the name of all that is good and holy would anyone do this to themselves? [embed]https://www.youtube.com/watch?v=qzpZQe7JT-o[/embed] In his video, icitry explains that the project started with him wondering, “What’s the dumbest but still technically possible language for writing a small FPS style game?” The answer was, yes, COBOL, and because the laws of the universe dictate that anything that can happen must happen, icitry got to work. Long, painstaking, tedious hours of work.
As he points out, COBOL is “old, verbose, missing most features even the shittiest modern languages have … and is definitely not created for game development.” All of this is true, although in fairness to COBOL, it was created at a time when people were still figuring out how programming should work and what a programming language should aim to be. Its earliest standard predated the idea of structured programming, although it soon attracted criticism from advocates of that concept— Edsger Dijkstra, in particular, famously hated the language and said its use “cripples the mind.” To modern eyes, just trying to parse a COBOL program is enough to induce a headache, let alone trying to write a game in it—but, miraculously, icitry manages to get his Wolfenstein 3D-esque project to work. He dodges COBOL’s complete lack of graphical functions by basically treating the game as what he calls a “frame generator”: his code computes the contents of each frame and uses a standard output function to write the results into a simple image format. This is rendered by ffplay—which, yes, is probably cheating, but not even old Leopold would try to write an entire graphics API from scratch in COBOL.
Elsewhere, icitry dodges COBOL’s lack of input management by using the console to input single characters to his game. He doesn’t so much dodge COBOL’s lack of any vector math functions—which are kind of important for a game where the entire gameplay loop revolves around calculating and manipulating 2D movement vectors—as he does just work around them by kinda writing them himself. And then, as if this wasn’t all enough self-punishment, he goes the extra mile by implementing DOOM engine functions like variable ceiling height. The whole project is a testament to mankind’s ingenuity, resourcefulness, and ability to withstand all manner of self-inflicted punishment. Watching the game run, you’d never guess it was written in a language so manifestly unsuited for the task at hand. Still! At least it’s not FORTRAN, right? Right?? *smash cut to an Austrian aristocrat at his desk with a copy of The Fortran Automatic Coding System for the IBM 704 and the DOOM source code* #Masochistic #YouTuber #Punishes #Writing #Person #Shooter #COBOLCOBOL,Doom,Wolfenstein 3D](https://gizmodo.com/app/uploads/2026/06/cobol-fps-1280x853.png "Masochistic YouTuber Punishes Himself by Writing a First Person Shooter Entirely in COBOL
So: masochism. You might know that it takes its name from 19th-century Austrian nobleman and writer Leopold Ritter von Sacher-Masoch—and specifically from the content of his famous work, Venus in Furs, which catalogued the narrator’s submissive nature and fondness for experiencing pain and humiliation. Masoch himself was apparently not amused by the fact that his name became attached to such predilections—probably fair, given that the term was first used in a book entitled Psychopathia Sexualis, which also pioneered negging by speculating that Masoch himself “would have achieved real greatness had he been actuated by normally sexual feelings.” Happily, modern attitudes to the “S” part of BDSM are significantly more enlightened than they were in the 1880s and 1890s. In entirely unrelated news, a YouTuber by the name of icitry—whose bio on the site reads simply “try now, suffer later”—has written a whole first-person shooter in freaking COBOL. If you’ve never had to deal with COBOL, well, good for you, and you should probably keep it that way. The language is amongst the oldest computer languages, and was developed in the 1960s for managing business mainframes. It’s probably what drove poor Ginsberg in Mad Men out of his mind. COBOL remains in use today, largely in such legacy mainframes and other places where it’s not feasible to replace existing systems that, for all their foibles, still work.
One purpose for which it absolutely does not remain in use—and, in fact, has never been used—is programming first-person shooters. So why in the name of all that is good and holy would anyone do this to themselves? [embed]https://www.youtube.com/watch?v=qzpZQe7JT-o[/embed] In his video, icitry explains that the project started with him wondering, “What’s the dumbest but still technically possible language for writing a small FPS style game?” The answer was, yes, COBOL, and because the laws of the universe dictate that anything that can happen must happen, icitry got to work. Long, painstaking, tedious hours of work.
As he points out, COBOL is “old, verbose, missing most features even the shittiest modern languages have … and is definitely not created for game development.” All of this is true, although in fairness to COBOL, it was created at a time when people were still figuring out how programming should work and what a programming language should aim to be. Its earliest standard predated the idea of structured programming, although it soon attracted criticism from advocates of that concept— Edsger Dijkstra, in particular, famously hated the language and said its use “cripples the mind.” To modern eyes, just trying to parse a COBOL program is enough to induce a headache, let alone trying to write a game in it—but, miraculously, icitry manages to get his Wolfenstein 3D-esque project to work. He dodges COBOL’s complete lack of graphical functions by basically treating the game as what he calls a “frame generator”: his code computes the contents of each frame and uses a standard output function to write the results into a simple image format. This is rendered by ffplay—which, yes, is probably cheating, but not even old Leopold would try to write an entire graphics API from scratch in COBOL.
Elsewhere, icitry dodges COBOL’s lack of input management by using the console to input single characters to his game. He doesn’t so much dodge COBOL’s lack of any vector math functions—which are kind of important for a game where the entire gameplay loop revolves around calculating and manipulating 2D movement vectors—as he does just work around them by kinda writing them himself. And then, as if this wasn’t all enough self-punishment, he goes the extra mile by implementing DOOM engine functions like variable ceiling height. The whole project is a testament to mankind’s ingenuity, resourcefulness, and ability to withstand all manner of self-inflicted punishment. Watching the game run, you’d never guess it was written in a language so manifestly unsuited for the task at hand. Still! At least it’s not FORTRAN, right? Right?? *smash cut to an Austrian aristocrat at his desk with a copy of The Fortran Automatic Coding System for the IBM 704 and the DOOM source code* #Masochistic #YouTuber #Punishes #Writing #Person #Shooter #COBOLCOBOL,Doom,Wolfenstein 3D")
Post Comment