4 ms·
> There hasn't been meaningful updates to Express in a long time. Because for the most part - it doesn't need them. Can you build a better express? Maybe. L
by horsawlarway 4y ago
> There hasn't been meaningful updates to Express in a long time.
Because for the most part - it doesn't need them.
Can you build a better express? Maybe. Lots of folks are trying that still, and you're welcome to use the tooling they put out.
Is express dead? Hell no.
Express is well documented, well supported, getting security patches, and comes up entirely clean for a new install (including most of the optional packages you might add).
Express has some sharp edges (it's been mentioned plenty above, but mainly because the framework predates the wide adoption of native promises in the JS space), but again, they're well known and relatively straight forward to work around.
---
Long story short, this:
> It doesn't. That's the whole point. Software is always evolving and I doubt it's even close to complete. There hasn't been meaningful updates to Express in a long time. Why do people use it and/or promote it as a standard?
Is an ignorant take. People promote it because it's a good tool.
Next you'll be telling me that I shouldn't use Bash because Bash 5.0 came out in 2018 and only got two minor point releases over the next 5 years. But that sounds dumb, huh?
- re-thc 4y ago> Next you'll be telling me that I shouldn't use Bash because Bash 5.0 came out in 2018 and only got two minor point releases over the next 5 years. But that sounds dumb, huh? What's dumb is not being able to tell the difference. It's not about the numbers. https://git.savannah.gnu.org/cgit/bash.git/ https://git.savannah.gnu.org/cgit/bash.git/ shows there are constant updates. Things are being worked on. Your example proves my whole point. There are updates every year for many years. Express? Not so. There are many gaps in its history. And for a tool like Express that has way more surface area it is in need of a lot more testing and updating e.g. if NodeJs changes something it breaks. Does Bash need to make sure it works with HTTP3, Brotli or many other things that came out? No. > Because for the most part - it doesn't need them. Right, let's go back to the Stone Age. You don't need clothes either - just a leaf. You're just so dismissive on innovation then why bother? You don't even need NodeJs. Back to assembly and punch cards... > Is an ignorant take. Yes, yours. As shown above by your example. > People promote it because it's a good tool. And how do you know that? Where are the stats? Or people just google for NodeJs server, see the top response being Express and just do that. The cycle then repeats. Have people promoting it actually benchmarked, compared and investigated all the tools before making this informed decision? I'm sure you've heard from each and everyone 1 of them to know the answer eh.