The code could be spaghetti even with a framework and is not necessarily spaghetti without one.
The big challenge when talking about use of frameworks is that developers always try to make it about some extremely subjective criteria that’s only in their own self-interest like easiness (for me) or best (whatever that means). Real criteria like costs or user concerns don’t up until way down the line. Its a massive difference in perspective that many developers refuse to consider and everyone else looks at as a individual contributor capability/maturity limitation.
> The code could be spaghetti even with a framework and is not necessarily spaghetti without one.
Sure, but some are easier to make spaghetti out of than others.
> Real criteria like costs or user concerns don’t up until way down the line.
This is orthogonal to frameworks versus not, just as you said one can make spaghetti in any sort of way, it doesn't mean that frameworks are worse at ameliorating "real costs."
The big challenge when talking about use of frameworks is that developers always try to make it about some extremely subjective criteria that’s only in their own self-interest like easiness (for me) or best (whatever that means). Real criteria like costs or user concerns don’t up until way down the line. Its a massive difference in perspective that many developers refuse to consider and everyone else looks at as a individual contributor capability/maturity limitation.