Why I’m thankful for JavaScript fatigue

Re:Why I’m thankful for JavaScript fatigue by bhouston on Tuesday November 29, 2016 @01:41PM (#13065161)

I am still angry that ExpressJS got all f-ed up. It was good but it is essentially dead. There seems to be no major replacement for that. I almost wonder if IBM fucked that up intentionally.

[ Parent | on HN ]

Re:Why I’m thankful for JavaScript fatigue by mercer on Tuesday November 29, 2016 @01:49PM (#13065235)

Is it that there are important features still missing, or that there are bugs that aren't fixed?

Reason I'm asking is that I was under the impression that ExpressJS was mostly considered feature-complete (with everything else middleware through NPM), and I'd probably still reach for it the next time I need a Node webserver. I'd rather not make a mistake on that front!

[ Parent | on HN ]

Re:Why I’m thankful for JavaScript fatigue by tannhaeuser on Tuesday November 29, 2016 @05:52PM (#13066885)

express.js doesn't support http/2.

There was an express.js 5 alpha version already last year, but then there was no follow-up since.

Insightful and entertaining discussion from begin of year: https://github.com/expressjs/express/issues/2844

Seems like Doug (maintainer of express.js) could need some help but is he prepared to delegate work?

It has happened before; TJ (former maintainer of express.js) got a burnout and quit.

[ Parent | on HN ]