Look at photos of Crystal Palace in 1851 for example.

> The Department of Government Efficiency cut approximately 15,000 USDA jobs and terminated thousands of USAID programs, including a screwworm monitoring project.

Or the per-pixel coord atomic I guess?

At least if it's progressive (so refines and resolves over time), this has been done with pointclouds in the VFX industry in GPU shaders for years in terms of stochastically drawing different points so eventually the whole point set gets rasterised to a fidelity threshold.

Future proofing I guess...

Really?! What OSs can handle that many native threads?

Also, this seems quite similar to stochastic progressive drawing of pointclouds for realtime that has been done for > 15 years in the VFX industry with GPU shaders in a tiled/bucketed fashion, unless this isn't progressive maybe? (The fact it's been accepted for Siggraph likely indicates it's slightly different).

You update it for them every 3/4 years (if they're lucky).

It probably makes a bit more sense to compare it to existing software subscriptions like Office, or the old-school 'per-seat' licenses per user for software.

Do you mean 2013 or 2023?

Very likely a lot of the difference is the types of email each address is getting.

Also, a lot of workflows for image processing and compositing do assume that 0 means zero, whether correctly or not (often incorrectly). So there are often assumptions that for 8-bit, 0u maps to 0.0f and 255 maps to 1.0f for things like masking or alpha: as soon as you have 0 values which become just over 0.0, you then have artifacts because some code somewhere is using a hard threshold of 0.0 to mask some other operation, and vice-versa for 1.0 with alpha, where suddenly because the 255 values are no longer 1.0f, you have very slightly see-through objects (often only visible in certain situations or when pixel-peeping) after pre-multiplication.

(Same thing can happen when 254 becomes 1.0f after +0.5 with masking).

However OIIO is far from perfect in all situations (having had to debug and fix issues with its mip-map generation filtering code in the past), so don't always assume that just because there's a mature open source library out there doing something that it's always perfect.

It's generally correct: If you're self-employed / sole trader and operating outside IR-35, there's no way the HMRC can know how much you were paid as they don't have the info, so they can't know how much tax you owe.

In other situations for payrole / salary (like PAYE for example) they do have the info, as companies have to submit it, so generally people in those situations don't have to submit tax returns (unless they have significant capital gains).

I do think it's a bit annoying you have to declare tax on interest since 2016 if it's over £1000 - previously banks would take it out automatically, and this is still done in other countries (NZ for example).