> And it also makes the project more secure, from supply chain attacks and such.
And less secure, from having fewer eyes look at it.
> Because there is no "abstraction layer" of a framework,
In a large project, I think you’ll end up developing a framework for use in-house, even if you don’t call it that.
> you also have greater control over your project, and can make performance optimizations at a lower level.
That’s true; you can tweak the framework to match your use case. For an analogy, look at Apple. They have much greater control over their hardware stack than the typical PC manufacturer. Because of it, they can change it to suit their needs.
And less secure, from having fewer eyes look at it.
> Because there is no "abstraction layer" of a framework,
In a large project, I think you’ll end up developing a framework for use in-house, even if you don’t call it that.
> you also have greater control over your project, and can make performance optimizations at a lower level.
That’s true; you can tweak the framework to match your use case. For an analogy, look at Apple. They have much greater control over their hardware stack than the typical PC manufacturer. Because of it, they can change it to suit their needs.