I like PHP a lot. It's my favorite programming language. That's not to
say that I'd like to see it grow more or for derivatives to come from
it. For me, the ideal programming language would be:
* Would take the name of Polar instead of PHP.
* Syntacticaly exactly like PHP, but would be much faster on string
handling and would swap "." for "->".
* Has all the same modules of PHP but would have extremely easy-to-use
Qt and GTK modules (a way to build cross-platform GUIs), have fast ways
to build ssh/telnet data entry or cash register apps for VT100 or VT220
terminals, have faster ways to build HTML tables, have cookie routines
that are encrypted (fast/slow, better modes), and has modules to allow
admins to rapidly build admin interfaces to various database reference
tables. The admin interface module, alone, would be a major time-saver.
* Mostly a scripting language, but a fake compiler could be provided
that would convert the script into a Linux ELF binary or EXE. However,
when you run the binary, it extracts the script to $TEMP (or %TEMP%)
(if not already extracted with same CRC stamp) and runs it in
interpreted mode from there. You still need the interpreter to be
installed before the binaries would work, which is forgivable. If you
try to run the binary without the interpreter, it would display a
friendly command-line message back suggesting that you "Google for the
interpreter".
* Various IDEs could be available for it, but it would have a slick,
VB6-like IDE where you can build Qt or GTK "forms" with various widgets
on them, doubleclick them to access their code, and then save as one
big script, optimized as much as possible.
* When run at command-line, it would NEVER spit out HTML on errors.
When you run "php -q program.php", if your program has an error, you're
going to get HTML back.
* No need for "-q" for command-line programs like you need with PHP.
* Would run indefinitely by DEFAULT, and not require "-d
max_execution_t ime=10000" to be added. Instead, if you wanted a timeout
restriction on the script, you'd have to add that into the script's
source code at the top.
* You can add new modules far easier without recompiling PHP and
Apache.
* Can be installed side-by-side other, earlier versions of Polar.
* Can be installed even if you don't have Apache, providing a way to
make GTK, Qt, or console-based apps.
* Can be installed easily on Linux, or retrieved easily with "apt".
say that I'd like to see it grow more or for derivatives to come from
it. For me, the ideal programming language would be:
* Would take the name of Polar instead of PHP.
* Syntacticaly exactly like PHP, but would be much faster on string
handling and would swap "." for "->".
* Has all the same modules of PHP but would have extremely easy-to-use
Qt and GTK modules (a way to build cross-platform GUIs), have fast ways
to build ssh/telnet data entry or cash register apps for VT100 or VT220
terminals, have faster ways to build HTML tables, have cookie routines
that are encrypted (fast/slow, better modes), and has modules to allow
admins to rapidly build admin interfaces to various database reference
tables. The admin interface module, alone, would be a major time-saver.
* Mostly a scripting language, but a fake compiler could be provided
that would convert the script into a Linux ELF binary or EXE. However,
when you run the binary, it extracts the script to $TEMP (or %TEMP%)
(if not already extracted with same CRC stamp) and runs it in
interpreted mode from there. You still need the interpreter to be
installed before the binaries would work, which is forgivable. If you
try to run the binary without the interpreter, it would display a
friendly command-line message back suggesting that you "Google for the
interpreter".
* Various IDEs could be available for it, but it would have a slick,
VB6-like IDE where you can build Qt or GTK "forms" with various widgets
on them, doubleclick them to access their code, and then save as one
big script, optimized as much as possible.
* When run at command-line, it would NEVER spit out HTML on errors.
When you run "php -q program.php", if your program has an error, you're
going to get HTML back.
* No need for "-q" for command-line programs like you need with PHP.
* Would run indefinitely by DEFAULT, and not require "-d
max_execution_t ime=10000" to be added. Instead, if you wanted a timeout
restriction on the script, you'd have to add that into the script's
source code at the top.
* You can add new modules far easier without recompiling PHP and
Apache.
* Can be installed side-by-side other, earlier versions of Polar.
* Can be installed even if you don't have Apache, providing a way to
make GTK, Qt, or console-based apps.
* Can be installed easily on Linux, or retrieved easily with "apt".
Comment