On Fri, Jan 06, 2017 at 01:14:31PM +0300, Konstantin Tokarev wrote: > > > 05.01.2017, 23:06, "André Pönitz" <[email protected]>: > > On Thu, Jan 05, 2017 at 07:57:54AM -0600, Thiago Macieira wrote: > >> Em quinta-feira, 5 de janeiro de 2017, às 07:26:52 CST, Phil > >> Bouchard escreveu: > > AFAIU QtQuickCompiler has nothing to do > >> with memory management, its main > > purpose is reduction of start > >> up time and obfuscation of sources. > > Ok I assumed that > >> execution time would be affected because the code is > compiled. > >> > >> The code is compiled anyway. The difference is only *when* it is > >> compiled: at release time of your application or when your user > >> launches it (JIT). > > > > It's not the only difference. A JIT compiler has typically not the > > same scope/abilities/optimization opportunities as a real compiler, > > not to mention deficiencies in a language that has 'double' as only > > numeric type. > > Yes, JIT compiler has much more optimization opportunities in case of > dynamically typed language than "real" compiler.
The point is that deciding to use a dynamically typed language in performance sensitive environments already paints you into a corner. Whether it's faster to jump from the 20th floor or from the 40th does not make a conceptual difference if your goal is to survive. Andre' _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
