It could be like python, same thing happened with angularjs. "Breaking changes" seems to be a very difficult part of building languages/frameworks, and I don't know how best to deal with it. I think it needs to be planned for though, otherwise it gets really hard to justify making improvements. I'll happily try and brainstorm ideas for how to do it...
Switchable features sounds like an extra overhead in terms of your workload and in terms of code size. And an additional confusion for new users. I think for it to work you'd really need to commit to having features be "on" or "off", but have an extremely minimal and "not technically supported, but available for advanced users" way of switching them.
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.
It could be like python, same thing happened with angularjs. "Breaking changes" seems to be a very difficult part of building languages/frameworks, and I don't know how best to deal with it. I think it needs to be planned for though, otherwise it gets really hard to justify making improvements. I'll happily try and brainstorm ideas for how to do it...
Switchable features sounds like an extra overhead in terms of your workload and in terms of code size. And an additional confusion for new users. I think for it to work you'd really need to commit to having features be "on" or "off", but have an extremely minimal and "not technically supported, but available for advanced users" way of switching them.