Re:Is Express.js dying?
by JustSomeNobody on Sunday January 17, 2016 @10:57AM
(#10919810)
While I realize it may not be the case here, discontinued development doesn't necessarily mean death. Sometimes it means "done". I don't think enough developers get that.
Software can only be done if the environment it runs in remains static. Any software dealing with the web can never be done as the environment it runs in is constantly evolving.
Re:Is Express.js dying?
by michaelmcmillan on Sunday January 17, 2016 @10:59AM
(#10919817)
That assumes that protocols and best practices does not change. Not to mention the dependencies the framework relies on.
It would be a stretch to call express a framework. It's just a collection of connect middleware and a few helpers.
Re:Is Express.js dying?
by BinaryIdiot on Sunday January 17, 2016 @12:10PM
(#10920061)
Using that argument you could almost never call something a framework of it uses a lot of libraries under the hood to make what it's doing easier. I see nothing wrong with the usage.
I have experienced exactly this multiple times. In fact, I am extremely aware of this when I start a new project. Perhaps especially when I am dealing with frameworks like Express, Django or Ruby on Rails.
If I recall correctly, Gary Bernhardt, said it well: "Treat Rails like a disease and isolate yourself." You can replace "Rails" with any popular framework. Yourself in this quote referes to the business logic of your system.