It looks like they used a fuck ton of Ray traced light effects to make the game look more natural and realistic. And yeah on a base PS5 which is basically running a RX 6700 or maybe a 3060 equivalent that's going to choke out. I suspect that they thought the PlayStation 6 was going to be out. I don't think anyone saw how much damage AI was going to do to our hobby. And they probably figured by now somebody would be making more RAM but with zero antitrust law enforcement nobody is going to take any chances...

As we recently discussed here, it won't allow that, whether because they didn't get the rights or because they decided not to do so. I would of course bet on the former, because R* wouldn't want the competition and they are not run by idiots.

Anyhoo, I wonder whether this version of the game will work on Linux. They have historically had a lot of problems with cheaters, which I have both been harmed by and benefited from at different times — when the big cash cheat was happening, they did take away most of the money that was given away, but they let people keep the vehicles and properties they'd purchased. They might well be tempted to utilize kernel-level anticheat, and I don't have Windows on my primary PC at all any more so that would be a hard deal breaker.

R* doesn't need my money, but anyway, they certainly won't get it if I can't run the game. The game probably won't run worth a shit on Steam Deck no matter what, and I imagine that the predictable effects on their decision making process won't be beneficial to me.

My epitaph once Krasnov sells us out to the Neo-USSR.

I had a coworker at Cisco in Santa Cruz (formerly the office was TGV, which they bought) who commuted from San Francisco who was an intern who absolutely did the work of a "real" employee. However you think the world works, whatever the laws are supposed to accomplish, this is reality.

It didn't eliminate either of those jobs.

You'll know eventually.

That's not how anything works.

NEVER AGAIN was supposed to be FOR ANYONE.

If they can do it to the Palestinians, they can do it to you.

This all works in exactly the opposite of the way in which you want people to think it works.

Why exactly is that? How do you profit from promoting genocide?

If there was competition in the market then no it wouldn't have done that but the same handful of people own all the grocery stores. Remember we put everything on the stock market and only a handful of people own enough stock that they actually have any kind of a controlling interest. Your 401k does not mean you have a controlling interest..

What does this means in practice is that there is zero competition in grocery shopping. The only limit on prices is the point where people actually start to notice that and stop voting Republican.

So they can fire a whole shitload of people and yeah it's slower for you to sit in the line ringing and bagging your own groceries and it's slower for everyone involved but you need food and they've got it so you have to put up with it.

There are a handful of alternatives but none of them at scale. You can drive an hour or two to a farmer's market I guess. There are expensive boutique grocery stores. Stuff like that. But realistically you're not going to be able to keep yourself fed with those. Not unless you have special circumstances. The majority of the population are stuck with the large grocery chains and they know it.

You could of course try opening your own grocery store chain to compete... Except they will run you out of business with low prices just long enough to bankrupt you and we don't enforce antitrust law.

We spent the last 50 years dismantling our Democratic institutions so that we could indulge in Petty moral panics. We are only just now starting to see the consequences of that. The real fun comes when the stock market finally collapses after the Epstein class is done looting our 401ks. If you're a baby boomer good luck dying before that happens because God knows you can't stop it.

If you were an NPC, how would you know? Besides your comments being posted as AC, I mean.

I didn't and don't but of course their excuse will be that this is the transitional period, and we have to wait for those jobs to materialize.

And there is a kernel of truth to it, in that if it were going to happen, it would take time to happen completely.

Ofc it's not going to happen, this is fundamentally different from prior shifts and it will only result in a net decrease. This would be a good thing if the wealthy didn't hoard all the wealth... Such as if we had the balls to take it. But, too many simps.

Deep thoughts, I actually did some machine language programming. Don't recommend it, but since It is an olde school thing, I was fine to lose my skills.

It can be a little scary, but is there a point where AI programming will be pretty good, perhaps being rusty won't mean anything.

As I noted, there is an SDR program out now that is not the equivalent of standard offerings - but better. It is AetherSDR, and It is pretty darn nice - written in Claude. A human reviews it for any egregious mistakes, but can you come up with a good reason that this complex program arguably better, should not exist?

I feel you man. I too don't know how to computer.

Encapsulating the compression for a part of data is not just changing an extension. The DNG format provides a world of features not present in a simple compression scheme (in fact it also provides multiple compression schemes depending on use case). Also this has zero to do with Apple. JPEG-XL is the codec used for lossy extensions as part of the Adobe DNG 1.7 specification. Every camera implementing lossy compressed DNG supports JPEG-XL and every software tool that reads DNG 1.7 can decode JPEG-XL.

The thing is... there's very few use cases for lossy DNG produced at the camera level. It's virtually only ever used after editing and recompression of DNG files. You shouldn't pat Apple on the back for giving you a sub-standard "ProRaw" *scoffs* image. There's a reason no real cameras on the market do that and instead offer to implement loss-less compression instead.

New features get released on a cadence of importance. There was just zero importance to JPEG-XL to the point where full decoders were developed and then just abandoned. Chrome even shipped versions two years ago with JPEG-XL support and then dropped it last year. Even compression schemes with legit use cases (there's very little use case for replacing JPEG since it works sufficiently for what most people use it for) take absolute years to adopt (look at AV1's painfully slow adoption despite the heavyweights of major streaming services and OS vendors behind it, hardware decoders are only just becoming ubiquitous).

What was the actual feature timeline? Less than 11 months. That's the time taken between the PDF/A announcing they will adopt ISO/IEC 18181 (JPEG-XL) as an image compression in the PDF format, at which point browsers which implement a PDF reader needed to have a JPEG-XL encoder to be compliant. It was less than 11 months between announcements and shipping a final product, and that included writing a decoder from the ground up. That defined the importance of the feature and why people should care about adopting it. Otherwise JPEG-XL would be just one of a hundred other image compression schemes not implemented by a browser.

11 months is not very slow, especially for implementing something ahead of time (there's zero PDFs out there with JPEG-XL currently needing decoding, just like there's virtually zero JPEG-XL images on the web for you to decode), instead of supporting an existing use case.

The person couldn't even infer JPEG-XL is a successive compression format to JPEG. Do you really need to insult them by throwing such fancy acronyms at the poor confused kid?

The purpose of a class is not to catch up the person who missed the previous class. This isn't even the only JPEG-XL article we've had in the past week. At some point editors just need to cut loose dead weight like you and get on with sharing the news.

Or do you need us to explain to you what a web browser is as well?