I'm not familiar with JIT ecosystems. by JIT this Just In Time correct?Are you aware of native modules in JIT ecosystems? They have a top level API which then gets translated to the correct target implementation. So the underlying environment is abstracted. All you have to do is port the API to the target environment, where the implementation just has to get the job done correctly.
One thing to note, is some environments may be more responsive in terms of command rate. This will create a difference, but you should only be as strong as your weakest link.
In terms of command rates since this is a shell, command input is only as fast as a human (presumable) can enter a command into the system. all the processing with what to do with that input is were I'm looking to make adjustments and changes.
It's this order that makes me think would it be better if built in command could be replaced. All the built in commands are basic and simple they are meant to meet the minimal requirement of operation. With my current checks this simple commands can never be replaced with user code of the same name. Swapping the order would make it possible to mask the built in firmware commands with software versions. I see the value in this but is it a good idea. And if that is a good idea does it again make sense to make even bigger changes and make the command parser a script that a user could create making all sorts of changes possible.
Statistics: Posted by DarkElvenAngel — Sat Nov 30, 2024 11:11 pm