Re: Digital Twin applied to Software

Carl,

Yes, strong/static typing, resource ownership and mutability constraints require that you have a plan. It's not useful for rapid prototyping at all. It shines when your architecture has settled and requires exactly these constraints in order to work reliably and stay maintainable.

As I understand, this does not apply to most applications typically implemented in Smalltalk today.

Smalltalk and C++ are worlds apart. Different markets, purposes, requirements, applications, mindsets and developer communities. Without common ground, debating the benefit of language features doesn't make much sense. Everyone is correct within their scope, but the scopes don't overlap.

Whether that bodes well for a Digital Twin, I don't know. I can imagine a Smalltalk tool that translates classes to C++ (I happen to have one, although still incomplete). But the other direction looks all but impossible to me.

Andre