I hear you. Let me share you my findings, knowing that with 10 years only of experience, I found great comfort in this stack. It is not perfect, but it is indee

I hear you. Let me share you my findings, knowing that with 10 years only of experience, I found great comfort in this stack. It is not perfect, but it is indeed better than the previous one for me. Portable - run on mac, windows, linux, others. Embedded - ship with the project. JS friendly / Integrated - for instance you can read and write from JSON/JS/APIs easily. Tons of plugins adapted to web and mobile related concerns. Try to minify CSS with make? Adapted to modern hardware constraints - for instance, sharing global deps is not the default best practice anymore since HD space is not at premium anymore. Multicore/multithread is the default option, not behind a flag. I/O is the modern constraint, not RAM. Limited knowledge to get started - imagine it is the first app you are making in JS, you just learned the diff between the browser and the server ;). Gulp takes you from where you are, make requires knowledge of Linux, bash, env variables, probably apt-get/yum, make itself. A place you have never been before. Modern doc - it's my opinion, but man is an awful doc interface. No quickstart, it has a TOC, not a menu and no search bar sig. Innovative 'cause no legacy - we wouldn't have investigated hot reloading, smart watch mode, "better" pkg mgmt. Easier to debug. No context switch ...