Only reason I haven't modded HDR for this game is because it's DX9 and a pain to mod. (I already did GTAV - Enhanced and GTA Trilogy Remastered since it's UE). If they make a new port for PC it'll be able to complete the set.
Definitely not. NoJS is not better for accessibility. It's worse.
You need to set the ARIA states over JS. Believe me, I've written an entire component library with this in mind. I thought that NoJS would be better, having a HTML and CSS core and adding on JS after. Then for my second rewrite, I made it JS first and it's all around better for accessibility. Without JS you'd be leaning into a slew of hacks that just make accessibility suffer. It's neat to make those NoJS components, but you have to hijack checkbox or radio buttons in ways not intended to work.
The needs of those with disabilities far outweigh the needs of those who want a no script environment.
While with WAI ARIA you can just quickly assert that the page is compliant with a checker before pushing it to live.
Also no. You cannot check accessibility with HTML tags alone. Full stop. You need to check the ARIA tags manually. You need to ensure states are updated. You need to add custom JS to handle key events to ensure your components work as suggested by the ARIA Practices page. Relying on native components is not enough. They get you somewhere there, but you'll also run into incomplete native components that don't work as expected (eg: Safari and touch events don't work the same as Chrome and Firefox).
The sad thing is that accessibility testing is still rather poor. Chrome has the best way to automate testing against the accessibility tree, but it's still hit or miss at times. It's worse with Firefox and Safari. You need to doubly confirm with manual testing to ensure the ARIA states are reported correctly. Even with attributes set correctly there's no guarantee it'll be handled properly by browsers.
I have a list of bugs still not fixed by browsers but at least have written my workarounds for them and they are required JS to work as expected and have proper accessibility.
Good news is that we were able to stop the Playwright devs from adopting this poor approach of relying on HTML only for ARIA testing and now can take accessibility tree snapshots based on realtime JS values.
While true, cars that breakdown don't come to a complete stop, generally. You should put your hazards and roll to the shoulder. That's not always possible, of course. But if a vehicle is clearly disabled, you wouldn't stop behind it waiting for it to move out of the way, which is what happened here as well.
No, if you click a link that brings you to or from a site your IP is logged
No, clicked links that bring to a site do not log your IP. For that you would have to add some sort of JavaScript to intercept the click and then have some JavaScript execute a HTTP Request that passes that information (eg: HTTP POST). Then the IP can be grabbed via that request by the receiving server. Or more importantly, a tracking cookie.
When clicking a link, the browser may add to Origin header on the HTTP request (HTTP HEAD/GET) that goes to the link's server. Or the link itself can have UTM parameters, but there's no guarantee that ever gets back to the original server.
But the point is if you have a page with 1000 links on it, the server that serves you the page doesn't know which one you clicked without JavaScript or reframing the link to go elsewhere, which is why this post exists.
I suggest against it. Just use JSDocs syntax and typescript (the CLI and VSCode checker) will check it. No need to use transcompiler anymore. It was more useful when JS itself was more ES5 based and CommonJS.
Using something like esbuild will get you minification if you want it, but it's only for deployment, not actually needed for runtime. Having pure JS code is much easier to work with and debug.
Most "film grain" is just additive noise akin to digital camera noise. I've modded a bunch of games for HDR (RenoDX creator) and I strip it from almost every game because it's unbearable. I have a custom film grain that mimic real film and at low levels it's imperceptible and acts as a dithering tool to improve gradients (remove banding). For some games that emulate a film look sometimes the (proper) film grain lends to the the look.
I used to hate film grain and then did the research for implementing myself, digging up old research papers on how It works at a scientific level. I ended up implementing a custom film grain in Starfield Luma and RenoDX. I actually like it and it has a level of "je ne sais quoi" that clicks in my brain that feels like film.
The gist is that everyone just does additive random noise which raises black floor and dirties the image. Film grain is perceptual which acts like cracks in the "dots" that compose an image. It's not something to be "scanned" or overlayed (which gives a dirty screen effect).
Related, motion blur is how we see things in real life. Our eyes have a certain level of blur/shutter speed and games can have a soap opera effect. I've only seen per-object motion blur look decent, but fullscreen is just weird, IMO.
You remember Steve from IT? The only one who knew how to manage our backend infrastructure? Well, after that unfortunate plane crash, we uploaded the entire contents of his laptop, cellphone, and personal cloud to an artificial AI. We were able to revive him to bring him back. Even better now, because we have him resurrected in simulated form, he now exists in a perpetual state of working at the office and no longer needs to go home to rest or be with his family. That means with the new 24x7 productivity, we are expecting increased profits for this next quarter.
Sure, but what does ChatGPT say?