4 ms·
These are all potential wins. However, having tried the tour and the example code, a concern is the memory usage on the client side. Even for simple examples,
by nemoniac 15y ago
These are all potential wins. However, having tried the tour and the example code, a concern is the memory usage on the client side. Even for simple examples, it's very high. Prohibitively high for mobile usage. Would you care to comment on this? Is it something that can be improved upon in future versions or is it inherent to the approach?
- hbbio 15y agoCurrently, we did not work a lot on reducing the size of the generated JavaScript code nor the memory usage. There are definitely huge potential gains in that space, and we planned to focus on this once we have the Node.js backend: Benefits will be doubled.