Corporate America Is Starting to Ration AI as Cost Skyrockets
wsj.com
wsj.com
And I'm seeing almost no self-awareness from leaders. They are making decisions about things that they just don't understand. And are completely unworried about it. Just blindly following whatever the news cycle is about AI.
How much that makes it into enterprise pricing is TBD, since none of the hyper scalers are making money yet of selling AI inference.
Almost all businesses are ahead of the gun. For most of their use cases, AI is either not yet good enough on its own, or good enough but too expensive.
No one wants to get left behind, so everyone's trying to get onto it now, even though it's not ready for what most enterprises want to do with it.
It's easy for them to look at a small startup without billions of lines of legacy business logic debt and see them having success and wonder why they can't have just as much - or more - why they're bigger so they should have better and more success, right???
Wrong...
But when it gets ~99% cheaper for local inference over the next 4 years, at the same time the price per watt improve 4x -> a lot of those cases will start to pencil out.
Historic trends, every 18 months, performance for the same level of quality has gone down 90%.
See: https://www.reddit.com/r/LocalLLaMA/comments/1gpr2p4/llms_co...
And Chart 13 here: https://www.rdworldonline.com/ais-great-compression-20-chart...
And here: https://epoch.ai/data-insights/llm-inference-price-trends
Historically, algorithmic gains are only ~30% of the pie, but there's enough out there to get to 10x, with just what's available already. The other ~70% of the pie is better training data (often synthetic) and distilling frontier knowledge. There's no sign we are tapped out on that front.
Additionally, GRAM (from ~10 days ago) is likely to be a 5-10x on its own (if not substantially more for smaller models). It's unlikely within 4 years LeCun's JEPA ideas and similar ideas like GRAM applied to LLMs have ZERO impact. The preliminary results are absolutely astounding (5000x better reasoning - this is not peanuts).
Further, that's not even counting that cost per watt is still dropping ~2x every 2 years on its own on the hardware front.
If you look at the "cost" of inference. People think it's electricity - but it's currently almost ~80% hardware amortization. The memory shortage is not going to last, nor are Nvidia's ~80-90% margins.
The human brain is still 8-10 orders of magnitude more efficient than the best LLMs of today. With ~1/10th of global capex riding on AI, if you don't think they're going to knock of 2 orders of magnitude more, when it's this obvious and easy... I don't know what to tell you...
Sure, it might take 6 years instead of 4. My crystal ball isn't perfect.
See https://arxiv.org/abs/2604.04364.
This won't really show up in benchmarks, but it will impact real world usage on the most common use cases.
I'm doing a study right now on the impacts of better context for small models to fix bugs.
A very dumb algorithm can make small models perform at 10x+ model sizes. I'll be surprised if it can't get to 20x+
Thank you for sharing this and for having the intellectual courage to hold to a sound reasoning that may be unpopular initially.
I think what will also happen, once we get past this current CEO AI FOMO mania, is that companies will start to look at AI spending more rationally like any other company expense, and will revert to more rational decision making.
Even if the cost comes down considerably over the next few years, that's plenty of time for companies to look at their financial results and question why AI expenditure isn't resulting in increase in revenue and/or profitability.
Do you mean the marginal cost by the producer, or the cost on the consumer? I can't see the price of electricity falling much, and the demand curve is apparently exponential if the hype is to be believed.
Computing has always been about how to wring out more efficiency. The ENIAC was 150,000 watts, with 3 phase 240 volt power, and cost about $500,000.
My day to day laptop (a year old) is 35 watts, with 1 phase 20 volt power, and cost $1,000, so that's 99.98% less power consumption, 99.8% cheaper, and it has about 10 orders of magnitude more computing power, all on a time span of 80 years.
There's always a chance we'll have some dramatic gains far larger than DeepSeek's optimizations a year ago, but it hasn't happened again yet at even that scale. It would be nice but I certainly wouldn't count on it.
People are willing to pay more for BETTER quality.
You obviously haven't seen DeepSeek v4 Pro's pricing if you think pricing only goes up...
Let's look at GPU prices as an example. Around 12 years ago, I bought a GTX 970 for around $350. That was considered a very good GPU at the time. Today, the "equivalent" GPU model (RTX 5070) now costs almost double. Of course, the newer GPU is much more powerful (more than double, in fact), but all the things you'd use a GPU for have also advanced and now expect an entirely new level of performance as a baseline, such that the older GPU is fairly worthless today. So most people agree that GPUs in general have become more expensive.
Regarding DeepSeek's price: it's obviously subsidized, and unlikely to match the actual inference cost right now.
Then buy $10 (or $2, if you're cheap, and they take PayPal) of DeepSeek credits.
Whilst you're at it spring for a Claude subscription too and GPT.
Switch models between Qwen, DeepSeek Flash, DeepSeek Pro, and you can meet 99% of your code generation needs.
Hop over to Opus 4.7 (or 4.8, but I haven't really used it yet) and GPT-5.5 when doing very complex architecture/design or troubleshooting something where DeepSeek Pro is getting stuck.
It is ridiculous how cheap this stuff is now. It's affordable at third world prices.
> spring for a Claude subscription too and GPT.
You started with some random pricing then veered off into impractical hand waving. Far above third world prices...unless you count the USA as third world, I guess.
If you have the $$, do the extra stuff. People who like to play video games often have a very fancy graphics card that sits idle during their work day.
And the technology already exists on the algorithmic front TODAY to lock in another 10x gain -> when, typically, algorithmic gains only account for ~30% of that drop and the other ~70% comes from better data (often synthetic) and knowledge distilation from frontier models.
Just look at DeepSeek's pricing...
The Chinese, since they lack computing hardware due to US export controls, are.
So I just started trying CodeWhale (https://github.com/Hmbown/CodeWhale) with DeepSeek V4. I expected to be impressed by the abilities (which still require plenty of oversight). I didn't expect to be completely shocked by how cheep it is. After most of a week of using it 4-8 hours a day, which would amount to a full week of coding in many jobs after you account for non-coding activities, I'm about to hit $3 in total usage. So we're talking $10-20 per month for single-agent use by a full time software developer? And I'm sure some of my usage is waste as I'm still getting my head around things like compaction. If I take a break for a few weeks, I pay nothing because there is no subscription.
If DeepSeek and Xiaomi MiMo stay within a few months of the US-based models in terms of capabilities and US companies don't figure out how to drastically cut prices, I can't see how China hasn't already won. Protectionism would be one reason, but that might be ceding 50-90% of the total addressable market, and bring us closer to moving knowledge work out of the US the same way we did with manufacturing because it's too expensive in the US.
The first big task was to find the common bits and abstract them out. It did a great job of creating a plan, summarized in a table, that gave a name to shared chunks, the line numbers in various files where they appeared, line counts of new functions vs. removed bits, and some pros/cons about splitting out each chunk. It was very well "thought out", so I told it to go ahead. It did a nice job other than straying from my coding conventions. That gave me a chance to build out my AGENTS.md file (it helped with that, too).
Once that was done, I had it create automated tests for the newly abstracted parts. I think this is probably a bad practice... I believe humans should at least define what the tests are testing so that there is a deeper understanding of what oversight is in place. But I was just trying things. It surprised me how well it did. The biggest surprise was that the tests seemed quite inspired by vision. It would try different parameters and then have comments about making sure the shape protruded in a certain way, then code that did that. I expected it to refactor a bunch of the code to make it more testable. It found a way to not touch the code while testing everything I asked it to with just two simple mocks - I hadn't foreseen that, but it felt quite practical. It was passing around several opaque tuples in the tests and accessing items in them by index. I prompted it to replace the first one with a frozen, kw-only dataclass. Then a second. On the second request, it saw the pattern and did the rest without me asking. It created 44 tests across a handful of files.
The next part is where I was the least happy. I use ruff and ty to check my code with almost all checks enabled. It was mostly good about the ruff issues. But for the type checking, it just wanted to disable 6-8 rules for the entire repo in pyproject.toml, or at least for all the tests. I had to repeatedly tell it not to and it kept telling me it wasn't recommended. When it finally gave in, it fixed most of the type issues (build123d has lots of types specified, but many operations result in type conflicts because things are so deeply overloaded). The things it didn't fix, it just left a comment to ignore type checking altogether on that line. After I did a little more brow beating, it finally changed the comments to only disable specific rules. To be fair, and unlike most of my other repos, I've had to spend way too much time getting types right in this repo myself.
My last task involved a small library management system for our little town library (tracking library cards, books, DVDs, check-outs/check-ins, etc.). I inherited it from someone who had built the entire web app out of bash/awk/troff scripts with the data in text files burdened by a lot of schema changes that he didn't really know how to deal with. I'm halfway through moving it to Python/FastAPI/SQLite. I asked it to do a security audit of the entire code base, both the newer parts and the old parts that are still in bash/awk/troff. It found everything I knew about and a few things I didn't know about. It made a decent assessment of the risks/impact of each issue. It also called out design decisions that were good security practices. One of the next big tasks will be to see how it does at continuing the migration - it has enough examples of how I've done it that I suspect it can do something fairly consistent with my thinking. I'll probably have it do one or two web pages. When I feel like it understands what I'm after, I'll tell it to use sub-agents to do the rest. I'll be very happy if I don't have to tease apart any more troff scripts that are generating PDF files!
I doubt it is really any different to what the US labs do [1]. I never really bought the "they were basically all just distilling from us" shtick from Anthropic, I just assumed they were either comparing or also creating training data as basically any lab is doing.
[1]: https://www.reddit.com/r/ClaudeCode/comments/1tqaist/opus_48...
And fusion power is just 2 decades into the future!
We have little visibility into current frontier model costs at mass scale. As a broad historical trend, tech costs tend to fall over longer time periods but your claim far exceeds Moore's Law rates in its heyday - and that heyday is long gone.
In 2021 TSMC announced it was increasing it's price per gate for new nodes for the first time in its history. In the past five years cutting edge nodes have delivered ~8-15% real-world performance gains on average at costs at least 10-20% more than the last node. If you're positing a string of unprecedented efficiency breakthroughs in LLM algorithms - such extraordinary claims require extraordinary evidence.
As I was saying, you're all fired.
I predict that will be their comeuppance; it will begin a new era in history.
As a leader, pushing for rapid change cannot really be nuanced lest the push dissipates into the organization's entropy.
It's irrational to push for tokenmaxxing (literally "please increase our AI spending") and not expect that this is the result you are going to get. You won't get productivity increase, since that is not what you are pushing for - you will get token usage maximization (engineers running inane agentic tasks against your code base to increase usage, using company paid AI for their side projects, etc, etc).
Perhaps that is what they were trying to do, but the reality is that all they will have got is a large token bill. The decision makers may have hoped that tokens would be used in most productive fashion possible so they could evaluate if the cost was worth it, but what they will have actually got is what they asked for and measured, high token usage (applied to whatever people needed to do to get their usage stats up, regardless of productivity).
The other business-as-usual factor is that there will be false reporting up the chain, so if the company understands the CEO want to see high AI usage and productivity gains, then s/he will see high AI usage (a large token bill) and will be fed success reports of corresponding productivity gains.
In a typical corporate environment, if all your peers are reporting success, achieving what the CEO wants, do you want to be the only one reporting failure? So - everyone reports high AI usage (easy for the employees to make happen), and most everyone also reports productivity gains if they understand this is the expectation.
If you want to report productivity gains or cost savings from some initiative (increased AI usage or whatever) and need some stats to point to, then you just point to whatever is working, for whatever reason, and attribute the success to the new initiative.
In a company I used to work for, one manager, when pushed to increase machine learning usage (a few years back, before ML became AI), just renamed his product from foo to foo-ML (with ZERO ML usage), and reported how well it is working. He has since been promoted twice.
Do these measurements have sufficient information? As much as any, I'd guess. It sounds like you already know that it's pretty hard in general to measure the productive output of software development organizations.
Why be a normal guy that waits to see what happens and is measured and pragmatic when you can get attention basically through the whole cycle by being the earliest adopter, adopt it to the maxx, then also be the loudest big brain when the tide changes and be praised for "taking hard decisions" when you revert everything you said so far?
The fakemaxxing economy.
Understanding this was one of the most important things in my career.
It would only be laughable if they waited way too long to reverse course, but I don't think that's the case.
Over/undershoots and corrections are of course unavoidable and normal; the absurdity is at the magnitude and rate of change. Furthermore, this is giving it the benefit of the doubt, that measuring AI spend is a good indicator; that's arguably also in dispute. To stretch my car analogy a bit more: it would be like the cruse control system has to hit the target speed, but it only has data from the O2 sensors.
[0] I know that the "classic" cruise control system cannot apply the brakes, but hey no analogy's perfect.
What he says he's consistently hearing from them mirrors what I saw at my own employer: they thought they had ROI metrics, but they actually only had usage metrics such as "lines of code committed" or "number of pull requests". The only way those could possibly work as an ROI measure is if your business charges customers by the line of code.
Eventually I got tired of it and got back to work.
Which reflects another thing I’ve seen at work. A lot of what AI coding has enabled is diving headfirst into quagmires. Our costs have spiked - not just because of the token spend, also because we gotta pay the cloud platform to run all these new services, operators to operate them, marketers to market them, etc. - but revenue hasn’t budged.
Don’t play their game and call them leaders. They are management, bosses, executives.
> They are making decisions about things that they just don't understand. And are completely unworried about it.
Clowns, even.
> Just blindly following whatever the news cycle is about AI.
But followers might be most apt.
——
This is such a huge pet peeve of mine. Describing management goofs using their language that makes them sound all-so-brilliant. We constantly watch these people do the dumbest shit and then they go around describing themselves as “thought leaders” and “servant leaders”. When, really, most are just clowns with fragile egos.
And, while I’m rambling, they’ve tried to take away the fact we are workers by calling us individual contributors. Using language to attempt and hide the hierarchy and power dynamic at play. It just…bothers me so much.
And many of them still claim they are "risk takers", but have effectively insulated themselves from risk by socializing losses.
You're falling into a common trap here: the ambiguity of the English language.
"Leader" means multiple different things. Yes, it means someone who has leadership qualities—who genuinely inspires those around them to do better, or who boldly marches into the unknown and gets people to follow them.
But it also means "someone in charge of a thing."
Now it's certainly true that many people in charge of things who are also really bad at actually inspiring or getting people to follow them (aside from with threats of destitution) also play on that ambiguity to try to convince people that because they're in charge of things, they must also be Good Leaders, and that's crappy...but yelling at others for using the term casually is very much an "old man yells at cloud" situation.
I once worked in a company that had soviet-level efforts to push LLMs into everything, someone eventually made the classic "Natural Language -> SQL Query -> Magic Result in webpage" and got promoted, the tool got mandated for every non-tech employee as part of an AI-boosting effort (people pushing metrics up).
One day I wake up with a product person in despair because the tool couldn't handle what looked like a very simple aggregation, I stopped what I was doing, crafted a 30-line SQL query over HORRIBLE TABLES, a couple CTEs and window functions here and there got him what he wanted. I found out later that single query that took 30 minutes to make saved him from inheriting a 6-month effort to create a microservice dedicated to patching said tool.
If it was so good I would expect to see 2005-2015 advancements yearly.
Meanwhile China is blowing past the world with real improvements in the real world- solar, EVs, etc. meanwhile people keep making their fancy sans serif websites about todo apps, faster than ever before. Useless.
I don’t disagree that AI is overhyped. But I think you are probably looking in the wrong place.
I think most software that is written isn’t really a product, at least not a public product. It’s an in-house tool or a one-off project needed to complete some larger task. People everywhere are always writing small programs that make their life or job just a bit easier (and explains why so many corporate projects are little more than an excel spreadsheet).
And there are a lot of people who have made custom software just for themselves with AI. Not a product, just a tool or project that finally made sense to build.
After 1T in spend, it's still not clear that AIs will beat out a $30k secretary.
Also, your link has nothing to do with computers.
The link talks directly about the disconnect between the supposed productivity benefits of a technology and the measured productivity benefits of it in practice. And provides historical context about why the “obvious” benefits of a computer did not materialize when it was introduced; business and their processes had to be rebuilt around the computer before real gains were seen.
It's a structural deficiency in the way they work that can't just be handwaived away.
There are new architectures, paper, and harnesses coming out weekly that improve performance, accuracy, and/or performance efficiency.
Whether they can do better or not than a secretary is a poorly defined metric. But by objective metric they are already producing less buggy code than $30k developers, and doing it faster.
But by objective metric they are already producing less buggy code than $30k developers, and doing it faster.
That's like bragging that a $1 trillion tank can go faster than a cheap budget car. For $1 trillion being slightly better isn't good enough.
If you consider the change in what’s possible in June 2026 vs 2025 (to say nothing of 2024) “incremental” than you and I are living in different realities and I don’t know what to tell you.
The perennial reality is that automation is inherently inflexible, so there's only so much of it that you can do before you've committed a huge strategic blunder by making your business resistant to change and severely curtailing its ability to cope with situations that don't cleanly fit the mold. So then we need to hack in ways to deal with the exceptions, but, since they're hacked in, they're often painful and time consuming. Sometimes so much so that after the new process stabilizes it turns out to be even more cumbersome and require more manual effort than the system it replaced.
When anyone other than a technologist suggests doing that kind of thing, we call it "bureaucracy", and we hate it. I think maybe what we have trouble seeing is that there's actually a pretty fundamental difference between automating purely technical processes like server deployment, and automating processes that are fundamentally about mediating human interactions.
It doesn't have to and I'm pretty sure it won't.
I would agree that a lot of companies talking a big talk about using LLMs are failing to actually apply it in a sensible way to their business.
What changes have LLMs (Not AI, not machine learning in general, I'm not going to waste time discussing the definition), LLMs made in the past 4 years that indicate anything close to the above? Solving a whiteboard math problem?
Very little about the American economy even makes sense for keeping the edge on LLMs beyond a few years. All the things I would think would be required: energy, research, construction capacity, labor costs -- it's pretty hard to deny who's on the upswing these days. China cranking out current generation microchips will be the last nail in the coffin.
For example. Imagine that you are comparing two documents (let's assume diff doesn't exist). You could ask an AI to compare the differences from you or you could use AI to write a tool to do it. For whatever reason, people are starting to go with the former not realizing that now they basically have to pay to compare documents.
It just requires being willing to think instead of mashing prompts into a keyboard.
I understand and agree with your point though.
In practice, I've found the answer seems to be "not much", because human triage is still required to understand whether the insight is correct and useful. But I'm not sure that was obvious in retrospect.
My answer: no, but it was able to help me find the website and social handles for every beat writer for every team, and generate a simple website where I can do a daily skim of teams/players and draw my own conclusions.
LLMs are a tool, not a panacea.
Normal people have never gone around automating their work. The most automation they do is dynamic tables on excel sheets.
I obviously know building a tool that can programmatically do something is a better solution, but I think that requires a fundamental shift in how people work. People need to be told by someone "this is how you should be using the AI" but right now they're simple told "use the AI".
With this AI is a fallback and not the default. Sounds like large companies have it backwards.
This is why we have business analysts and software developers.
To help identify inefficiencies and to build technical solutions.
We are very close to the point where if Claude and ChatGPT APIs are down, companies cannot function. How is that introduced so quickly into so many critical places without taking that specific fact in consideration? What is the plan for all those companies whose workflows now depend heavily on a remote LLM whenever the services get cut? What if your company account gets banned?
In some ways it is worth than depending on a company for hosting, because even your debugging tools are based on AI. MCP is great to go through datadog, sentry, until your agent or the MCP server are down and you don't know how to look for the issue yourself because you do not actually understand how your systems work.
Contrast with Gmail/Gsuite/Outlook365/QuickbooksOnline/etc are down, though.
What you cite here isn't a direct attack on AI but on centralized service provision in general. Unfortunately that battle has been lost for decades, now.
Here we have the opposite: In the land of the one-eyed, the blind are leading.
The blind in this case are all those executives and managers who don't understand much about AI's current potential and limitations, and so far have treated it like a magic button that will solve everything. The one-eyed are rank-and-file employees who maybe sort of know a little more about AI.
Personally I'd consider efficient and economical use of AI to be a key skill for a good developer. Using AI for everything at full throttle would appear to be a crutch. I wonder if this will eventually become a hiring criteria for companies without unlimited budgets (most of them).
A lot of companies went from “use as much AI as possible” to suddenly realizing that not every call needs frontier-model intelligence. In production, many calls are just repeated classification, tagging, routing, extraction, etc.
The interesting problem is not banning usage. It is figuring out which parts of the traffic are safe to handle cheaply, and which parts should still go to the expensive model.
Between corporate FOMO and the rapidly decreasing costs of actually running LLM's I'm interested to see at which side of the spectrum these two meet
In other words, the news cycle is looking for an AI story that lands with readers, and that the example of Uber blowing through its AI budget and Microsoft discontinuing use of Claude internally are not good indicators.
I agree that those aren’t good indicators.
However, at some point we have to remember that CEOs and boards of directors are just regular morons who read the news the same way everyone else does.
At some point, if a lot of corporate leaders associate AI with mediocre results, high costs, and public backlash, they might just start saying “this juice isn’t worth the squeeze.”
Like a few other commenters, other than reasonably making a software developers work easier I haven’t seen a lot of value creation or revenue boost from AI. I know AI companies make money, but the companies consuming these services, are they meaningfully making a revenue to justify the continued spend?
Only thing I can say AI was useful for, in a corporate environment, was learning a new coding language on the fly. Gives me a baseline to work off of and fix.
But I can learn without it, too. A nice tool, but not a need.
An ironic analogy sort of, once media started hiding behind a paywall, I just stopped reading them rather than paying. Same with LLMs - usable if cheap/free.
90%+ of corporate people are not programmers. 1 programmers can cause the same token damage with a bunch of concurrent agents as a couple thousand Karens in compliance asking a chatbot questions
It's much easier to deliver incremental AI ROI on the later even if it's hard to measure/quantify. A 1000 tokens might point this compliance person in the right direction on a key problem. Meanwhile 1000 tokens doesn't get you anything useful on coding
If LLMs are genuinely helpful or even decisive in a military engagement, you can expect any host country to commandeer whatever data centers they need, leaving commercial entities to bid up the prices on the leftover capacity.
Another risk is that data centers are a great target for cyber warfare.
It’s ideal if your business can leverage LLMs when they’re online but continue to operate profitably when they’re offline.
- ChatGPT drops, AI is perfect to be our savior.
- AI glorified as the great messiah.
- Everyone worships stocks even remotely related to AI.
- Execs desperate for relevance boast about tokenmaxxing.
- SHTF
- burst
- last year flagship GPUs and DRAM are sold used for the price of a burger.
- Laidoff people start using local AI as hardware price drops to make actual useful stuff
- New round of bootstrapped tech bros that eventually give birth to the new metaverse/NFT/etc.. hype.
I asked codex to take a look, and it:
- Grabbed the CI logs on its own to figure out what the CI error was
- Looked at my local setup
- Looked at the changes in sqlx from 0.8 to 0.9
And figured out that sqlx depends on an updated version of the “whoami” crate but doesn’t specify default features, which causes it to fall back on a stub implementation that makes the default user “anonymous”, which was failing to authenticate to the UNIX socket we use in our CI Postgres server. It patched the environment variable for our docker container to explicitly specify a username and the issue was fixed.
It would’ve taken me probably several hours to figure this out on my own. It took codex maybe 5 minutes.
Tell me again how LLM’s “don’t work”?
I'm not taking a shot, to be clear, we had a similar issue a few years ago and we made sure this wouldn't happen again, that's absolutely not a shot, nor do I think it's a character flaw to use AI, au contraire, this is a very good use. I'm just worried that because AI is so good at fixing minor issues caused by governance/organisation flaws, we will be stuck using it to fix those and be trapped in mediocrity (that's not an issue for me, mediocrity is where I work best, but I'm a bit sad for the great Devs I've worked with.)
It’s not in the changelog though, this is an update of a transitive dependency that inadvertently changed the default behavior. sqlx didn’t document this because they didn’t even know it changed.
Even if it was a documented change, our process caught it because it was caught by CI. The issue itself was only a result of how our CI was configured (we had a database url with a domain socket path that didn’t explicitly specify a username, and we inadvertently relied on the default of “the current user”, which the whoami crate now defaults to “anonymous”.) I don’t see an issue in our “team process” (whatever that means) at all.
A bug in a dependency means I’m not familiar with the tools I’m using? What exactly should I have had a priori knowledge of that would have solved this? That the whoami crate, which I don’t use, but was a transitive dependency, changed a default which affected the sqlx crate in a way that they didn’t know about either, in a way that produced an error that only happened in the CI environment and not locally? And I should have known this how exactly?
I hate what AI is doing to our industry and I hate the constant deluge of slop I have to review every day. I’m not an AI lover by any means. But Jesus Christ why do people bend over in any direction imaginable to pretend that reality isn’t reality (LLM’s must be useless because I personally don’t like them) and blame someone 3 levels away from a problem just to make themselves feel better.
But sure, no, it must be me “not knowing my tools enough” because I’m not aware of bugs in other projects that their maintainers themselves are not aware of. Because the alternative is that AI might actually be useful in some way, and we can’t admit that, can we?
Not being aware of the limitations of the tools you're using is a hallmark of junior-level programmers. That's why experience matters; if it was just about raw coding talent nobody would care about experience. But making mistakes like this is supposed to be how you learn.
Unless of course you turn over the learning to the AI, as you did here. Otherwise you would have known that the defaults you're complaining about are clearly identified in the README files you didn't read.
None of what you’re saying about my scenario is true at all. You’re hallucinating shit worse than LLM’s. There was no README that outlined the behavior. There was no change log entry. The sqlx crate did not document a single thing related to this at all. You’re missing critical information and making enormous assumptions, and jumping to attacking my character as the very first step.
Maybe you googled just enough about the sqlx and whoami crates to come to a wrong conclusion. Because there was a changelog entry related to whoami in the sqlx release notes. And yes I read it. But guess what: that wasn’t the issue. The issue is a legitimate bug in sqlx related to how they use the whoami crate. There’s no clearly identified README entry. There’s just a sqlx bug in 0.9.
I’d explain in detail exactly what the bug is but you’re not interested because you’ve already made your conclusion about me before you have any information about what happened. (Hint: the whoami crate decided to move the functionality that actually grabs your username behind the `std` crate feature, and made the std feature enabled by default. But the sqlx crate has always included whoami with `default_features = false`. I’ll leave you to guess what happened as a result. Before you answer, you should also learn how cargo treats crate features in a build where the whoami crate is linked multiple times with different features. Once you think you have it figured out, go and find this README entry I should have read.)
Edit: actually, fuck it, I’m sick of being coy. Here’s the sqlx regression: https://github.com/transact-rs/sqlx/pull/4275
Note how it’s still open as of this writing.
Note how it’s not “clearly stated in the README”. It’s a bug. A bug that’s still not fixed.