Alternative view : for security reasons open source use will shirnk, since it's becoming most dangerous vector of attack.
Future Software Factories will have extra large static harness, that will be have a very few dependencies, e.g, reactjs, bundled into the package. Even nodejs probably will be more of a runtime feature, patched by the cloud.
open source was mostly a feature of not enough software eng resources. Now , since this is in abundance, instead of a shortcut it becomes a risk.
So in this future, we don't use hardened software. We use security through obscurity.
...But also in this future, the source code of all of these programs is stored in context in the cloud of a few tech companies with unknown levels of security around such context?
Considering they likely use the stuff for training, what are the odds its actually air tight for the foreseeable future? The odds are 100% that the contexts will be compromised because that's the conjecture with the open source projects as well, yes?
Doesn't that seem concerning?
>patched by the cloud
Yes, something like that.
I've pitched the idea on twitter and asked security guys whether someone does something like this:
Say we have 0/1-days in Python 2, which is not maintained. I'm thinking of software + service which will:
This way we don't need centralized maintenance, although it will work better with it.