I expect if you follow the references you'd find one of them to be one of those "if Earth was a grain of sand" analogies.
People like laughing at AI but usually these silly-sounding answers accurately reflect the information the search returned.
I expect if you follow the references you'd find one of them to be one of those "if Earth was a grain of sand" analogies.
People like laughing at AI but usually these silly-sounding answers accurately reflect the information the search returned.
My understanding is that webp isn't actually all that bad from a technical perspective, it was just annoying because it started getting used widely on the web before all the various tools caught up and implemented support for it.
Replacing people with AI creates a situation where the incentive for people to make original works is greatly diminished,
Why would that be? It should be tye opposite, making VO cheaper means studios can take risks and get experimental. Basically what cheap engines have done for indie development.
Bitcoin is over 15 years old now, that's not a particularly fast speedrun.
It's a specific type of thing, but it's not a brand. Nobody owns the trademark for Bitcoin. Anyone can buy, sell, or mine Bitcoin. It's no more a specific product than dollars are a specific product.
If they added a Bitcoin logo, then you'd see every other crypto lining up to get their logos permanently installed on every person's devices, too.
Is there a problem with that? This isn't "advertising", these are unicode symbols. There are unicode symbols for all kinds of things. Every currency has unicode symbols, why not cryptocurrencies?
What could go wrong with using human programmers to convert it?
If you're going to insist on perfection for something like this then you're probably never going to get anything done. Convert the program and then test and debug it just like you'd do with any newly written code. The idea is to make it easier to do that, not to make it so you don't have to do it at all.
I would expect that's part of the point, if a C program can't be converted to a language that doesn't allow memory violations that probably indicates that there are execution pathways that result in memory violations.
It probably doesn't matter from a popular perception standpoint. The talking point that AI burns massive amounts of coal for each deepfake generated is now deeply ingrained, it'll be brought up regularly for years after it's no longer true.
If someone wants to pay me to upvote them I'm open to negotiation.
A lot of people are keen to hear that AI is bad, though, so the clicks go through on articles like this anyway.
Except it is capable of meaningfully doing so, just not in 100% of every conceivable situation. And those rare flubs are the ones that get spread around and laughed at, such as this example.
There's a nice phrase I commonly use, "don't let the perfect be the enemy of the good." These AIs are good enough at this point that I find them to be very useful. Not perfect, of course, but they don't have to be as long as you're prepared for those occasions, like this one, where they give a wrong result. Like any tool you have some responsibility to know how to use it and what its capabilities are.