Like everything else you can't really say this vs this without giving a proper case, the answers will be of a personal choice and non-specific.
So much trash talk being thrown around here and it all boils down to personal opinions. I doubt you haters have ever dug into a framework and studied the reasons behind it.
You clearly lack of understanding a business mindset too. Fine that there exists some programmer-friendly reasons such as it's not necessary and it could save you staggering 30kb. However try tell this to a customer or non-technical manager:
"I think we should deny using common business standards such as AngularJS, although it's well tested, documented and provides the organization with a broad understanding of coding regulations that makes know-how sharing easy. Instead we should fiddle our own little code library together because that would save us 30kb per new user request."
Not many customers or those managers would really buy in to your arguments.
For small personal projects I'm sure you can argue that not using a framework is a good idea or some not too complex projects. But as the project increases it's important to have community standards and it's a lot more work to start from scratch. It's not only the amount of work that is being done to coding, it's also documentation, standardizations, education and so on. The code part might end up being 30% of the process, where it potentially is around 90%-100% with a framework that already features all this.
Later on when you made a big project and your case has proven it's succes I'm sure you can start working out your own targeted source code.