1,872 karma · joined September 26, 2020
The points are: game graphics is indeed suffering, but the problem is not being unlike films and photos, it's the opposite. The games should stop using film industry produced tone mapping curves and instead create their own, making a clean break.
Personally, I agree with the video.
Personally, it's always sad when a company agrees to censor on their own merit when they don't have legal obligation to.
Regardless, I wanted to point out the obvious: each new broad regulation increases the cost of operating in the market where said regulation applies. The gatekeepers of today might not leave, but every new potential newcomer will calculate is it even worth it to operate in a market like that? Maybe it pays off to invest hundred of millions into lawyers and lobbying instead of technologies? Or maybe we'll skip EU market altogether (for reference, according to a courtroom statement Apple gets 7% of their revenue from Europe)
The only financially viable solution for online games is to release in Europe later, after the project popularity in other markets was established.
So now I'm using LLMs as crapshoot machines for generating ideas which I then implement manually
The restart is there in my example, and it doesn't look too complex. And this aspect of observation is exactly what will be changed in Swift 6.2. Nice improvement, I'd say!
> I disagree, because the model hasn't changed yet. That's the crippling aspect to it: You can't tell some controller object to recompute its state based on a change to another object in the model, because you're getting notified BEFORE that object has changed.
If your model stores 2 interdependent states then you'll risk running into infinite update loop regardless of whether you've been notified from `didSet` or `willSet`. It can be fixed by changing the model.
To be fair I didn't understand your example with camera and resolution. In all cases you already know the new value and so the dependent code is good to go. The code shouldn't ever care where the value comes from: the main state, the future state, or some mock state.
It works by signing the build with your personal Apple ID, using Apple servers.