Is Express.js dying? • Hacker News Board

Re: Is Express.js dying?

#11

Post by LukeB_UK » Sun, Jan 17, 2016, 3:42 PM UTC

ctmkpp wrote: post #9

Clickbait. Express.js is not dying. At all. It is being very much actively worked on by some of the hardest working maintainers and contributors. Express.js is actually a combination of various modules. If you want to see the work being done, go to those individual modules.

It was a question asked by someone on the Express Github repo. How is that clickbait exactly?

Re: Is Express.js dying?

#12

Post by bovermyer » Sun, Jan 17, 2016, 3:43 PM UTC

Well, that certainly seems to be a ton of drama. I don't want to bad mouth any of the people involved, regardless of their affiliations, so I'll just say that I'm not sure what good will come of this spat.

Re: Is Express.js dying?

#13

Post by LukeB_UK » Sun, Jan 17, 2016, 3:44 PM UTC

niftylettuce wrote: post #4

Just use koa@next, it's awesome. ES6/ES7 with Babel, Flowconfig, and more.

Another good alternative is Hapi: http://hapijs.com/

Re: Is Express.js dying?

#14

Post by bryanlarsen » Sun, Jan 17, 2016, 3:44 PM UTC

AustinG08 wrote: post #7

I've been building an app using Express over the past 9 months and this gives me pause. It seems like IBM wants to have its cake and eat it too. Should be interesting to see how it all plays out, but is building an app on Express a liability? I have been contemplating switching to hapi, maybe this is a good time to explore that option.

What's giving you pause? According to the link, Express is undergoing extensive and active development...

Re: Is Express.js dying?

#15

Post by ebbv » Sun, Jan 17, 2016, 3:44 PM UTC

Popcorn aspect aside to the drama in this thread, this is a great example of how companies should NOT behave in relationship to open source projects. They simultaneously made the maintainer feel unvalued and like his role in the project was being held hostage, while sending BS sounding mixed messages to the community.

Re: Is Express.js dying?

#16

Post by DiabloD3 » Sun, Jan 17, 2016, 3:45 PM UTC

ctmkpp wrote: post #9

Clickbait. Express.js is not dying. At all. It is being very much actively worked on by some of the hardest working maintainers and contributors. Express.js is actually a combination of various modules. If you want to see the work being done, go to those individual modules.

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.

Re: Is Express.js dying?

#17

Post by endemic » Sun, Jan 17, 2016, 3:47 PM UTC

foldr wrote: post #8

It's not the cool web framework for Node any more. I don't think it's going to "die" in the sense that existing express applications are going to be impossible to maintain any time soon.

Agreed. The real question is, can you still get stuff done using it? Will other developers be familiar with its conventions? "Yes" on both counts.

Re: Is Express.js dying?

#18

Post by api » Sun, Jan 17, 2016, 3:48 PM UTC

Of course. It's the web, where we rewrite the entire stack every two years.

Re: Is Express.js dying?

#19

Post by [deleted] » Sun, Jan 17, 2016, 3:52 PM UTC

bryanlarsen wrote: post #14

AustinG08 wrote: post #7

I've been building an app using Express over the past 9 months and this gives me pause. It seems like IBM wants to have its cake and eat it too. Should be interesting to see how it all plays out, but is building an app on Express a liability? I have been contemplating switching to hapi, maybe this is a good time to explore that option.

What's giving you pause? According to the link, Express is undergoing extensive and active development...

[deleted]

Re: Is Express.js dying?

#20

Post by AustinG08 » Sun, Jan 17, 2016, 3:52 PM UTC

bryanlarsen wrote: post #14

AustinG08 wrote: post #7

I've been building an app using Express over the past 9 months and this gives me pause. It seems like IBM wants to have its cake and eat it too. Should be interesting to see how it all plays out, but is building an app on Express a liability? I have been contemplating switching to hapi, maybe this is a good time to explore that option.

What's giving you pause? According to the link, Express is undergoing extensive and active development...

After reading that entire thread, it seems to be that IBM/Strongloop wants to maintain ownership of the project without contributing the resources. They expect dougwilson to continue running the project but he doesn't want to unless it is under the expressjs organization or something like that.

Apparently IBM threw a few guys into discovery on the project a few weeks ago and they may actively get involved, but it is yet to be seen. Maybe IBM just wants to own it and doesn't care what happens to the project one way or the next. I have no way of knowing what IBM's intentions are, and I think that's the concern of the maintainer, dougwilson.