Are frameworks like Ember.js overcomplicating web development with overly excessive file structures and poor compatability [on hold]

The Ember project I made was 15+ sets of html/js-controller/js-view/js-model pages and it took 5-7 people and OVER A YEAR to code. It's still not close to being done

At a different company, 1 frontend (myself) and 1 backend were able to make 5 webpages, all more complex than the 15 page project in about a month using 5 separate html pages, but merging the javascript into the HTML pages. So instead of one html page,1 model.js, 1 controller.js, and 1 view.js we combined those 3 js files into the html file.

The Emberjs project has so many files that it is a nightmare to navigate through.

Why using raw js/html was better: For the Raw project we didnt split up the javascript and html. For every html page, the javascript was right there on the same .html . This made it SO MUCH EASIER and more organized. I didnt have to search through files, i just pressed COMMAND-F and found what I wanted. In Ember.js some actions were repeated on the controller and the view. These seems like a huge waste to me.

Why split all of the javascript up into separate pages? It makes everything so much longer and so much more complicated to sort through. It's like some coders forget that CMD-F exists.

So why use Ember? Almost all of the problems that would hold us up on Ember were due to Ember/handlebars giving vague console errors or ember not working correctly with some other KEY element of HTML5 or javascript/jquery. We ran into none of these problems when we cut off Ember.js which is why the project was quicker and cleaner.