2 ms·
Frameworks die. It is a fact. Death in this sense means discontinued support and development. It is not difficult to see how this can render any software that d
by michaelmcmillan 11y ago
Frameworks die. It is a fact. Death in this sense means discontinued support and development. It is not difficult to see how this can render any software that depends on a 'dead' framework unstable or even broken with time.
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.
- JustSomeNobody 11y agoWhile 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.
- michaelmcmillan 11y agoThat assumes that protocols and best practices does not change. Not to mention the dependencies the framework relies on.
- matwood 11y agoSoftware 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.
- jb55 11y agoIt would be a stretch to call express a framework. It's just a collection of connect middleware and a few helpers.
- BinaryIdiot 11y agoUsing 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.