I think that your article is cool to read but totally out of the reality. People does not build SPA "because is cool".
Throwing a front-end guy in a back-end project (framework or not) is complex and dangerous. Should the front-end guy take a course to learn all the damn basics of back-end development? I don't think so.
Frameworks are evil? No. Developers should look at the source and get how things works? Sure.
Said so, once you get the basics you SHOULD use a framework. A common web app is made of a lot of things (Authentication, Routing, Database, FileSystem) and you can not be good at everything.
You can even create your framework, but i'm pretty sure you will end up looking at the actual one to see how they solved this and that :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think that your article is cool to read but totally out of the reality. People does not build SPA "because is cool".
Throwing a front-end guy in a back-end project (framework or not) is complex and dangerous. Should the front-end guy take a course to learn all the damn basics of back-end development? I don't think so.
Frameworks are evil? No. Developers should look at the source and get how things works? Sure.
Said so, once you get the basics you SHOULD use a framework. A common web app is made of a lot of things (Authentication, Routing, Database, FileSystem) and you can not be good at everything.
You can even create your framework, but i'm pretty sure you will end up looking at the actual one to see how they solved this and that :)