A brief list of complain-ey observations
1. npm community is a disaster. So many pieces of abandon-ware or modules that don’t work as advertised. Deep dependency trees are gross and break easily. Thank goodness for npm shrinkwrap making some of it easier to bear.
2. I’ve spent time with too many frameworks/libraries that are too opinionated about how I should try to solve the problem in front of me.
3. Be it functional programmer or the next framework / toolchain of the day, much of the community is too interested in chasing that next hotness rather than asking if it solves a problem with their current setup.
For my current environment, I’ve settled on using knockout, include replace (extremely lightweight templating library compared to polymer), require and grunt. They solve simple problems for me and then get out of my way to let me solve the problems I actually need to focus on. However, if I do some cursory searching, I can find multiple blog posts extolling how my tool chain is dead. I always look into their reasoning in case my own is flawed. However, I’m often faced with nonreasons (or perhaps psychosis). e.g. It’s not compelling for me to switch from grunt to gulp just because the latter is more programming like in it’s design.
I’m also not convinced I need to switch to a transpiled language (though Typescript has tempted me a few times). I’d rather minimize the number of things that could go wrong between me and the js interpreter.
My code so far has proven to be fast, readable, and easy to maintain / bring other engineers up to speed on. I’m sure these other frameworks are good for certain problems, I just wish the community was more discerning about picking the right tool for the job.