This is llm hallucination too? Old ideas and goes back to a system that was in place in the 1800’s. It didn’t go well. Who are these people that peddle this every 20-30 years or so? Opportunist.
I found a different benefit to micro services — AI understands them and context matters. Monolithic app confuse ai where micro services enables them to be far more effective.
It's an interesting question how AI influences this. If it scales up the scope of what an individual engineer can do, and if the primary driver of microservice scope is Conway's law, then in theory microservices should get "fatter".
However I go the other way than you: I have found AI needs as much context as possible and that means it understands monoliths (or fatter architectures) better. At least, the agentic style approach where it has access to the whole git tree / source repository. I find things break down a lot when changes are needed across source repositories.
The visual is really nice. I can appreciate this tool, but once it’s in my database it’s for the human to manage and update. Do I go back to using this tool? How can this help? I don’t want any tool to read data like mcp can. Read table names, sure.
We tried different services like these, they quickly become unappetizing. You end up forcing yourself to microwave a box vs. order something fresh cooked.
I guess I’m looking for some decent food that isn’t owned by the tobacco industry. Having variety of meals that are cooked by chefs with good ingredients.
It’s hard to believe that 10k is worth whatever they need from Perl in 2025.
I wrote Perl for many years while I worked on the godforsaken cmecf system.
Cmecf this year announced it had been hacked by Russian hackers.
This means that cmecf written in Perl allowed a country access to Federal Court evidence including intelligence gathering methods, corporate secrets, and inside sources.
Perl is not memory safe, loaded with security issues for over a decade. It’s only saving grace is string manipulation, which is exactly why the best hackers in the world all know it.
You must have confused Perl with another programming language. Perl has always been a memory-managed language with a reference-counted garbage collector.
The link you posted doesn't even mention Perl at all. It does say that:
Using a memory safe language can help prevent programmers from introducing certain types of memory-related issues. Memory is managed automatically as part of the computer language; it does not rely on the programmer adding code to implement memory protections.
Perl clearly fits the definition of a memory-safe language with automatic memory management. The funny thing is that this document lists Delphi/Object Pascal as memory-safe languages, even though there are clearly not.
Perl is not memory safe? Are there pointers directly to memory like in C? No, it is an interpreted language that runs opcode in the Perl virtual machine.
Sure, there are quite some safety concerns with Perl, but they can be mitigated.
For example there is the taint mode with "-T" that prevents direct execution of system commands.
Would I use Perl for a new project? No. :-)
I would be interested in more details about the cmecf hack!?
Was the bug in Perl or its libraries, or in the code written in Perl? There are many valid criticisms of Perl, but I've never heard of the language itself described as insecure, and especially not memory-unsafe. I don't know how I'd write a use-after-free or stack smash in Perl if I were forced to.
Yep, there are bad bugs for example in mod_perl which is written in C and takes the interpreted Perl code and runs it in the Apache context. I think this is what the OP "heard about". But that is not the fault of Perl itself.
reply