Interesting, thanks for the explanation.
"Use JSX to declare your pipeline, an XML like syntax. No more staring at YAML."
How is this better?
I've noticed a lot of people moving back to npm from yarn recently. Is something triggering this?
Of course, thanks for pointing that out.
This looks cool. Only looked at it quickly but could it use a nicer syntax for multiple mixins instead of a bunch of wrapped functions?
Honestly, I was ready to disagree with him but everything he said is (probably) true. I think it might have been easier to read if he presented his main point upfront: don't set up linters to cry fowl when using let instead of const or automatically convert to const.
Yea my point was that the title is a little pretentious. I bet it's just because you're very excited for NestJS. I am happy for you and don't mean to rain on your parade. It's just a little tiring for me to see new frameworks solve problems that I (and others on my team) don't have when there are other problems I would love to see solved. For example, Node still doesn't have a batteries-included framework that has community support like Rails and Django. Express has stood the test of time and is great for what it is, but it will never fill that role.
I haven’t been waiting for this. I’ve been pretty happy with Express actually.