Skip to content

Commit

Permalink
Update conclusion
Browse files Browse the repository at this point in the history
  • Loading branch information
@kgryte
kgryte committed Feb 3, 2017
1 parent 0362a2a commit d61bd65
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion FAQ.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,7 @@ Native [add-ons][node-add-ons] have several disadvantages:

1. __Debugging__: debugging and instrumentation require separate compilation pathways. JavaScript implementations have the luxury of abundant tooling for dynamic inspection and instrumentation. The same cannot be said for native [add-ons][node-add-ons].

Despite the disadvantages articulated above, this project __does__ include Node.js native [add-ons][node-add-ons] and will continue to do so. However, each [add-on][node-add-ons] must include a JavaScript fallback in order to address cross-platform portability. While beneficial, native [add-ons][node-add-ons] are only part of what must be a more comprehensive solution to provide numeric computing facilities to Node.js and more generally JavaScript.
Despite the disadvantages articulated above, this project __does__ include Node.js native [add-ons][node-add-ons] and will continue to do so. However, each [add-on][node-add-ons] must include a JavaScript fallback in order to address cross-platform portability. While beneficial, native [add-ons][node-add-ons] are only part of what must be a more comprehensive solution to providing numeric computing facilities to Node.js, JavaScript, and the Web.

<!-- </faq-question> -->

Expand Down

0 comments on commit d61bd65

Please sign in to comment.