| ▲ | briffle 3 hours ago |
| You'd be even more impressed if you saw just how little resources they have to use (ram, storage, cpu), or how old of a C standard they have to work with. I have a few friends that work on this. |
|
| ▲ | sib301 3 hours ago | parent | next [-] |
| I am indeed impressed but not at all surprised considering what we used to get to the moon! |
|
| ▲ | ultrarunner 2 hours ago | parent | prev [-] |
| Seems like Java is popular at Garmin. |
| |
| ▲ | nradov an hour ago | parent | next [-] | | And also — sadly — Monkey C. I cannot imagine what possessed them to invent their own scripting language for wearable device apps. It's sort of like JavaScript but worse and with minimal third-party tooling support. https://developer.garmin.com/connect-iq/monkey-c/ | | |
| ▲ | Palomides 8 minutes ago | parent [-] | | it kinda sucks, but with the constraints it's at least understandable. they wanted an extremely lightweight language with a bytecode VM which could be ported to whatever MCUs in 2015, while also strictly limiting the functionality for battery usage reasons (and, uh, product segmentation/limiting third party access). |
| |
| ▲ | ilikehurdles an hour ago | parent | prev [-] | | While I might not trust C code more than Java in life saving equipment, I would trust a median C developer over a Java one. |
|