You are reading a single comment by @charlie and its replies. Click here to read the full conversation.
  • At this stage I am probably underestimating the memory constraints of the system.

    quite likely, and maybe also CPU speed and I/O speed, check this https://www.espruino.com/Performance to get better picture

    Given the hardware constraints I am starting to see why javascript might not be the best language for watch development.

    I don't see anything better that offers the simplicity, flexibility and extensibility while still having low memory requirements. Also the asynchronous nature of js make things easier than using languages like micropython or lua.

  • I don't see anything better that offers the simplicity, flexibility and extensibility while still having low memory requirements. Also the asynchronous nature of js make things easier than using languages like micropython or lua.

    Not sure I agree with the async part, I think the introduction of async await layer to wrap promises helps, but promises are a fairly hard concept to get head around if new to programming (and the code gets very messy if still use promise.then syntax), something which is apparent in user app code when timeouts are being used instead of async functions, and I suspect are causing some of freezing issues I have seen briefly seen in the forum)...but I am a python fanboy so I will defend it against all reason.

About

Avatar for charlie @charlie started