this post was submitted on 31 Jul 2025
518 points (98.7% liked)
Not The Onion
17487 readers
2118 users here now
Welcome
We're not The Onion! Not affiliated with them in any way! Not operated by them in any way! All the news here is real!
The Rules
Posts must be:
- Links to news stories from...
- ...credible sources, with...
- ...their original headlines, that...
- ...would make people who see the headline think, “That has got to be a story from The Onion, America’s Finest News Source.”
Please also avoid duplicates.
Comments and post content must abide by the server rules for Lemmy.world and generally abstain from trollish, bigoted, or otherwise disruptive behavior that makes this community less fun for everyone.
And that’s basically it!
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
They have a lot of wiggle room in pricing software when it's eliminating whole ass people. The software is competing with a floor of 30-40k/yr
Only if it actually can do their job, which is... Doubtful
You need to double employee pay to focus on this. If a person takes home $30K gross, the employer's likely paying double that.
Your pay is not what the employer pays for your labor. At the low end of the pay scale, it's closer to double. Worker's comp insurance, unemployment taxes, HR costs, shitloads of things add up. With AI, they're gambling on deleting all that overhead.
Fair point!
Yes, and as we've seen time and time again, companies are totally cool when operating costs suddenly revert back to what they were years ago.
Yeah. And AWS was supposed to replace on-prem hosting. Except, now, they represent a higher opex cost than even payroll.
I see no reason why OpenAI isn't just charging peanuts for service to build a gigantic user base who can't think without it, then jacking the price up to whatever they want — and I can assure you, if Sam Altman has the option to become an immortal trillionaire, he will take it.
That's usually because the on-prem equiment was hidden somewhere in capex, not opex.
There are a lot of cases I've been involved with where AWS comes out way cheaper than an on-prem solution, once you take all the costs into consideration. But there are plenty of other cases where it has turned out to be more costly, especially if some bonehead attemted a "like-for-like" migration with no effort to minimize AWS service costs. Take every on-prem VM and stand up a corresponding EC2? Replicate the same rat's next of connectivity that's in the legacy system? That'll probably cost you.