Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix image ref in FAQ #780

Merged
merged 1 commit into from
Aug 30, 2016
Merged

Fix image ref in FAQ #780

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions doc/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -175,7 +175,7 @@ Windows: `set _JAVA_OPTIONS=-Xmx512M`

Linux: `export _JAVA_OPTIONS=-Xmx512M`

[1]: media/platformtoolset.png
[1]: media/PlatformToolset.png

<a name="nodepromisify"/>
## Using promises instead of callbacks with the device client
Expand All @@ -195,6 +195,6 @@ And there you have it. All the existing functions of the client still exist, and
Events are unchanged, so you still subscribe to those the way you would with the un-promisified client.

<a name="whyunotypescript" />
## Why not use typescript instead of javascript for the SDK?
At the time when the SDK development was started, pure javascript felt like a better choice in order to make contributions as easy as possible for any node developer, whether or not he or she was aware and proficient with typescript.
We regularly reevaluate this decision as we move forward and you are most welcome to provide feedback or contribute by opening issues or pull-requests and help us decide what to do in the future.
## Why not use TypeScript instead of JavaScript for the SDK?
At the time when the SDK development was started, pure JavaScript felt like a better choice in order to make contributions as easy as possible for any Node developer, whether or not he or she was aware and proficient with TypesSript.
We regularly re-evaluate this decision as we move forward and you are most welcome to provide feedback or contribute by opening issues or pull-requests and help us decide what to do in the future.