[Bf-committers] "Security" gets in the way
matt at mke3.net
Wed Apr 28 23:34:42 CEST 2010
On Thu, Apr 29, 2010 at 2:31 AM, <malefico at licuadorastudio.com> wrote:
> What ?! how come the discussion started with "current blender defaults are
> getting in the way with production" which I totally agree and switched to
> "Let's replace Python with something else" ???
Yes, this is getting silly, and I think is representative of the problem.
I can see two major perspectives here: a) those from an IT background,
where security is very important and security is often a number one
priority and b) those who use blender in production, where having a
functional 3d application is a number one priority.
The fact that people are even suggesting to drop Python is an example
of this - placing security in the sense of protecting some contingent
of users from themselves, as having higher importance than the pain of
completely re-doing Blender's main scripting language which is working
very well, that hundreds if not thousands of users depend on, have
spent years learning, and which is the standard language of the 3D
industry. It just shows how wide the disconnect is. Clearly I don't
think this mindset should be driving a discussion that has clear,
practical and costly implications for the people that are actually
The very big problem now is that Blender is not functional by default
- very important parts of it do not work after you install it. Your
own files *don't work*. This is a very stupid situation to be in, and
needs to be changed.
More information about the Bf-committers