Well, see, you're still only describing interpreted languages, really, with some additional arbitrary criteria. You're welcome to categorize how you like, but it still lacks a real definition, and the meaning varies from one person to the next. Therefore, in terms of policy setting, the term is altogether useless.
Also, I might be missing something you're saying, but Python is very much used via a shell, although you can also execute Python programs directly.
For something more complex or long-lived I go with Ada that IMHO is more suited for writing complex software.
There is a lot of large, complex software for which Python is well-suited. I, like thousands of developers, have created full-blown applications in the language, that are just as maintainable as, say, something written in C++.
Naturally, though, you can (and should) use what you work best in. Just remember that your experience is that: your experience. Plenty of developers are just as successful at making large, complex (and maintainable) software in so-called "scripting languages."
Every language is a tool, and different problems require different tools.
I agree with this much, at least.
I just see Apple's dismissing an entire set of languages, which have been used to deploy production software that people use today, as crummy garden-walling.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Well, see, you're still only describing interpreted languages, really, with some additional arbitrary criteria. You're welcome to categorize how you like, but it still lacks a real definition, and the meaning varies from one person to the next. Therefore, in terms of policy setting, the term is altogether useless.
Also, I might be missing something you're saying, but Python is very much used via a shell, although you can also execute Python programs directly.
There is a lot of large, complex software for which Python is well-suited. I, like thousands of developers, have created full-blown applications in the language, that are just as maintainable as, say, something written in C++.
Naturally, though, you can (and should) use what you work best in. Just remember that your experience is that: your experience. Plenty of developers are just as successful at making large, complex (and maintainable) software in so-called "scripting languages."
I agree with this much, at least.
I just see Apple's dismissing an entire set of languages, which have been used to deploy production software that people use today, as crummy garden-walling.