From: janis_papanagnou+ng@hotmail.com   
      
   On 20.10.2025 23:44, BGB wrote:   
   > [...]   
   >   
   > Decided to leave off going into a longer topic about language-design   
   > tradeoffs.   
      
   (I changed the subject for you. But wouldn't it have been better to   
   just open a new thread?)   
      
   >   
   > And the seemingly often overlooked practical distinctions between the   
   > design of serious/implementation languages and light-duty script   
   > languages,   
      
   An interesting distinction, though I'm exactly sure what you have in   
   mind when saying "light-duty" here.   
      
   One commonly used script language that I use on a daily basis is the   
   Unix Shell. Is that "light-duty" in your categories? (Not for me, to   
   be sure.)   
      
   In some courses I gave in the 1990's my dogma had always been (and   
   still is) to approach "scripting" as [seriously] "programming"!   
   And apply all the software development principles also when writing   
   programs in "scripting" languages.   
      
      
   > where blurring this line can result in languages that aren't   
   > particularly well suited to either use-case.   
   >   
   > Or, in effect:   
   >   C, C++, C#, Java, etc:   
   >     Mostly sensible designs for implementation languages.   
   >     Where: Language you would actually use for non-trivial code.   
   >   BASIC, Emacs Lisp, etc:   
   >     Sensible for script languages.   
      
   (You're probably talking about newer BASIC dialects. - But there's   
   anyway so many different BASIC dialects existing that it wouldn't   
   appear to me to choose this thing in the first place.)   
      
   >     Or, language used for behaviors or program-control / events.   
   >   JavaScript, ActionScript, etc:   
   >     Sort of an awkward middle ground.   
   >   
   > Though, JS and AS and similar, are still better than, say:   
   >   Trying to use Java or similar for high level event scripting;   
      
   I've been using JS in many toy projects because I needed dynamic   
   web-content and didn't have a managed server. If I've had one I'd   
   use (despite my dislike) even Java, if I could only avoid this   
   crooked, error prone, and inconsistent JS.   
      
   > [...]   
      
   (But that's obviously more a subthread for other folks, those that   
   like talking about BASIC and JS.)   
      
   Janis   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)