3 ms·
I’m very impressed by the level of technical detail in this post. I’m somewhat surprised garmin made their own language for apps but considering the low power
by edude03 3y ago
I’m very impressed by the level of technical detail in this post.
I’m somewhat surprised garmin made their own language for apps but considering the low power processors they target was their any other options?
- heywhatupboys 3y agostrict subset of JVM, like the old days of mobile phones and SIM cards
- depierre 3y agoAuthor here. Thanks! I am surprised as well, especially considering that their compiler does little to actually no optimization. For instance, it won't remove dead code or unused variables. These seem like low hanging fruits that could save memory and cycles on low power devices.
- xebbler 3y agoPebble ran third party native apps (generally written in C) sandboxed via the ARM SVC/USR-mode privilege system, integrated with the onboard MPU. Fitbit - after hiring many Pebble staff - supports third party apps written in JavaScript. These run on the pre-existing JerryScript engine, and are still sandboxed on the native side should the VM have holes. This made it much easier to get started as a developer, but imposed an upper limit on app performance vs. the native apps seen on Pebble.