Difference between revisions of "Why Native?"
From MidrangeWiki
| Line 15: | Line 15: | ||
! width="200"|Scripting Environments (PHP, Python, Perl, Ruby) | ! width="200"|Scripting Environments (PHP, Python, Perl, Ruby) | ||
|- | |- | ||
| − | | | + | | |
| − | | | + | | |
| − | | | + | | |
| − | | | + | | |
|- | |- | ||
| − | | | + | | |
| − | | | + | | |
| − | | | + | | |
| − | | | + | | |
|} | |} | ||
{{stub}} | {{stub}} | ||
Latest revision as of 22:59, 22 July 2014
Purpose
This page provides summary comparisons between the IBM i "native" virtual machine environment (command line, integrated database, integrated language environment, work management, and so forth) versus other runtime environments (Java & Microsoft .Net) versus scripting environments (PHP, Python, Perl, Ruby). Each type of environment has advantages and disadvantages over the other; this page will delineate them.
| Attributes | Native Virtual Machine (IBM i OS, ILE, etc.) | Other Virtual Machines (Java & .Net) | Scripting Environments (PHP, Python, Perl, Ruby) |
|---|---|---|---|
This article is a stub. You can help by editing it.
