lispit

...oops...

GPUs use tiling and morder-order storage for textures for this reason.

https://fgiesen.wordpress.com/2011/01/17/texture-tiling-and-...

Related to this is the concept of arrays of structures (AoS) vs. structures of arrays (SoA). Do you store all of the data that makes up one "object" in a single data structure, or do you store all of each "member" of each object in separate flat arrays?

If you need to use all of the "members" of an "object" at once, AoS is more efficient. But if you only need to use 1 or 2 members for a certain task, you will waste lots of memory bandwidth on data that isn't needed for the current operation. In this case, an SoA layout can improve your performance by an order of magnitude, by insuring that only the data that is actually necessary for your task is loaded into cache.

The same principle applies to row vs. column-oriented databases, which obviously are orders of magnitude more sensitive to IO bandwidth usage.

One of the most damning criticisms of OOP, from this perspective, is that it encourages you to wrap up lots of potentially unnecessary data into monolithic "objects" without concern to memory layout or usage patterns, giving you AoS and bloated data structures.

When Stroustrup created C++ or Hejlsberg created C#, did C progammers spend decades whining about their choice of names and alienating newcomers?

Twitch is still Flash, though the interface has been converted to HTML+JS.

http://blog.twitch.tv/2015/07/video-player-controls-now-in-h...

Yes.

https://stackoverflow.com/questions/21921790/best-approach-t...

newLISP is not a derivative of Common Lisp or Scheme or any other Lisp. It's a different language in a similar style.

I wish the Common Lisp camp wasn't so insistent on equating "Lisp" to "Common Lisp." It's annoying having to tiptoe around them by saying "Lisp-like language."