Well yes and no. If I know that I have this proclivity it’s on me to plan accordingly. I usually know better and reserve time but I forgot to yesterday.
But from their point of view they’ve just been snubbed after working up the courage to ask. It’s uncomfortable to be rejected.
That’s why it’s the introverted that so often is labeled offensive.
> I don’t think constantly adapting our behavior to please extroverts is the answer. Helping people understand introversion is a far better approach.
And by "helping to understand introversion" I would suggest to first check your own MBTI personality type and - if possible - let your social partners do the test as well. But as I know Extraverts, they don't give a shit about "deeper" stuff. So the interaction stays superficial and I just stopped caring how they interpret my behaviour.
I really like the idea, why not hack a scripting engine to add bindings to itself, e.g. in Duktape JavaScript engine. Then a JavaScript function could use the C-API of Duktape to generate AST's at runtime for itself. But I think the VM would be the limit then... support for coroutines etc.
use `pairs(a_table)` to get `key, val` variables bound respectively. Use `ipairs` to get a loop over indices and values. This is very similar to Python, only with "do/end" instead of indent/dedent. What you can't do in Python, but can in Lua is to provide less variable names than the iterator function returns. For example, to get a list of keys when iterating over `(key, val)` pairs in Python you'd have to do this:
There was a time (around Blender 2.70) when we did provide Blender packages and it did compile (of course, since all our software is built from source) but then llvm dropped JIT around version 3.5 and it became incompatible with OpenShadingLanguage.
We made a choice that we'd rather forge ahead with modern LLVM and Clang (for Rust, Clang-GCC and Julia) than hang back to support Blender. Given our very limited resources, this was still probably the right decision, however, we might have made a choice to create a special llvm35 package at that point, but we had no idea that OpenShadingLanguage would take so long to adapt to MCJIT, which the still haven't done to this day, as far as I know.
The important point here is that MSYS2 is a very open-source, limited resources project. We aren't experts in all packages, so if you are knowledgeable about llvm, OpenShadingLanguage and Blender and are interested to do so, then please help out.
For Blender, getting CUDA support into MSYS2 is probably high up on the priority list too.
Plot twist: US companies and the US gov play a game whose only goal is to reestablish lost trust since Snowden to make more $$$ again and sell more hardware with US backdoors again.
My reasons are made clear in the README. I don't want to contribute to nonfree software. It's pretty simple.
Businesses who want to use my work in nonfree software are welcome to get in touch to negotiate such a license.
IMHO, for anyone who has seriously considered the morality and ethics of software licensing options, the AGPL is the obvious choice. I'm surprised it isn't more popular. It was a shame large donors strongarmed the FSF into splitting it from the GPL, and that the FSF kept pushing the GPL as it's go-to license.
This library doesn't seem to be focused on matrix math for computer graphics.
FWIW, you don't tend to see a significant gain from writing those individual types as SIMD. The gain is from operations over large arrays of numbers. E.g. each vector has only one component type in it (e.g. you have vectors of [x0, x1, x2, x3] and [y0, y1, y2, y3] instead of [x0, y0, z0, w0] etc).
