> Connectors are what really matter when it comes to de-risking a project. Yes, they define the architectural style and thus what architectures you can build.

> Connectors are what really matter when it comes to de-risking a project. Yes, they define the architectural style and thus what architectures you can build. This is getting more and more important because the default architectural style of the vast bulk of our programming languages, call/return, is unsuited for build most of the types of systems we are trying to build. > Components aren’t all that interesting. Yes and no. The architecture is defined by the connectors, but in day-to-day programming, your functionality is going to be mostly in the components. > And at any scale I think about in my work, there’s components and connectors Yes. Which is why I created an architecture-oriented programming language that lets you deal with components and connectors http://objective.st http://objective.st > Is this what the Smalltalk guy meant by it being all about message passing? I believe that to be largely the case.