On August 9, 2011 08:57:07 am Frederic Da Vitoria wrote: > There is no reason to be insulting.
It is insulting to experienced veterans when people with less understanding of the issues come to half-baked conclusions; pretend that their conclusions are universally valid; and keep arguing without listening to the arguments of the experienced voices. > I did indeed miss the points you so vehemently cited. Which means the > potential performance issues Harry feared would remain. No. It only means that that Harry's fears have not been addressed yet, and that you are one again jumping to conclusions. Unlike you, Harry was careful to specify that this is his point of view and not a conclusion. To address this fear: there are enough empirical solutions and literature out there to demonstrate that the combination of scripting language with compiled code does not suffer significant performance issue. Adobe Lightroom, not the slowest RAW converter, uses a combination of Lua scripting for the UI and compiled C/C++ where performance is key. What Kay is suggesting (and I fully support) is to keep using C/C++ where speed of execution (aka performance) is the bottleneck and use Python scripting where speed of development is the bottleneck. Parts of the Python script can always be rewritten in C/C++ after careful analysis identify them as being the bottleneck. The only real problem is resourcing the project with the necessary human resources. Organization. And noise. Yuv
signature.asc
Description: This is a digitally signed message part.
