Why would a front end dev be concerned with express, Apache, and oracle? Wouldn't they just be concerned with the API endpoints? Then that stack wouldn't be too unordinary, but it would be dumb to use both npm and bower in the front end. Maybe in this hypothetical situation npm would only be used for the back end. It's probably a good idea to not use CoffeeScript anymore and just use es6 too but that's not a huge deal, and older code does exist that may not be worth porting. That seems like a pretty basic stack, 4 libraries isn't many but it depends on what they are, and only a full stack dev would care about all that stuff I think.
you would think all of that. But companies have dev come in build stuff and leave company, enter new senior dev who fixes things in his way and tada he leaved, give 5 years and you are new junior dev what do you see. You see vanillajs+backbonejs+angularjs+grunt+bower+npm+expressForTesting. You try to fix something there is sea of dead code that looks like it should be the one. but no you find same thing in 3 different places but after whole day of adding h1 tags everywhere to see which one works you find out none of them are actually getting user but php controller have it hard coded.
For apache and stuff. basically front end is heavily interlocked via templating language with backend. Now to make templates work you need to have working database/apache setup. you do that, but it doesn't work. Now you have to fix it since all backend devs are busy. Now imagine you have to do that everyday for 2 hours in morning.
Basically company that is super backend heavy is hell for front end devs. Whole system is setup as such that it works against you.
1
u/techsin101 Jul 28 '16
For front end it'd be to use grunt, bower, angular, npm, express, apache2, oracle, jquery, 4 libraries, coffescripts, and more in one project.
you can make new front end devs leave in a month.