https://bugs.documentfoundation.org/show_bug.cgi?id=97827
--- Comment #7 from Michael Stahl <[email protected]> --- > - LibreOffice uses the Rhino engine to support JavaScript. Rhino is written > in Java, it is heavy and slow for complex macros. this is utterly irrelevant - your macro is going to call heavy and slow LibreOffice code via heavy and slow UNO bridge that looks up every method to call via UNO reflection, so it will never be fast anyway. SpiderMonkey and V8 are very large and complex C++ projects with unstable APIs so integrating them would be very painful (cf. the ongoing Firebird disaster). also they have their own GC whereas Rhino uses the Java GC, so switching would make our distributed-GC problem (which already exists between Java and Python) worse and leak memory (can't collect cycles). furthermore, ~nobody is using JavaScript (or BeanShell for that matter) for LO scripting anyway, there is ~no documentation for it, in fact there was a plan to unbundle all the Java Scripting Host based stuff to an extension and the only reason that didn't get done is that nobody had the time to work on it. see ESC minutes from 08.11.2012: http://permalink.gmane.org/gmane.comp.documentfoundation.libreoffice.devel/38646 + should we drop Rhino, Beanshell & javascript in 4.0 ? (Michael) + could be turned into an extension + was in the past was turned off (Stephan) AA: + disable Rhino / Beanshell unless in experimental mode (Michael) + for future deprecation / removal. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
