gsoc-2021-ideas

s good. > I doubt we're going to see big commercially-backed library development efforts for it, soon or ever. I agree. > Perl 5 has a huge ecosystem of course, but it's such a nasty warty language with nasty warty tooling. This is where I think Raku's strength lies. A lot of the effort that went into Raku was to build a platform that could just directly use tooling and libraries of other PLs while insulating developers from their downsides. That way you get to use Raku tooling, syntax and semantics at the surface level with other PLs' tooling and modules and performance. Kinda like using C code in a non-C PL, but generalized to using code from any other PL in Raku. The exemplar was supposed to be Perl, but it was also supposed to extend to many other PLs. Starting 7 years ago this became the Inline family.[1] Inline::Perl is the most mature. Imo it's remarkable. But it was always supposed to just be the first one to get the polish to demonstrate that the approach works and works great. About a year ago the author behind it said it was nearly time to do the same for Python modules. And now I see a GSOC proposal to do that.[2] The Inlines hide the warts (though you do have to read the modules' documentation to know what their API's are etc). I think the impact of Inline Python will be huge because it takes away the complaint about reading Perl documentation and code. Instead you read Python API docs but get the benefits of using Raku. (And, in the wings, there's Inline::Ruby, Inline::Lua, and so on.) [0] https://raku.land/ [1] https://raku.land/?q=inline [2] https://github.com/perl-foundation-outreach/gsoc-2021-ideas/...