I'd recommend most people not use express for new projects. It's slower than many alternatives and much less elegant and expressive than most others. The people who wrote express went on to write koa where it's far simpler to compose middleware due to a promise based API. It's kinda sad that so many people cling on to what they left behind and improved upon many years ago.
There may be better alternatives, though I don't think there's an inherit problem with anyone learning express today or implementing it in their projects. I personally learned a lot of new development patterns and concepts from express, and though it may not be the best, it's still a good choice. And if someone thinks they should upgrade, great . Those concepts can easily translate to another framework.
Inflicting yourself and your team with inferior technology is always a problem. It isn't a good choice, any one of the simpler, more powerful and better performing alternatives is a good choice. Express needs to be consigned to history as soon as possible, people only use it because it's already popular, and the more articles written about it the more fuel we put on that fire.
Again, you're point is fine. If you want to chose the best and most efficient tools for your application, awesome. All im saying is theres nothing inheritly wrong with using express. I understand if its a technology thats far phased out of favor in multiple respects and will significantly hinder your application, but with express thats just not the case.
I also disagree, that wasn't my point. Again, all im saying is express doesn't present significant enought issues in comparison to other frameworks for it to have to be phased out.
I think that express does present significant issues and is a poor technology choice. It's unmaintained and hasn't had a release in 6 years, that's just the beginning of its problems: dev.to/romainlanz/why-you-should-d...
That i'll have to agree with, i wouldn't recommend implementing unmaintained technologies into any production application. I wasn't actually aware of that.
I'd recommend most people not use express for new projects. It's slower than many alternatives and much less elegant and expressive than most others. The people who wrote express went on to write koa where it's far simpler to compose middleware due to a promise based API. It's kinda sad that so many people cling on to what they left behind and improved upon many years ago.
There may be better alternatives, though I don't think there's an inherit problem with anyone learning express today or implementing it in their projects. I personally learned a lot of new development patterns and concepts from express, and though it may not be the best, it's still a good choice. And if someone thinks they should upgrade, great . Those concepts can easily translate to another framework.
Inflicting yourself and your team with inferior technology is always a problem. It isn't a good choice, any one of the simpler, more powerful and better performing alternatives is a good choice. Express needs to be consigned to history as soon as possible, people only use it because it's already popular, and the more articles written about it the more fuel we put on that fire.
Again, you're point is fine. If you want to chose the best and most efficient tools for your application, awesome. All im saying is theres nothing inheritly wrong with using express. I understand if its a technology thats far phased out of favor in multiple respects and will significantly hinder your application, but with express thats just not the case.
I disagree that making poor technology choices does not constitute a problem.
I also disagree, that wasn't my point. Again, all im saying is express doesn't present significant enought issues in comparison to other frameworks for it to have to be phased out.
I think that express does present significant issues and is a poor technology choice. It's unmaintained and hasn't had a release in 6 years, that's just the beginning of its problems: dev.to/romainlanz/why-you-should-d...
That i'll have to agree with, i wouldn't recommend implementing unmaintained technologies into any production application. I wasn't actually aware of that.
Ill have to stand corrected on that one.