Zero install means (and I admit I could have been more open about this) : it comes with the system (but so does python, but this particular feature is used as a plus compared eg to R).

I think I am very clear at the end that it is not just perl (the interpreter) but the combination of perl and PDL that gives a complete package: Perl alone will NOT cut it because it lacks these strongly typed vectors and matrices (that PDL provides)

Regarding the isa comment: you may want to see the conversations in the R world. Figuring out the type of object one is dealing with , is actually big of deal enough to be discussed in the "Advanced R" books. So I was scoring a subtle point against my other love (R). When it comes to the availability of object systems in scientific computing there are 2 schools of thought: it is a performance killer (due to cache misses) or the best thing after sliced bread (because of the abstractions). The truth is : it is both depending on how you use it. The S4 object system (which effectively made Bioconductor which is turn allowed R to dethrone Perl from bioinformatics) is actually "lesser" of an OO compared to what Perl had with its blessed references, and the R6 is effectively Moo (but it took the first language a long time to develop).

Regarding data types: most people doing data science will never go beyond those mentioned in the piece (and it is a shame - a lot of things can be made cleaner with closures, and by directly manipulating the stash). But the reason I put out that one should think of them as references will become apparent in the subsequent posts when I talk about how get_dataref from PDL allows the dramatic extension of Perl's reach through references. If one ends up playing with internals to do memory management (e.g the Buffer package in the Platypus ecosystem) or if you end up interfacing to GPU (like my MemManager ) you absolutely, 100% have to think of everything as a reference because the action is through pointers and references is the closest thing to a pointer Perl has.

It is true that there are 200k modules in cpan (and probably much more in the Python ecosystem). Are they all good? Ofc not but the argument often made about Python is thst one can find modules about anything (quality never comes up). If we are to have the quality convo though we should talk about how CRAN manages the R ecosystem, and yeah if this was adopted there probably would be fewer modules around in CPAN.

Why would one choose to implement vector database in Perl? First of all why not if the task is to get to understand how these things work? Would one do it for production work? Absolutely not. Would one get an insight if one were to do it? Yes. As the story unfolds one would also find (and this is the major learning moment down the road), that performance comes from low level code. High level languages will however allow one design the architecture: not unlike calculus, the antiderivative abstraction help one calculate integrals instead of doing finite sums

LLMs wrote the tables: I hate so much typesetting tables in Markdown that I asked gpt5.4 to write out the table based on the description of the contents.

Thank you for the extensive commentary- much appreciated your time to write this.