3 ms·
It doesn't have to actually be CLI. It does need to be repeatable (by you) and reproducible (by others), and it does need to go through a known API. Those req
by bradknowles 9y ago
It doesn't have to actually be CLI. It does need to be repeatable (by you) and reproducible (by others), and it does need to go through a known API.
Those requirements will tend to drive you towards a CLI solution as the easiest/best available, but if you could get those requirements satisfied in any other programmatic way, then I think you'd probably be okay.
But then the problem becomes, can you do programming from the GUI? I think that's actually a lot harder to do.
- joe_the_user 9y agoThose requirements will tend to drive you towards a CLI solution as the easiest/best available, but if you could get those requirements satisfied in any other programmatic way, then I think you'd probably be okay. Theoretically you can do these some other way. In practice, the CLI is the only way that's remained. The thing with the CLI is it is quite easy to a new component to it whereas someone creating a little app for a little task as a GUI tends to create a "cul-de-sac", stovepipe, a program with not relation to any other program. So third approach would be great but it doesn't seem to be getting any closer.
- Izkata 9y agoSikuliX is halfway between CLI and GUI: https://avleonov.com/2017/02/13/sikulix-the-last-chance-for-automation/ https://avleonov.com/2017/02/13/sikulix-the-last-chance-for-...
- CyberDildonics 9y agoPrograms like Nuke, Houdini and Touch Designer have been doing this for years specific to graphics - this is trying to be more generalized: https://github.com/LiveAsynchronousVisualizedArchitecture/lava/blob/master/README.md https://github.com/LiveAsynchronousVisualizedArchitecture/la...