When do you really need a framework? Hopefully never, but that's actually not the point.
When would you want a framework? When you are working in a larger team (or with multiple teams on the same product) - then a framework will provide a layer of abstraction that allows you to be on the same page without a lot of learning, discussions, etc. - but never let your knowledge of frameworks replace your knowledge of the underlying APIs and processes: that's the point.
I convinced my team to write at least the pages that the user needs to see fast in vanilla JavaScript, though. The rest of the application is currently being rewritten in react (the legacy code we are replacing is in durandal/knockout).
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.
When do you really need a framework? Hopefully never, but that's actually not the point.
When would you want a framework? When you are working in a larger team (or with multiple teams on the same product) - then a framework will provide a layer of abstraction that allows you to be on the same page without a lot of learning, discussions, etc. - but never let your knowledge of frameworks replace your knowledge of the underlying APIs and processes: that's the point.
I convinced my team to write at least the pages that the user needs to see fast in vanilla JavaScript, though. The rest of the application is currently being rewritten in react (the legacy code we are replacing is in durandal/knockout).