I personally would be already happy with a fully compliant ES3 code-base but the fact Object.getOwnPropertyDescriptor is there, together with Object.getOwnPropertyNames, mislead me because if there's no way to define enumerability or descriptors these two look like impostors.
That being said, I agree you usually go easy with micro controllers and JS, without bringing absurd alchemies in, but since Espruino supports and promotes the usage of modules, you surely know that module and imported API + getters/setters play usually very well, and give developers the ability to create code that is more pleasant to use.
I just wanted to understand the rational behind those methods and I got it, I also hope those methods could make it without bloating too much the core.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
I personally would be already happy with a fully compliant ES3 code-base but the fact
Object.getOwnPropertyDescriptor
is there, together withObject.getOwnPropertyNames
, mislead me because if there's no way to define enumerability or descriptors these two look like impostors.That being said, I agree you usually go easy with micro controllers and JS, without bringing absurd alchemies in, but since Espruino supports and promotes the usage of modules, you surely know that module and imported API + getters/setters play usually very well, and give developers the ability to create code that is more pleasant to use.
I just wanted to understand the rational behind those methods and I got it, I also hope those methods could make it without bloating too much the core.
Regards