3 ms·

Your remark seems to match what I've observed during the reverse engineering part of the project. With magic constants like `0xc0debabe` [0] or opcodes like `ca

Your remark seems to match what I've observed during the reverse engineering part of the project. With magic constants like `0xc0debabe` [0] or opcodes like `canhazplz` [1] that you would expect more from a student CS project for instance. [0]: https://github.com/anvilsecure/garmin-ciq-app-research/blob/main/ciq.ksy#L48 https://github.com/anvilsecure/garmin-ciq-app-research/blob/... [1]: https://github.com/anvilsecure/garmin-ciq-app-research/blob/main/ciq.ksy#L380 https://github.com/anvilsecure/garmin-ciq-app-research/blob/...

qrohlf 3y ago
Yeah, exactly. THAI_SPICY_HOT was just one of many signals that I got that the MonkeyC project could have very much started out as an intern project or similar. The list of languages the documentation claims MonkeyC takes inspiration from also denotes a certain type of programmer background: > C, Java™, JavaScript, Python™, Lua, Ruby, and PHP all influenced the design for Monkey C (source: https://developer.garmin.com/connect-iq/monkey-c/ https://developer.garmin.com/connect-iq/monkey-c/) If I asked an embedded hardware expert to design a novel programming language for my highly resource-constrained wearables platform, I would be very surprised if these were the language touch points they used as their references in the design brief.