>AI billing audit startup Vaudit reviewed $34 million in AI invoices submitted by 60 enterprise customers and found approximately $1.7 million in mistaken overcharges — a billing error rate of roughly five percent.
I currently have a problem with Rust that I use Rust-Analyzer for syntax and autocomplete in VS Code and it has to run the compiler when you save a file to "refresh" things.
As you may imagine, this is insanely slow.
So slow that when I switch from a .rs file to a .ts file I feel like I switched computers.
Not even, this was deemed too insecure. So now we have to have one protocol per-use case instead of something that allows to handle easily all the use cases we already know exist - the most stupid thing possible
I may be wrong but I think the word you want is anthropocentric, not anthropomorphic. Anthropomorphism is turning something that isn't human into something human, e.g. an AI, while anthropocentrism is taking human as the center and default state of things.
If you have an issue with an open source software, you need to register on a website that is made for developers, that will try to sell you a git hosting service, write a bug following a technical format, and you are expected to given information in a reproducible way.
If you have an issue with a closed source freeware, you just use a contact form on their website or leave a comment on their blog or whatever.
The amount of friction to report a bug that FLOSS puts on users is absolutely insane. It's almost like it's trying to deny anyone who isn't a technical person from reporting problems they are having.
GitHub is meant for developers. Plenty of OSS has forums or Zulip/Discord chats for ordinary users to get support in a more casual way. Sometimes not, but there's just as much closed source software with poor support too.
How is 1 + 1 = 2 hard to test?
Vibe coded implementation paired with vibe coded tests made to fit the implementation?