It definitely would not be, regardless of whatever "done correctly" means. Solar noon at exactly 12:00 is only going to happen on a single line of longitude. If you have a timezone centered on that line and exactly 15° (one hour) wide then solar noon will be up to 30 minutes away from 12:00 depending on your east/west position in that timezone.
It was exactly this realization that the numbers were arbitrary and 12:00 didn't need to be solar noon that led to the creation of timezones in the first place, so that it's not 4:14 in Norwich while it's 3:52 in Birmingham and just travelling from city to city doesn't mean you're changing your watch constantly and it becomes actually possible to write a sensible rail schedule.
Timezones are already a step toward an arbitrary standard time for the purposes of making communication easier and not needing to change your watch just because you moved around. UTC everywhere would just be another larger step in that already established direction.
I don't see how dealing with that is any worse than dealing with time zones.
Downside of UTC everywhere: you might have to set your alarm for a different time when you travel.
Upsides: Never need to account for timezones in communication. Never need to change a clock, ever.
They make sense because the numbers won't be arbitrary.
But they are. There's no changing that. They're arbitrary now. They'd be arbitrary if we had UTC everywhere. We're not out here using sundials to set our clocks, 12:00 is not solar noon more often than it is.
Or we'll realize that the specific numbers are arbitrary and use UTC everywhere.
What is so bad about virtual environments?
They're a solution to a self-inflicted problem. They're only "really nice and useful" if you accept that having your projects stomp all over each others' libraries and environments is normal.
If projects were self-contained from the outset then you wouldn't need an additional tool to make them so.
I know someone who has a company with the word "technology" in the name, like "Smith Technology". They use .technology because it's literally the name of the company, which I think is good for the brand identity, but have run into issues where people just don't think it's a correct url because "smith.technology" looks like it's missing its TLD.
Fridges actually do rest. They cycle on and off as needed to maintain their desired temperature and on average only spend about 30% to 40% of their time "on".
Also, this is tangential to the rest of our conversation, but I appreciate the dedication to the comment chain required to actually set up something with similar composition to the red man image and take a picture of it. Even has some black in the image in roughly the same size and area as his sweater. :D
For what it's worth I agree that AI images will generally have "tells" that give away their nature. It's just they aren't quite so straightforward as being able to check that average values are within a range. It would be nice if it were that easy though.
While I do dabble with AI image generation I'm not a lunatic who calls themself an "artist" for doing so, nor do I think being a "prompt engineer" is any kind of expression of creativity or skill. I think the people who do are completely self-deluded.
Odd. I tag your red at 78%. And for what it's worth this RGB to HSV converter agrees with that number taking your colour hex as C92D20. I certainly don't know enough about it to offer an explanation as to why it might be different.
edit: Ah, I think it's HSV vs HSL, which I'm just now learning are different things. :D
I'm not sure what you mean by the saturation being around 50% across the board. If I peek the HSB of all of the averages only that first teal-ish one appears to be around the mid point for saturation.
I'd expect that many images are going to be somewhere near 50% grey if you average their luminance out overall. That's just the average of every colour though. The fact that averaging a range of things tends toward a standard distribution isn't particularly surprising. Again though, it's not hard to get a diffusion model to generate something outside of that expectation.
Prompt: "night sky"
Image:
Average colour:
Average brightness: 21%
Prompt: "lineless image of an old man drawn in yellow ink on white background"
Image:
Average colour:
Average brightness: 90%
I'm saying it because it's not only obvious with even a moments thought (you can literally just ask it for an entirely red image or whatever), but also because it's easily provable.
Prompt: "Under the sea"
Image:
Average pixel colour:
Prompt: "a man with red hair wearing a red coat standing in front of a red background"
Image:
Average pixel colour:
So I ask you the same question. Did you just say that because you felt like it was true?
It is absolutely not true of all AI images. I'd be surprised if it's even true about most AI images.
Regardless of whether the gaming market itself is growing or not you can still compare to Nvidia to see how AMD is doing within that environment. If no one was buying any GPUs Nvidia would also be showing a dip, but they're not.
Anyone? There are lots of houses worth less than $1,000,000. Sure, by the time a mortgage is paid off and you fully own the house yourself a person should also have some savings, but I certainly wouldn't expect that to be universal.
I'd put money on a pretty messy driving history for the insurance to be that much.
That Concord episode of Secret Level is going to be pretty awkward.