Update FAQ

Author: jeromewu

apps/website/docs/faq.md

@@ -1,11 +1,36 @@
 # FAQ
 
+### Why ffmpeg.wasm doesn't support nodejs?
+
+ffmpeg.wasm did support nodejs before 0.12.0, but decided to discontinue nodejs support due to:
+
+- It takes extra effort to maintain nodejs support
+- If you are not in browser, there are a lot of better choices than using WebAssembly for a better performance, ex:
+  - nodejs: https://www.npmjs.com/package/fluent-ffmpeg
+  - react-native: https://github.com/arthenica/ffmpeg-kit
+
+Of course, it is still highly welcome to contribute a nodejs version of ffmpeg.wasm.
+
+### Why ffmpeg.wasm is so slow comparing to ffmpeg?
+
+As of now, WebAssembly is still a lot slower than native, it is possible to further speed up using
+WebAssembly intrinsic, which basically wrting assembly code. It is something we are investigating
+and hope to introduce in the future.
+
+If you are OK with more unstable version of ffmpeg.wasm, using ffmpeg.wasm multithread (mt) version
+can have around 2x speed comparing to single thread (but consume a lot more memory and cpu)
+
+### Is RTSP supported by ffmpeg.wasm?
+
+We are trying to support, but so far WebAssembly itself lack of features like sockets which makes
+it hard to implement RTSP protocol. Possible workarounds are still under investigation.
+
 ### What is the license of ffmpeg.wasm?
 
 There are two components inside ffmpeg.wasm:
 
-- @ffmpeg/ffmpeg (https://github.com/ffmpegwasm/ffmpeg.wasm)
-- @ffmpeg/core (https://github.com/ffmpegwasm/ffmpeg.wasm-core)
+- @ffmpeg/ffmpeg (https://github.com/ffmpegwasm/ffmpeg.wasm/packages/ffmpeg)
+- @ffmpeg/core (https://github.com/ffmpegwasm/ffmpeg.wasm/packages/core)
 
 @ffmpeg/core contains WebAssembly code which is transpiled from original FFmpeg C code with minor modifications, but overall it still following the same licenses as FFmpeg and its external libraries (as each external libraries might have its own license).