For a longtime, analysts have been calling for a cross platform scripting language for use in all areas of computing. This universal scripting language is needed because web development, distributed processing, network system management and software agents among other tasks - all would work much better if a universal, standard, and cross platform scripting language was available. A GPSL-General Purpose Scripting Language would help to replace the current hodge-podge of WSH, the Unix shells, Rexx, Perl, Python and at least a dozen other languages that currently must be mixed and matched to deliver distributed applications.
CrossPlatform Scripting Princes
Let's look at some of the charaecteristics of this scripting language. First and foremost, it should be Open Source and cross platform. However, being Open Source does not demand that it be free (see below). It should be an interpreted language, possibly compilable and running in a small footprint so it can be used on PDA, mobile and other evolving computing devices. Being an interpreted script with a small footprint helps to insure that the scripting tool will remain orthogonal and act as a complement to the major compiled programming languages.
The GPSL would be Open but could be subject to a modest licensing fee, say $1 per year per usage in an ISV's products. Take DBMS vendors - assume there are 300 Million licensed DBMS users in the world and 1/3 of them were to operate DBMS that used the GPSL - this would generate operating revenues of $100 million for the GPSL development and standards organization.
Finally, to add teeth to the GPSL standards, it should have a requirement that all ISV users of the GPSL provide their users with a standards conformance toggle or "undo" switch. This software switch would ensure that the GPSL standard code could be easily adhered to throughout any application generated by the ISVs software that uses the GPSL scripting tool. This in turn, would allow individual ISVs to create variants and proprietary extensions to the language. This allows 3rd party innovation, but also prevent "run-ahead" proprietary extensions which are silently and automatically generated into users code. Developers and users would always have an easy "undo switch" from using proprietary and potentially non-interoperable code and/or output.
The four top priorities for CEOs, CIOs and IT managers for the past decade
have been revolving among these issues:
Jacques Surveyer is a consultant and photographer; see the latter at thePhotoFinishes.com.