Would you consider a different pattern, woven on a old loom a new technology?
A app is not a "new technology". A microprocessor is a technology and the code you run on it is just another pattern on the loom.
A app is not a "new technology". A microprocessor is a technology and the code you run on it is just another pattern on the loom.
It's not useful to get pedantic about the definition of a "new technology." What is your point? Take the example cited in the article about deciding whether to store your data in SQL databases, vector databases, or blockchains. Are you saying that this is a purely aesthetic choice and not a choice that bakes in a lot of other patterns and decisions?
When we list humanities technological inventions a century from now, I don't think we will be listing CockroachDB or similar.
That's exactly what the author is arguing against. Decisions about foundational infrastructure (frameworks, databases, programming languages) have consequences for the organizations that decide to use them. Switching costs can be high. Lock-in of all kinds is real.
> When we list humanities technological inventions a century from now, I don't think we will be listing CockroachDB or similar.
That isn't at all what I or the author of the article was saying.
You could pick another word at some arbitrary level, but I'm not sure it's a particularly useful distinction to draw.