3 ms·
> An app architecture i.e. a framework. > Then because they're complicated they're difficult to learn. It's easier to learn a publicly available framework, a
by okeuro49 3y ago
> An app architecture
i.e. a framework.
> Then because they're complicated they're difficult to learn.
It's easier to learn a publicly available framework, as there is lots of help on Stackoverflow, and usually the popular frameworks have good, or just existing, documentation.
> existing code isn't dependent on some obsolete framework - Ember/Angular 1/etc.
The "app architecture" can also become obsolete. But now instead of a migration path, you're stuck with the person who made the "app architecture" most likely having left the company.
- sanitycheck 3y agoNo, not a framework. The fundamental idea of a framework is that it's reusable, and there are inherent compromises and complexities which are a direct result of making reusability a goal. I've adopted lots of code, some good and some terrible. Framework-based code is only easier to understand if I already know the framework and sometimes not even then if the original developers mostly had to fight their framework. The "app architecture" does not become obsolete because nothing has come along to replace it and it was already simple enough that Stack Overflow was never a necessary part of development. K.I.S.S. Not just glam metal.