No need to look for a conspiracy, this sort of thing happens all the time to all sorts of companies. Maybe it's a patent they want, maybe they want the talent, maybe they want the assets, maybe they want to remove a competitor... It's really not that unusual.
herrvogel
To you, maybe.
That's... a rather huge drawback. Why even pay for a shield at that point?
Manually optimizing the code I wrote in C, so that it runs noticeably slower and has all sorts of stupid bugs that weren't there before. All in a good night's work.
It's more practical though, from a more general UX perspective where the U is often a non technical person. If you throw a "ur browser doesn't support webserial(or whatever)" message up on the screen, you're just gonna confuse tons of users who won't even know what the hell you're talking about. Easier (for everyone) to tell them to just use what you know works.
I don't think it is, honestly.
-
AI sucks at legible text in general. It can certainly do it, but very often the text very clearly does not belong there. You can usually tell it wasn't written or printed there by anyone, it just does not fit very well. This image has very natural looking text in the lower right corner, on that bag thing.
-
AI sucks at consistent reflections in the eye. This dog has a pair of quite consistent reflections in its eyes. You can even see the phone that's taking the photo in its right (our left) eye.
-
AI images are generated from noise. Some of that noise is leftover at the end of the process, especially when you're rendering intricate stuff, like fur. That noise looks blurry, but it looks nothing like blur. I can't see any of that in this image, it all the natural smartphone post-processing and compression feel, mixed with regular ol' blur of being out of focus.
-
AI sucks at consistently aligning lines in the background when they're interrupted by an object in the foreground. Like edges where the wall meets the floor, or edges where walls meet each other. Very often the AI does create a continuous wall behind the object, but the lines will be misaligned. None of that here.
-
AI is also not the best at drawing thin hair-like things that stick out against "open" background, like individual strands of hair or, in this case, whiskers. They often look wrong somehow.
Now none of those things is sufficient evidence by itself because AI can and will occasionally get those right, but together all at once, they make a convincing case that this image is altered at best, but probably not AI generated.
Just look at Michael Jordan. His mother negotiated the everliving crap out of everyone who wanted to be associated with him, and now the dude's still raking in absolutely obscene amounts of money every year without doing absolutely anything at all.
Sql errors: there be a syntax error roughly over there I think. Or maybe it's a semantic error somewhere else I'm not entirely sure. Listen man all I can say is that this one comma there definitely has something to do with it probably, and the error is most certainly either to its left or to its right.
I believe that's how you destroy horcruxes. Saw it in a British documentary once.
No, that's something else. Circular breathing is breathing in through one orifice and out through another at the same time. What that person described is just reversing the direction of your whistling. You still breathe either in or out at once, but sound comes out of your face either way. It's really not hard at all to do.
Dries out your mouth pretty quick though.
Traction is not the only factor. How does this new tire affect steering? How much noise does it make as it rolls on the ground? How much noise does it make as air flows over it at high speed? How durable is it? How does it handle high rotational speeds? How does it handle impact? How does it handle braking? How does it handle different weather and road conditions, different temperatures? How does it treat the road surface? And can it be manufactured at such huge scales? There are plenty of reasons why it might very well be completely unsuitable as car tires.
Have they given an explanation as to why that is? I mean why make it a fatal error that prevents compilation, when you could make it a warning and have the compiler simply skip it?