On the contrary, bindless means less work for the CPU. Bindless basically means the GPU is responsible for querying image and buffer resources from a global heap or descriptor table.
If you actually look at x86 microcode much, you start to realize that the backend is actually very risc-like. The distinction between cisc and risc to me is more of a frontend instruction selection one.
Ok so, the final display gamut, initial source color gamut, and working gamut are three separate spaces. Effectively, the gamut defines where your primaries are, which are the positions of the unit RGB cube within a larger volume. These three working spaces can be all completely different, and the only thing to ensure is that you are consistent about transforming from one space to the next. It's possible to do operations that take you outside the final gamut, after which you clip or do some other operation. There are no hard and fast rules, although some approaches will certainly look much better depending on lighting conditions (color temperature) and so on.
Many of us, myself included, do not want to read about patent encumbered IP in general. It doesn't matter who owns the patent, or how you purport to wield it on this particular day, in this particular year. You are essentially doing the equivalent of traversing the internet, planting mines as you go.
You're slightly confused I think. We operate and perform lighting in linear color spaces, but the choice of white point and primaries offers a few degrees of freedom. LDR renderers might opt to stay within linear sRGB primaries, but it's easy to clip against the gamut boundary if doing HDR lighting. A color transform is needed to go to Rec2020 or wider.
Why are you using PNGs as a texture format? Generally, you'll use BC textures for the most part, or barring that, your images will be compressed as part of your archive format with some sort of super-compression algorithm that compresses the pakfile block-by-block. Perhaps you're referring to your texture compression/conversion pipeline which ingests PNG from your DCC tool of choice?
Sorry but Musk was an insufferable individual long before he came into his current wealth (the most prominent examples I can think of is the manner in which he exaggerated his credentials/education).
It might be more accurate to suppose that certain types of people are more likely to come into this sort of wealth.
You're just reiterating the author's point. Not every piece of software written faces dire security ramifications like leaking user identity. Not all software is loading or touching user data at all. Not all software is running in trusted environments. The premise is that Rust may be a good fit if security is a key concern, and even then I would argue it's likely possible to partition the domain into security-sensitive and security-insensitive domains. Cherry picking problem spaces where security matters and making claims about Rust goes against the spirit of the argument.
This is such a narrow view on the problem because you also have to restrict the "make sense" part to the set of problems where it's ok to have the entire ledger in public view, not to mention that there are other mechanisms to accomplish the double spend issue
Honestly, gzipped json is likely much smaller than uncompressed protobuf.
If you were going to use a binary protocol, why choose one that has no partial parsing/toc these days. There are much better alternatives IMO (flatbuffers being one of them)
Them falling out of favor has nothing to do with nanite FYI, and you would not want to use GS for any of the benefits a tech like nanite gives you because it's far too slow. We've all moved to CS for that sort of things if you can't rely on AS/MS
Graphics programming perspective: We call this “rejection sampling” and may work and is a more general sampling method that can sample from more difficult probability distributions but has significant disadvantages. First the runtime is the worst case across all threads invoking this in a GPU simd unit. Second, you have to evaluate the pdf itself which is easy in this case, and harder in general. The sqrt really doesn’t really amount to much to outweigh the cons in a shader. You can use the rcp sqrt intrinsic if precision is less important, or square the LHS if the ALU is actually a problem (or to conserve more energy)
So much crypto press here. You know what actually happened? The crypto talks were given to empty rooms, and the crypto booths were empty. People only took pictures to ridicule them on social media. Scams should sit down.
Aside from the advice mentioned (I bind caps to escape), I find that beginners use escape waaaay more often than is necessary because they aren't using all the commands at their disposal. For example, entering insert mode to delete some characters instead of using d+motion or x. Or entering insert mode to add indentation instead of using the = operator. It would take too long to enumerate all the cases where there is a much more streamlined way to perform an operation than entering insert mode, but I think this would explain the difference in experiences between people that may have used longer and aren't bothered by escape-use frequency and newer vim users.