[DiabloD3]

I actually have to agree with this. It seems like some semi-political debate about how one guy left and they don't like the direction the project is headed, but it is clearly not dying.

I've flagged it for mod review, I'm not sure if this should be on the front page, it doesn't seem like it meets the requirements for HN.

[jnbiche]

Please don't flag stuff like this. You're treating HNers like children. Lots of us use frameworks/libraries like Express for major projects, so it's important we see critical project sustainability information like this. And we can figure it out ourselves.

If you don't think it's front-page worthy, then just don't upvote. Flagging is meant for off-topic or spam, which this is clearly not.

[quicklyfrozen]

That one guy is the only one currently contributing code (a slight exaggeration, but very slight).

That info by itself seems HN worthy as many of us have likely used Express as the "safe" choice when starting a new project. Time to rethink that...

[mikermcneil]

Perhaps, but I can assure you that Express 3 and Express 4 are completely safe. The interface set up by Express is depended on by far too many companies and other frameworks for that to not be the case -- for instance, even though Express 3 is officially unmaintained by Strongloop, the Sails core team has committed to taking over critical patches.

As for the future of Express: I've only had the opportunity to get together with Doug in person once, but we've talked about this a few times in the past. I can guarantee you the last thing he wants is drama, so I'll leave the ball completely in his court there.

I will say this though: keep an eye on Doug's federated projects (jshttp and Pillar). Whether or not the various pieces are released as Express 5 or not, the _code base_ is still improving and becoming increasingly standardized, regardless of the monicker. More on that: https://github.com/balderdashy/sails/pull/3235#issuecomment-...