>>7 I don't mind what you did for Tecgraf, that's the proper way to create a scripting language: for it's use case. But when others say `Python, Perl, or Javashit` they mean they want to use these as crutches, when they
should be designing what they need, and if
scripting is necessary at all.
Take for example Django, Mojolicious, and AngularJS: these frameworks don't solve the inherit problem of organizing what a
web server should display. For that, you're supposed to edit and use you daemon, and adapt to the data[store] you working
for.
So if your company requires fast manipulable responses from a SQL-like database, you shape the HTTPdaemon to yield exactly those results: thus HTSQL, BCHS, OHS, etc..
It's the `
worse is profitable business model that broke the confidentiality of programs made for clients: you can't ever solve the problem, if not you run out the business.
Thus the dark age of "scripting languages" as a library was born.
To answer you question: none: if your business requires it, it's in the business of debt.
Shells were and should be last scripting ever needed, since they are for personal use, not (((general))) use.