You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Though on that subject, loops with non-constant span won't even compile, so I've been forced to do a hack where the loop always has the same number of iterations but only some of them do any meaningful work. (Last week's DOF blur shader adapts iterations to distance this way)pic.twitter.com/32totsaIup
Yeah I think it's because it is always running all iterations of the loop - basically when it compiles it's unrolled that many times, and the iterations that were "false" get multiplied by zero so the values don't count. (may all be a lie, definitely verify)
Now when you mention it, I guess that would explain why the vertex-->fragment pipeline has an order of magnitude less memory than the input... the worst part is that as ridiculously complicated as the idea sounds, it's too plausible to dismiss.
After reading through a lot of documentation and tutorials, my impression of shader languages has gone from "it's eldritch sorcery, no mere mortal could possibly learn them" to "okay, it's sort of like C, I can deal with this"... and then firmly back into "it's sorcery".
That tracks with what I know about it as well
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
