3 ms·

My biggest takeaway from this article is that Netflix is moving from Express to Restify, and I look forward to watching the massive uptick this has on https://g

by ecaron 12y ago

My biggest takeaway from this article is that Netflix is moving from Express to Restify, and I look forward to watching the massive uptick this has on https://github.com/mcavage/node-restify/graphs/contributors https://github.com/mcavage/node-restify/graphs/contributors

sadkingbilly 12y ago
Yes, but their original bug was from dynamically loading routes from an external source. I don't see how Express is to blame for this. Moving to Restify is not a solution, but they state having different reasons for moving (support for bunyan logging? But Express already supports this too).
- ecnahc515 12y ago
  the bug was related to dynamically loading routes, but the true cause was that express allowed duplicate handlers. They were loading routes dynamically correctly, that wasn't a problem, it was that when doing that express let them duplicate routes.
  - jonny_eh 12y ago
    If they were loading duplicate routes, how was it they were "loading routes dynamically correctly"?
  - sisk 12y ago
    That's a feature. From the API docs: > Multiple callbacks may be given; all are treated equally, and behave just like middleware. The only exception is that these callbacks may invoke next('route') to bypass the remaining route callback(s). This mechanism can be used to perform pre-conditions on a route, then pass control to subsequent routes if there's no reason to proceed with the current route.
gaving 12y ago
not exactly highly endorsed https://twitter.com/tjholowaychuk/status/382084838179614721 https://twitter.com/tjholowaychuk/status/382084838179614721
- dagw 12y ago
  While I kind of agree the restify gives you "almost nothing" when compared to some larger frameworks, in my experience "almost nothing" is basically all I need from my framework when writing REST APIs and restify has had me covered every time.

3 ms·

My biggest takeaway from this article is that Netflix is moving from Express to Restify, and I look forward to watching the massive uptick this has on https://g

by ecaron 12y ago

sadkingbilly 12y ago
Yes, but their original bug was from dynamically loading routes from an external source. I don't see how Express is to blame for this. Moving to Restify is not a solution, but they state having different reasons for moving (support for bunyan logging? But Express already supports this too).
- ecnahc515 12y ago
  the bug was related to dynamically loading routes, but the true cause was that express allowed duplicate handlers. They were loading routes dynamically correctly, that wasn't a problem, it was that when doing that express let them duplicate routes.
  - jonny_eh 12y ago
    If they were loading duplicate routes, how was it they were "loading routes dynamically correctly"?
  - sisk 12y ago
    That's a feature. From the API docs: > Multiple callbacks may be given; all are treated equally, and behave just like middleware. The only exception is that these callbacks may invoke next('route') to bypass the remaining route callback(s). This mechanism can be used to perform pre-conditions on a route, then pass control to subsequent routes if there's no reason to proceed with the current route.
gaving 12y ago
not exactly highly endorsed https://twitter.com/tjholowaychuk/status/382084838179614721 https://twitter.com/tjholowaychuk/status/382084838179614721
- dagw 12y ago
  While I kind of agree the restify gives you "almost nothing" when compared to some larger frameworks, in my experience "almost nothing" is basically all I need from my framework when writing REST APIs and restify has had me covered every time.