From understanding my old GameBoy that had 4 AA batteries in alternating rotation, that had 6V (1.5V each battery). Chaining positive and negative together increased the voltage.
Since this has them pointing both up, it’s just 1.5V but it’s as if you put a half sized battery.
Basically, the same, just less amperage because of a smaller battery (if compared to 2 of the same).
tl;dr: same, but half capacity.
This is a trash take.
I just wrote the ability to take a DX9 game, stealthy convert it to DX9Ex, remap all the incompatibility commands so it works, proxy the swapchain texture, setup a shared handle for that proxy texture, create a DX11 swapchain, read that proxy into DX11, and output it in true, native HDR.
All with the assistance of CoPilot chat to help make sense of the documentation and CoPilot generation and autocomplete to help setup the code.
All in one day.
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.
Always removed in two, there are. No more. No less.
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.
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.
Bad effects are bad.
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.
Since you’ve gone, I’ve been lost without a trace
I dream at night, I can only see your face
I look around, but it’s you I can’t replace
I feel so cold, and I long for your embrace
I keep crying, baby, baby please
Oh, can’t you see
You belong to me?
How my poor heart aches
With every step you take?
I understand the full lyrics, but most songs generally default to romanticism. If you’re not paying attention it’s easy to misinterpret.
I can spend 2 minutes scanning a page for a certain word every time I need to search for something.
But I’m very happy somebody spent the time to code Ctrl+F.
While
Whyle
Whyull
Yull
Yul
The way his content is structured and edited is like junk food for your brain. There’s a formula that appeals to the least lowest common denominator and he (his team) excels at it.
The topics he picks usually hit some nerve of vicariousness (game shows contestants) or suspense from wanting to know what happens next (challenges and clickbait).
Nice riposte, OP.
When I document code I have this problem with indices vs indexes.
No. Microsoft is not liable, at least when it applies to HIPAA.
The HIPAA Rules apply to covered entities and business associates.
Individuals, organizations, and agencies that meet the definition of a covered entity under HIPAA must comply with the Rules’ requirements to protect the privacy and security of health information and must provide individuals with certain rights with respect to their health information. If a covered entity engages a business associate to help it carry out its health care activities and functions, the covered entity must have a written business associate contract or other arrangement with the business associate that establishes specifically what the business associate has been engaged to do and requires the business associate to comply with the Rules’ requirements to protect the privacy and security of protected health information. In addition to these contractual obligations, business associates are directly liable for compliance with certain provisions of the HIPAA Rules.
If an entity does not meet the definition of a covered entity or business associate, it does not have to comply with the HIPAA Rules. See definitions of “business associate” and “covered entity” at 45 CFR 160.103.
https://www.hhs.gov/hipaa/for-professionals/covered-entities/index.html
HIPAA doesn’t even require encryption. It’s considered “addressable”. They just require access be “closed”. You can be HIPAA compliant with just Windows login, event viewer, and notepad.
(Also HIPAA applies to healthcare providers. Adobe doesn’t need to follow HIPAA data protection, though they probably do because it’s so lax, just because you uploaded a PDF of a medical bill to their cloud.)
Burn-in is a misnomer.
OLEDs don’t burn their image into anything. CRTs used to burn in right onto the screen making it impossible to fix without physically changing the “glass” (really the phosphor screen).
What happens is the OLED burns out unevenly, causing some areas to be weaker than others. That clearly shows when you try to show all the colors (white) because some areas can no longer get as bright as their neighboring areas. It is reminiscent of CRT burn-in. LCDs just have one big backlight (or multiple if they have zones) so unevenness from burnout in LCDs is rarely seen, though still a thing.
So, OLED manufacturers do things to avoid areas from burning out from staying on for too long like pixel shifting, reducing refresh rate, or dimming areas that don’t change for a long time (like logos).
There is a secondary issue that looks like burn-in which is the panel’s ability to detect how long a pixel has been lit. If it can’t detect properly, then it will not give an even image. This is corrected every once in a while with “compensation cycles” but some panels are notorious for not doing them (Samsung), but once you do, it removes most commonly seen “burn-in”.
You’d have to really, really leave the same image on your screen for months for it to have any noticeable in real world usage, at least with modern OLED TVs. You would normally worry more about the panel dimming too much over a long period of time, but I don’t believe lifetime is any worse than standard LCD.
TL;DR: Watch RTings explain it
The point is to show it’s uncapped, since SDR is just up to 200 not. It’s not tonemapped in the image.
But, please, continue to argue in bad faith and complete ignorance.