-
Notifications
You must be signed in to change notification settings - Fork 64
FAQ
Q: What is the prupose of ɳidium?
A: Creating high performance JavaScript applications without the browser stack.
Q: Does ɳidium require a GPU?
A: Yes
Q: What platform ɳidium currently support?
A: As of today, ɳidium runs on linux and OSX. The port to Android is still a work in progress. Windows port is in our top priority list.
Feel free to contact us if you need information on a specific platform.
Q: Can I use ɳidium as a kind of game-engine?
A: Yes. It does an amazing job at rendering, but there is no physic-engine behind, or any 3D engine built in.
Q: Is ɳidium a kind of browser?
A: Yes & No. Nidium has similarities with a browser, but it's definitely not a browser (No HTML)
Q: How does it compare to node-webkit or electron ?
A: ɳidium is not built on top of a browser.
Q: How does it compare to flash?
A: Both ɳidium and flash use vector graphics, but ɳidium is not a browser plugin. With ɳidium, you write application using JavaScript instead of ActionScript. And of course, it's open source :)
Q: How does it compare to openframeworks?
A: ɳidium lets you use plain JavaScript instead of C++.
Q: Why did you make a server version?
A: The core components were designed to be reused as a library. We needed a very fast, low latency, robust server. As the async network layer is very fast and we dogfooded ɳidium to outperform Node.js/Socket.IO. This server has been tested in production environement (>810M requests / day). Off course, ɳidium (frontend) has the same built-in server, which can give your application amazing posibilities.
Q: Will there be a kind of comet or push module?
A: Yes! This project is build around the networklayer that was also used in the APE-Project. You can expect some cool stuffs in a near future.
Q: Can I use ES6 features?
A: Yes several. Currently we are focussing to add more features and modules, but we will definitely extend es6 support.
Q: Can I reuse Node.js modules?
A: Yes & No. Nidium has support for require() but NodeJS API has not been ported to Nidium. So this means that any modules that use NodeJS specific API/features will not work.
Q: Any plan to make ɳidium compatible with NodeJS API?
A: Yes, but this is not yet on our top priority list.
Q: What is this konstrucktor.py?
A: That is a nifty tool to download dependencies, generate gyp files, and pass configuration flags around.
Q: How can I help?
A: Head over our slack channel and come chat with us :)