> It's not that simple. If you don't like them, you have no choice. I already addressed that. If you don't like the contemporary front-end tools there are ple

> It's not that simple. If you don't like them, you have no choice. I already addressed that. If you don't like the contemporary front-end tools there are plenty of other programming domains to work in that use other languages and tools. There are also many huge legacy JS systems (especially in the corporate world) that need traditional JS skillsets. > but the complexity is at a point where you need a back-end who understands data types and CS I would argue that front-end developers should already be expected to understand "data types and CS" otherwise they should be earning a designer salary instead of an engineer salary (no disrespect to designers, what they do is also complex, but engineers are paid more on average). > A "Full stack" dev. I disagree. A full stack dev, in addition to front-end, would be expected to also understand how to wire-up back-end services and databases and create abstractions that make this data available for the front-end or other back-end consumers. There aren't really any positions with the exclusive front-end title that also expects any of that. Being able to configure webpack or babel is not "back end" or "full stack", webpack is just a pre-processing tool, not unlike any of the other myriad front-end tools that have existed for years (e.g. sass, less, haml, compass etc)