| Startup time is not the strong point of Rakudo. And it will be a long time before it will. Beyond startup, performance definitely has attention of the core developers: that's when hot code gets inlined, and JITted to machine code if you're on Intel hardware. But before that, currently not so much. The best possible startup time that could potentially be reached in the current implementation of Rakudo, is the bare startup time of NQP in which Rakudo is basically implemented. Compare NQP on an Intel 2.4 GHz i9 on MacOS: % time nqp -e ''
real 0.04s
user 0.03s
sys 0.01s with: % time rakudo -e ''
real 0.15s
user 0.15s
sys 0.03s With NQP taking about 16MB of memory. Raku as a language is selected for its features, its community and possibly for its promise. Whether that is a disaster or not, is up to the user. Finally, if you want fast startup, don't use a scripting language. |
Huh? Isn't startup speed one of the points of simpler, less optimized interpretation strategies? I mean, unless you compare it to AOT compilation, which is another story. Those numbers show that Perl and Tcl, both "full featured" scripting languages, don't have the least issue on the matter.
I'm not the kind to freely rain on parades, especially when Raku is already not a popularity king, but I don't think my use of the word "disaster" was unfounded, even if not "very nice".