Angular reminds me of the Spring "framework". Once you peel back the GIGABYTES of framework redirection and figure out what it's actually doing, it's not a bad

Angular reminds me of the Spring "framework". Once you peel back the GIGABYTES of framework redirection and figure out what it's actually doing, it's not a bad way to organize code - it's just that trying to wrap that up in a reusable library rather than just recommend it as a best practice is so braindead as to be incomprehensible.