&gt; Will JavaScript take over front-end?<p>Has it not? A more appropriate question would be &quot;When will it step down?&quot;<p>&gt; it takes 40% more development time to finish a project with AngularJS than without using it.<p>And by &quot;without using it&quot;, does it mean you write in vanilla JS? I believe you jumped into conclusions way too early. Working with any technology will take long. It&#x27;s not the actual writing of code that will take long, it&#x27;s the learning (if you&#x27;re a total noob), setting up (if you don&#x27;t have scaffolding tools), and debugging (if you don&#x27;t have tools). The actual work is just a fraction of what you&#x27;re actually doing.<p>&gt; How was your experience with React or any other<p>If you mean React alone, then it&#x27;s like Angular with directives... alone. You&#x27;ll have to debate on your router, your data flow library, your server-communication layer, your build tooling, your process. It&#x27;s all the same thing under the guise of a different syntax.<p>&gt; Should I invest more time to keep me updated with one of them?<p>Get to know all the libraries, but never try to use them all. Choose one and get things done.<p>&gt; I still think, front-end should just present the information, not the whole application logic.<p>It&#x27;s like saying JS should have stayed on the browser, but wait! There&#x27;s Node.js (server), Espruino (hardware), FirefoxOS (OS), PhoneGap (mobile), NW.js (desktop). If everyone was thinking the way you do, these would have never been invented.