3 ms·
Maybe there just isn't that much left to do? I've used Express a lot over the years, and I can't think of anything right now that it's missing. I'll be happy if
by pavlov 11y ago
Maybe there just isn't that much left to do? I've used Express a lot over the years, and I can't think of anything right now that it's missing. I'll be happy if it's going to be stable from now on, with no breaking changes.
More fundamentally, I feel the "web framework" doesn't need to be an exciting piece of the stack anymore, like was the case maybe ten years ago. Routing URLs and gluing together middleware doesn't need to be "interesting" or "cutting-edge".
It's great that Express makes it easy, and I'm happy to keep using it regardless of whether there's a version 5 and 6 and 7 in the works.
- marricks 11y agoThe discussion brings up that there is some core functionality that should be added to just have Express keep pace, mainly implementing ES6 changes and supporting HTTP/2 (which some say should just be a new framework). Those are not easy maintenance things to do, and certainly are important.
- pavlov 11y agoIf it were up to me, I'd leave both of those to a different framework. There's nothing in ES6 that warrants breaking Express's compatibility with older runtimes. And HTTP 2.0 probably is better off in a new framework that's designed from scratch for it. (I'm not a great fan of HTTP 2.0 and would rather see Express unburdened by its complexity.)
- ritchiea 11y agoThat's a great point, there is a bit of friction between the idea that if an open source project isn't being actively improved it's dead and Express's mission to be a minimalist framework.
- deleted 11y ago[deleted]