anisotropic

It just gets blurry and looks unappealing (although that's better with anisotropic filtering, but then, anisotropic filtering is also expensive and not every device/GPU supports it).

And in texturing what you do to avoid aliasing is mipmapping (you might also throw anisotropic filtering on top).

Sky's diffusion and reflection is very anisotropic and omitting this gives your simulation very unnatural feel.

Ask any high-level language compiler implementor; they will tell you that x86's register-starvedness and anisotropic instruction encoding are huge losses.

The x86 line has anisotropic instruction encoding; more frequently-used instructions are shorter.

If you'd be doing WebGL you can do some things like using square power of two textures and enabling mipmapping and if available anisotropic filtering.

One thing that also bugged me is the fact that an isotropic light source forms an unevenly-lit image, so maybe you'd want an anisotropic emitter too.

It's not the same as Kindle's eInk, just an LCD with amazingly low dot pitch and an anisotropic color filter which only works in transmissive mode (backlight on).

Subscripts are how it's used in the more down to earth engineering applications like anisotropic thermal conductivity and elasticity.

>they will tell you that x86's register-starvedness and anisotropic instruction encoding are huge losses.

You take a Computed Tomography series of images, doing all kinds of back-projection (duh) and volumetric anisotropic edge-preserving smoothing, and then you apply segmentation and false-color, semi-transparent transfer functions and lighting...

Instead, the logic board is seated on top of an anisotropic graphite sheet, which helps disperse any heat that is generated out to the sides, all while your Mac stays virtually silent.

Since the box is anisotropic, this would not give the uniform distribution (it's more likely to draw a "diagonal" direction than a coordinate axis direction).

> And the "anisotropic instruction encoding" makes so much sense that ARM adopted it (in a much simplified fashion) with Thumb-2.

To anyone who wants to actually understand this: Carbon fibre doesn't have a single "strength" value since it is virtually always anisotropic - its strength varies massively depending on which direction you stress it in.

So while of course it's better to keep everything in registers if possible, I'm sure that the old Lisp compilers would have performed reasonably well on x86 if they'd tried instead of throwing their hands in the air and saying "we can't do it!" And the "anisotropic instruction encoding" makes so much sense that ARM adopted it (in a much simplified fashion) with Thumb-2.