I wonder if anyone is using it for anything. I don't mean that in a disrespectful way, but there are a lot of personal programming languages out there that were made because one person for...
I wonder if anyone is using it for anything. I don't mean that in a disrespectful way, but there are a lot of personal programming languages out there that were made because one person for whatever personal reason felt like it, not because it necessarily filled any particularly useful niche or solved a pressing issue in the industry. I've made multiple toy languages myself, and while this seems more mature than anything I've ever made, the motivations seem similar? Just some personal hobby project that you might as well open source in case someone else finds it useful. There aren't any references to any other projects using this language on the website or on github. Smaller programming languages that aren't known in the industry are usually quite eager to advertise any serious project that uses their language.
I was wondering basically the same thing. It's probably just me being out of the loop on what people are doing with low performance embedded devices, but are scripting languages actually desired...
I was wondering basically the same thing. It's probably just me being out of the loop on what people are doing with low performance embedded devices, but are scripting languages actually desired for them? I usually think of scripting languages as useful for portability at the cost of runtime overhead, but if I were targeting a low performance embedded device I don't think I'd need the portability and wouldn't want to spend the limited resources on avoidable overhead.
There are often interesting use cases for wanting to scripting functionality where you might want to deliver a script that isn't in the hot-loop of anything but you'd like dynamism without a full...
There are often interesting use cases for wanting to scripting functionality where you might want to deliver a script that isn't in the hot-loop of anything but you'd like dynamism without a full firmware update. A non-contrived example:
Imagine you are writing firmware for an EV charger, and would like highly dynamic scheduling behaviour. You could try to embed every eventuality in some encoded data payload, or you could reserve some space to deliver a script with usable bindings to time and control registers, and never worry about new use cases again. Hypothetically, some cars just don't follow IEC-61851 properly and so delivering scriptable tweaks to how the max current signal is modulated (which can be done at most once per 5 seconds) would be quite nice. Hypothetically.
The problem with the word embedded is it straddles 8 bit microcontrollers to 64bit arm cores that can happily run Linux. I am assuming this is targetting the more the latter end of the spectrum.
It looks nice enough. It reminds me of Wren. I wonder what people are using this for?
I wonder if anyone is using it for anything. I don't mean that in a disrespectful way, but there are a lot of personal programming languages out there that were made because one person for whatever personal reason felt like it, not because it necessarily filled any particularly useful niche or solved a pressing issue in the industry. I've made multiple toy languages myself, and while this seems more mature than anything I've ever made, the motivations seem similar? Just some personal hobby project that you might as well open source in case someone else finds it useful. There aren't any references to any other projects using this language on the website or on github. Smaller programming languages that aren't known in the industry are usually quite eager to advertise any serious project that uses their language.
I looked at the Github history and there are multiple people contributing, which seems like a positive sign.
I was wondering basically the same thing. It's probably just me being out of the loop on what people are doing with low performance embedded devices, but are scripting languages actually desired for them? I usually think of scripting languages as useful for portability at the cost of runtime overhead, but if I were targeting a low performance embedded device I don't think I'd need the portability and wouldn't want to spend the limited resources on avoidable overhead.
There are often interesting use cases for wanting to scripting functionality where you might want to deliver a script that isn't in the hot-loop of anything but you'd like dynamism without a full firmware update. A non-contrived example:
Imagine you are writing firmware for an EV charger, and would like highly dynamic scheduling behaviour. You could try to embed every eventuality in some encoded data payload, or you could reserve some space to deliver a script with usable bindings to time and control registers, and never worry about new use cases again. Hypothetically, some cars just don't follow IEC-61851 properly and so delivering scriptable tweaks to how the max current signal is modulated (which can be done at most once per 5 seconds) would be quite nice. Hypothetically.
The problem with the word embedded is it straddles 8 bit microcontrollers to 64bit arm cores that can happily run Linux. I am assuming this is targetting the more the latter end of the spectrum.