I really like sigils for several reasons and I do miss them when in non sigil languages - imo raku made two big improvements over perl that is to avoid changing the sigil on accessing an item and to have an unsigilled option for people who don't like them https://rakujourney.wordpress.com/2022/12/24/on-sigils/

>and to have an unsigilled option for people who don't like them

Sigilled "variables" do lose many of the perks that sigils provide though, as codesections explains in the blog.

in Raku, this is:

class A {

    has $!bar;    #private
    has $.baz;    #public (with autogenerated accessors)

    method !foo {}     #private
    method  foz {}     #public
}

Hi @ritchie46 - I have just written [raku Dan](https://github.com/p6steve/raku-Dan) as a way to scratch the "data analytics" itch in a new way -- my next step is to write Dan::Polars as a polars binding via (eg.) raku NativeCall. Can you point me to a good recipe for success? ~p6steve@furnival.net

A single binary dependency may be a better fit for one project as you outline, but I would make the wider case for a common core language that provides a DSL toolkit with a recursive descent style Grammar capability. This helps to build critical mass across multiple DSLs to maintain and improve a secure code base. In turn, DSL authors get a more productive development environment. Raku embeds Grammar support for DSLs and will soon have AST introspection for "Slang" authors to reach in and build elements directly...

I'm still looking forward to a single binary for each of the following:

* NQP

* Rakudo

* Rakudo programs

Building on https://yakshavingcream.blogspot.com/2019/08/summer-in-revie...

Yes, that’s precisely what I am trying to say. With FatRat (aka BigInt) by default then the casual programmer has to know to step explicitly into Num (eg by 1e-1 + 2e-1 which needs a bit of a scientist mindset) or will never benefit from all those lovely FPU transistors.

typing, roles/inheritance and multi dispatch together offer a very clean coding model that cuts through the usual if-then-else wool

great question @msvan - raku has many ... for me the unique genius of raku is to have stolen all of the best parts of type system, OO, grammars & regex, functional and procedural coding and jammed them into one smoothly integrated syntax

'use Inline::XXX;' gives raku coders access to Perl5 (CPAN) and python modules

Actually, it is even simpler than that. If you have the Inline::Perl5 module installed, then the only thing you need to do to load a Perl module, is to use the :from<Perl5> adverb in the -use- statement, e.g.:

    use DBI:from<Perl5>;

this works now x for input and output ... the challenge for this kind of thing in bare code is that you need a LOT of namespace ... .oO maybe override the dot?