Show HN: Expresso: A faster, drop-in replacement for the ExpressJS router
1–4 of 4 posts
Re: Show HN: Expresso: A faster, drop-in replacement for the ExpressJS router
#2Not to mention standard community/ ecosystem/ migration risk.
Re: Show HN: Expresso: A faster, drop-in replacement for the ExpressJS router
#3Nice work. It always gives me heart burn when the docs say “basically the same” because now I have to do some digging to determine if the performance gains are worth my understanding if I am inside the “basically same” use case or in the “unfortunately slightly different or unsupported” use case. Not to mention standard community/ ecosystem/ migration risk.
Re: Show HN: Expresso: A faster, drop-in replacement for the ExpressJS router
#4Nice work. It always gives me heart burn when the docs say “basically the same” because now I have to do some digging to determine if the performance gains are worth my understanding if I am inside the “basically same” use case or in the “unfortunately slightly different or unsupported” use case. Not to mention standard community/ ecosystem/ migration risk.
I think it’s likely an easy switch for most people. But I would not over look the documentation of when does it not make sense. This usually engenders more confidence in the maintainers vision or perspective on how they achieve the performance gains. Since after all so much of the work you are doing comes down to making trade offs.